-
Notifications
You must be signed in to change notification settings - Fork 0
[Stage 2.1] Clarify deterministic text and JSON terminology #61
Copy link
Copy link
Closed
Labels
agent-friendlyarea: docsgood first contributionEntry-level contribution with clear scope and low project-context costEntry-level contribution with clear scope and low project-context costoss first friendlyFriendly for first open source contributions and automated contributorsFriendly for first open source contributions and automated contributorsstage: 2.1MVP hardening and validation work before Stage 3MVP hardening and validation work before Stage 3status: readyReady for contributors to pick upReady for contributors to pick up
Description
Metadata
Metadata
Assignees
Labels
agent-friendlyarea: docsgood first contributionEntry-level contribution with clear scope and low project-context costEntry-level contribution with clear scope and low project-context costoss first friendlyFriendly for first open source contributions and automated contributorsFriendly for first open source contributions and automated contributorsstage: 2.1MVP hardening and validation work before Stage 3MVP hardening and validation work before Stage 3status: readyReady for contributors to pick upReady for contributors to pick up
Type
Fields
Give feedbackNo fields configured for issues without a type.
Add an explanation for the following terms:
Deterministic text: the same issue, in the same project, always produces the same explanation, with the same field order and the same content.
Deterministic JSON: in addition to human-readable text, the CLI generates a structured output that can be consumed by tools, agents, and CI pipelines. The output is deterministic, meaning the same issue in the same project always results in the same JSON structure and values.