feat(agent): add deterministic base-agent orchestrator - #14
Merged
Conversation
JSONbored
force-pushed
the
codex/base-agent-orchestrator
branch
from
May 28, 2026 12:40
afe6a9e to
d9541cd
Compare
6 tasks
7 tasks
This was referenced Jul 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@gittensoryGitHub mention commands for installed repos0.2.0and updates root/package changelogsWhat changed
agent_runs,agent_actions, andagent_context_snapshotsstorage plus D1 migration.gittensory-mcp agent ....issue_commentapp health requirements and sanitized GitHub mention command handling.Why
Gittensory now has a single deterministic orchestration layer that can rank, explain, preflight, and draft public-safe packets without becoming an autonomous PR bot. MCP remains the first-class private surface, while GitHub comments stay opt-in, command-driven, and sanitized.
Validation
npm run test:ciNotes
0.2.0, but npm publishing should still happen through the release/tag path after this merges.issue_commentevent enabled for mention commands.