Contracts
Accepted records define public behavior. Use them for exact schemas, limits, diagnostics, and compatibility rules. Proposed records are review material only and authorize no implementation or provider access.
| Concern | Contract |
|---|---|
| Hidden issue data | Issue contract v1 |
| Repository field ownership | Repository policy v1 |
| Plan and redacted report | Reconciliation plan v1 |
| Read-only GitHub boundary | GitHub read-only adapter v1 |
| REST-first snapshot | REST Project snapshot v2 |
| Dry-run Action and CLI | Action and CLI release v1 |
| Dry-run and legacy-shadow credential eligibility | Dry-run credential profile v1 |
| Controlled mutation semantics | Controlled mutations v1 |
| GitHub mutation transport | REST-first field creation v2 |
| Apply entrypoint | Controlled apply entrypoint v1 |
| Reviewed single-token exception | Controlled apply single-token profile v1 |
| Resumable rate deferral | Resumable rate-limit deferral v1 |
| First usable suite preview | Projects effects v1 |
| MCP compound approval and bounded apply entrypoint | MCP compound approval bridge and wrapper v1 |
| MCP compound approval implementation candidate | Bridge and wrapper implementation v1 |
Unknown versions and fields fail closed. A plan or credential alone never authorizes apply. For dry-run and legacy-shadow, read permissions are the functional minimum and least privilege is recommended; excess write permissions on an existing supplied credential are not an eligibility failure.
The accepted preview and approval-bridge records remain the semantic authority.
The bridge and wrapper contract was substantively reviewed and merged through PR #152 as
nomed/yukh-projects@56118de6760b5b582c9a2cf84640e22e3eaaac83. They preserve
the Accepted Projects add_dependency Effect B. The unreviewed implementation
candidate under #154 adds no provider, credential, live-effect, deployment,
activation, or release authority.