Skip to content

docs(contracts): add machine-readable output contract reference#44

Merged
saraeloop merged 2 commits intomainfrom
docs/machine-contracts
Apr 15, 2026
Merged

docs(contracts): add machine-readable output contract reference#44
saraeloop merged 2 commits intomainfrom
docs/machine-contracts

Conversation

@saraeloop
Copy link
Copy Markdown
Member

Summary

Add a dedicated machine-readable contract reference for gitrole’s public
automation surfaces.

Changed

  • add a new docs reference page for:
    • gitrole status --short
    • gitrole doctor --json
    • gitrole resolve --json
  • document:
    • exact command purpose
    • output shape
    • field meanings
    • value vocabularies
    • exit codes
    • stability guarantees
  • clarify which parts are safe for automation and which are descriptive only
  • document role-name constraints so the status --short key/value output remains unambiguous
  • explicitly state that changes to these machine-readable surfaces are breaking changes

Why

These outputs were already being treated like stable public contracts in tests
and team intent, but the repo did not yet document them explicitly. This page
makes the contract visible to users, agents, and future maintainers.

Notes

  • docs only
  • no CLI logic changes

Document the public machine-readable surfaces for gitrole so scripts,
agents, and future maintainers have an explicit contract to rely on.

Also:
- add a dedicated reference page for:
  - `gitrole status --short`
  - `gitrole doctor --json`
  - `gitrole resolve --json`
- define field meanings, value vocabularies, and exit codes
- document what is considered stable vs descriptive
- clarify that contract changes to these machine-readable surfaces are breaking changes
- document role-name constraints for stable key/value output

Docs only. No CLI logic changes.
@saraeloop saraeloop self-assigned this Apr 15, 2026
@saraeloop saraeloop merged commit ecbd3e6 into main Apr 15, 2026
4 checks passed
@saraeloop saraeloop deleted the docs/machine-contracts branch April 15, 2026 18:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant