Repository navigation
docs: retire mandatory minimal-orchestration - #984
Merged
Merged
Conversation
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 59 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Problem and result
The repository required a globally installed minimal-orchestration skill, which can block authorized work when that old skill is unavailable. Retire that prerequisite in AGENTS.md, the orchestration adapter, and rawsql-task-orchestrator. Keep repository impact routing, tmp/PLAN.md, durable handoff evidence, verification, review, branch isolation, and authorization requirements.
This is repository-only workflow maintenance (no-release; no Changeset). It does not change packages, dependencies, SQL behavior, MCP, security controls, or historical reports. The user explicitly requested this retirement separately from the concurrent security fixes: control task.
Verification and readiness
Next: review the policy diff. Merge/release is not authorized by this PR.
Merge Readiness
The required checks remain required. This PR does not claim that unrun local or main-only workflows passed and does not request a waiver.
Self Review
Self-review workflow: .codex/guidance/review.md consistency review, retro triage, and human-acceptance review against root#145.
Self-review result: no unresolved policy-diff blockers; preservation checks and remote PR/CI/Release Readiness passed. Unrun optional/local/main-only verification is disclosed above, without changing the existing checks.
Concept-review workflow: explicit no-concept-impact review; only repository task guidance changes, with no packages, SQL contracts, public API, CLI, scaffold, generated product output, or human-owned business meaning affected.
Concept-review result: no package or concept-boundary violations found in the three-file diff; no product/release scope change.