Add agent context format #27
No reviewers
Labels
No labels
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
priority:p0
priority:p1
priority:p2
priority:p3
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pdurlej/fallow-ts!27
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "codex/wave2-agent-context-format"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Canary Context Pack
Product story
Agents need a compact prompt-oriented summary of the graph before editing. JSON remains the machine contract;
agent-contextis the small human/model-readable view.What changed
--format agent-contextto the CLI.formatAgentContext()Markdown output.Why it changed
This completes Wave 2 issue #11 and gives agents a usable context format without requiring MCP.
Files touched
src/cli.tssrc/format.tssrc/types.tssrc/index.tstests/cli.test.mjstests/golden.test.mjstests/golden/basic-agent-context.mddocs/agent-context.mddocs/report-schema-v0.mdREADME.mdRelevant context
Stacked on PR #26 / branch
codex/wave2-circular-dependencies.Runtime evidence
npm run buildnpm testnode dist/cli.js analyze --root . --format agent-context --output /tmp/fallow-ts-agent-context.mdgit diff --checkKnown constraints
Until diff-aware input exists, the
Touched Modulessection lists all analyzed modules and says so explicitly.Explicit out-of-scope
No MCP server, no changed-only analysis, no classification buckets, no baseline/fail-on behavior.
Requested decision
Review and approve as Wave 2 PR 5.
Merge blockers
Format output being misleading for agents, missing golden coverage, or docs implying changed-only behavior.
Closes #11.