Skip to content

docs(#5762): add missing status flags, manifest fields, and init examples - #5764

Merged
ggallen merged 1 commit into
mainfrom
agent/5762-fix-repos-doc-gaps
Jul 30, 2026
Merged

docs(#5762): add missing status flags, manifest fields, and init examples#5764
ggallen merged 1 commit into
mainfrom
agent/5762-fix-repos-doc-gaps

Conversation

@fullsend-ai-coder

Copy link
Copy Markdown
Contributor

Summary

Fix three documentation gaps in repos management docs identified in the audit for PR #5741.

Changes

  • cli-internals.md: Add --manifest/-f, --json, --repo, and --concurrency flags under repos status in the command tree, matching the pattern used by diff and sync
  • repo-management.md: Add inference_project and inference_region to the multi-forge manifest YAML example under forge.github
  • repo-management.md + docs/cli/repos.md: Add --mint-url <MINT_URL> to the primary repos init examples (getting started and migration sections)

Testing

  • Verified repos status flags against implementation in internal/cli/repos.go (lines 222-225)
  • Verified inference_project/inference_region fields exist in internal/repos/manifest.go (lines 67-68)
  • Verified --mint-url flag is registered in repos init command tree in cli-internals.md

Checklist

  • PR title follows Conventional Commits (correct type, ! for breaking changes)
  • Documentation-only change — no code or tests affected

Closes #5762

Post-script verification

  • Branch is not main/master (agent/5762-fix-repos-doc-gaps)
  • Secret scan passed (gitleaks — 2843dc797bbd8b74d72b5984023aa216db73c147..HEAD)
  • PR body secret scan passed (gitleaks — no-git)
  • Pre-commit hooks passed (authoritative run on runner)
  • Tests ran inside sandbox

…ples

Add repos status flags (--manifest/-f, --json, --repo, --concurrency)
to the cli-internals.md command tree, matching the pattern used by
diff and sync. Add inference_project and inference_region to the
multi-forge manifest example in repo-management.md. Add --mint-url
to the primary repos init examples in repo-management.md and
docs/cli/repos.md.

Note: pre-commit could not run in sandbox (network restriction).
The post-script runs an authoritative pre-commit check.

Closes #5762
@fullsend-ai-coder
fullsend-ai-coder Bot requested a review from a team as a code owner July 30, 2026 14:16
@fullsend-ai-coder fullsend-ai-coder Bot added the ready-for-review Triggers review agent dispatch label Jul 30, 2026
@fullsend-ai-review

fullsend-ai-review Bot commented Jul 30, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 2:18 PM UTC · Completed 2:30 PM UTC
Commit: a4cd434 · View workflow run →

@github-actions

Copy link
Copy Markdown

Site preview

Preview: https://e6a58d52-site.fullsend-ai.workers.dev

Commit: a4cd434823e021de629a2ee199f0ab83d6041a3e

@codecov

codecov Bot commented Jul 30, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@fullsend-ai-review

Copy link
Copy Markdown

Looks good to me


Labels: PR modifies documentation files under docs/ only

@fullsend-ai-review fullsend-ai-review Bot added ready-for-merge All reviewers approved — ready to merge component/docs User-facing documentation Review effort 1/5 labels Jul 30, 2026
@ggallen
ggallen added this pull request to the merge queue Jul 30, 2026
Merged via the queue into main with commit aae2033 Jul 30, 2026
35 checks passed
@ggallen
ggallen deleted the agent/5762-fix-repos-doc-gaps branch July 30, 2026 14:41
@rh-hemartin

Copy link
Copy Markdown
Member

--mint-url was made a default for a reason, this tool is brining it back without a default?

@fullsend-ai-retro

fullsend-ai-retro Bot commented Jul 30, 2026

Copy link
Copy Markdown

🤖 Finished Retro · ✅ Success · Started 2:44 PM UTC · Completed 2:59 PM UTC
Commit: a4cd434 · View workflow run →

@fullsend-ai-retro

Copy link
Copy Markdown

Retro: PR #5764 — docs(#5762): add missing status flags, manifest fields, and init examples

Workflow outcome: Efficient, successful docs-only PR. 38 minutes from issue filing to merge, $4.77 total agent cost across triage + code + review.

Timeline

Time (UTC) Event
14:03 Issue #5762 filed by ggallen — 3 well-scoped doc gaps with exact file/line references
14:03–14:08 Triage confirmed all 3 findings (5 min)
14:09–14:16 Code agent produced PR #5764 ($1.82, ~3 min active, 47 turns)
14:16–14:30 Review agent approved with 0 findings ($2.95, 10 min, 4 sub-agents + challenger)
14:38 ggallen (issue author) approved
14:41 PR merged
Post-merge rh-hemartin questioned --mint-url addition to primary examples

What went well

  • Issue quality: ggallen filed a detailed, well-scoped issue with exact file paths and line numbers for all 3 gaps.
  • Code agent efficiency: Faithfully implemented all 3 changes in ~3 minutes active time at $1.82. Verified each doc change against the Go source code before committing.
  • Review agent thoroughness: Dispatched 4 domain-specific sub-agents (correctness, style-conventions, intent-coherence, docs-currency). The correctness sub-agent (opus) verified all documented flags against internal/cli/repos.go and internal/repos/manifest.go. The challenger correctly dismissed 3 false-positive style findings about placeholder naming conventions.
  • Zero rework: Single commit, single review iteration, no fix agent needed.

One gap identified — already tracked

Post-merge editorial concern: rh-hemartin commented that --mint-url was intentionally omitted from examples because it has an auto-discovery mechanism (in internal/repos/init.go lines 426–441, repos init discovers the mint URL from org variables, dispatch config, or per-repo state). Adding --mint-url <MINT_URL> to primary examples could mislead users into thinking they must provide this value when the CLI discovers it automatically.

The review agent's correctness sub-agent verified --mint-url exists as a valid flag (technically correct) but did not assess whether showing it in primary examples was appropriate given the discovery mechanism. This gap is already tracked by fullsend-ai/agents#169 ("Correctness sub-agent should flag docs that present default config values as required settings"). This PR provides corroborating evidence: implementing #169 would extend to auto-discovery mechanisms, not just hardcoded defaults, and would have surfaced a finding like "the --mint-url flag is auto-discovered by repos init — verify this belongs in primary examples rather than an advanced/greenfield section."

Note: the issue author (ggallen) explicitly requested this change ("Greenfield setups need this flag") and approved the PR, so this is fundamentally a maintainer editorial disagreement rather than a systemic agent failure.

Autonomy assessment

The review agent's approval matched the first human reviewer's (ggallen) approval. The editorial concern raised by rh-hemartin post-merge reflects domain knowledge about CLI design intent that is difficult to encode in agent instructions. No autonomy change is warranted from this single PR — the review agent performed well on technical accuracy for a docs-only change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

component/docs User-facing documentation ready-for-merge All reviewers approved — ready to merge ready-for-review Triggers review agent dispatch Review effort 1/5

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: fix repos management doc gaps (status flags, manifest example, init examples)

2 participants