feat: orc propose — the approval queue's front door#8
Merged
Conversation
Run.propose() was Python-only, so nothing outside a skill could stage an action: the approval queue had a human review surface but no external producer surface. orc propose routes a CLI-originated action through the exact guarded path skills use (executor existence, params schema, workspace allow-list — all checked before anything is enqueued) inside a traced run, and prints the human next steps or machine-readable JSON. Denials come back actionable: unknown executors list the known ids, allow-list rejections print the exact config.toml snippet, schema violations print the executor's schema. approve list gains --json so scripts can check the queue without scraping the rich table. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Context
Both validation studies named the credential-separated approval queue the #1 priority — but
Run.propose()was Python-only, so nothing outside a skill could stage an action. This adds the missing CLI surface (and unblocks baton's ship step).Changes
orc propose EXECUTOR --params '<json>'|@file --summary TEXT -w WS [--approvers N] [--idempotency-key K] [--json]— routes through the exact guarded path skills use (executor existence → params schema → workspace allow-list), inside a traced run. Actionable denials: unknown executor lists known ids; allow-list rejection prints the exact config.toml snippet; schema violation prints the schema.orc approve list --json— machine-readable queue check for scripts.Known limit (documented):
orc replayof a propose-run is unsupported — replaying a proposal would silently stage a duplicate effect.Testing
11 new propose CLI tests + 1 approve-list test, all RED-first; full suite 308 passed, ruff clean.
🤖 Generated with Claude Code