[auto] Sync docs site — 20522d behind source repos

[stackbilt-admin]

Autonomous Task

Task ID: 92a64cf3-82a4-47a6-a533-e5c22722ca26
Authority: auto_safe
Exit code: 0

Task Prompt

Docs site is 20522 days behind source repos (latest activity in stackbilt-auth).

Run the docs sync pipeline:

1. cd to the docs repo root
2. Export GITHUB_TOKEN from .dev.vars or environment
3. Run: ./scripts/docs-sync.sh --sync-only
4. Review the changes with git diff
5. If changes look correct, commit with: git add -A src/content/docs/ && git commit -m "docs: sync from source repos"
6. Do NOT deploy — the deploy will be handled separately

If docs-sync.sh doesn't exist yet, check if docs-manifest.json exists and read it to understand the sync architecture.

Result Summary

Build passed and commit succeeded.

Summary:

• Ran docs-sync.sh --sync-only which pulled content from 2 source repos:
  • getting-started.md — synced from charter repo README (fallback path, since docs/getting-started.md doesn't exist)
  • img-forge.md — synced from img-forge/docs/img-forge.md
• 7 other pages were skipped (source doc files don't exist in the repos yet — would need --generate flag)
• Fixed a sync script bug where frontmatter was stripped (bash subshell pipe issue)
• Removed README-only elements from getting-started.md (badges, hero image, repo-relative links) that don't work in the docs context
• Commit: d286201 — build verified by pre-commit hook

TASK_COMPLETE

[TASKRUNNER] Auto-committed uncommitted changes

---

Generated by AEGIS task runner. Review before merging.

[stackbilt-admin]

Codex Review

 2	{"version":1,"timestamp":"2026-03-04T11:38:48.692Z","commandPath":"setup","flags":["--detect-only","--format"],"format":"json","ciMode":false,"durationMs":8,"exitCode":0,"success":true}
 3	{"version":1,"timestamp":"2026-03-04T11:38:52.119Z","commandPath":"setup","flags":["--preset","--yes"],"format":"text","ciMode":false,"durationMs":22,"exitCode":0,"success":true}
 4	{"version":1,"timestamp":"2026-03-04T11:38:56.228Z","commandPath":"doctor","flags":[],"format":"text","ciMode":false,"durationMs":35,"exitCode":0,"success":true}
 5	{"version":1,"timestamp":"2026-03-04T11:39:00.252Z","commandPath":"adf.init","flags":[],"format":"text","ciMode":false,"durationMs":14,"exitCode":0,"success":true}
 6	{"version":1,"timestamp":"2026-03-04T11:39:04.156Z","commandPath":"doctor","flags":[],"format":"text","ciMode":false,"durationMs":49,"exitCode":0,"success":true}
 7	{"version":1,"timestamp":"2026-03-04T11:39:08.702Z","commandPath":"adf.migrate","flags":["--dry-run"],"format":"text","ciMode":false,"durationMs":22,"exitCode":0,"success":true}
 8	{"version":1,"timestamp":"2026-03-04T11:39:50.202Z","commandPath":"adf.migrate","flags":[],"format":"text","ciMode":false,"durationMs":45,"exitCode":0,"success":true}
 9	{"version":1,"timestamp":"2026-03-04T11:39:54.319Z","commandPath":"doctor","flags":[],"format":"text","ciMode":false,"durationMs":54,"exitCode":0,"success":true}

codex

• NON-CRITICAL: The page tells users to install Charter as a local dev dependency at src/content/docs/getting-started.md:183, but most of the new examples then invoke bare charter commands at src/content/docs/getting-started.md:193 and src/content/docs/getting-started.md:224. The repo’s own reference explicitly says local installs should use npx charter ... unless installed globally src/content/docs/cli-reference.md:12. As written, the default path leads to command not found for many users.

• NON-CRITICAL: bootstrap is now described as migrating existing agent rules at src/content/docs/getting-started.md:26 and again as detect + setup + ADF + migrate + install + doctor at src/content/docs/getting-started.md:260. That contradicts the canonical command reference, which still defines bootstrap as detect + setup + ADF init + install + doctor src/content/docs/cli-reference.md:85, with migration documented as a separate adf migrate command src/content/docs/cli-reference.md:203. The committed telemetry also shows adf.migrate being run separately /.charter/telemetry/events.ndjson:7. This inconsistency will mislead readers into skipping migration.

• NON-CRITICAL: /.charter/telemetry/events.ndjson:1 is a local-generated telemetry artifact that should not be committed with a docs change. It adds churn to future diffs and publishes local command history/timestamps for no user-facing value.
  40,467

• NON-CRITICAL: The page tells users to install Charter as a local dev dependency at src/content/docs/getting-started.md:183, but most of the new examples then invoke bare charter commands at src/content/docs/getting-started.md:193 and src/content/docs/getting-started.md:224. The repo’s own reference explicitly says local installs should use npx charter ... unless installed globally src/content/docs/cli-reference.md:12. As written, the default path leads to command not found for many users.

• NON-CRITICAL: bootstrap is now described as migrating existing agent rules at src/content/docs/getting-started.md:26 and again as detect + setup + ADF + migrate + install + doctor at src/content/docs/getting-started.md:260. That contradicts the canonical command reference, which still defines bootstrap as detect + setup + ADF init + install + doctor src/content/docs/cli-reference.md:85, with migration documented as a separate adf migrate command src/content/docs/cli-reference.md:203. The committed telemetry also shows adf.migrate being run separately /.charter/telemetry/events.ndjson:7. This inconsistency will mislead readers into skipping migration.

• NON-CRITICAL: /.charter/telemetry/events.ndjson:1 is a local-generated telemetry artifact that should not be committed with a docs change. It adds churn to future diffs and publishes local command history/timestamps for no user-facing value.

---

Automated review by Codex CLI. Not a substitute for human review.

[stackbilt-admin]

Closing: drift calculation bug produced absurd 20000+ day title. Fix in aegis self-improvement.ts. Sync state on main is current as of 2026-03-10.