Skip to content

Documentation refresh: audit and update docs to cover the past two weeks of work #235

@dhilgaertner

Description

@dhilgaertner

Goal

A lot has shipped over the past two weeks (24 merged PRs since 2026-04-17) but our docs have largely not kept up. Most files under docs/ were last touched around 2026-04-10 to 2026-04-15. This issue is for planning the documentation refresh — auditing what's drifted, deciding the structure, and assigning sections — before opening focused doc PRs.

Doc staleness snapshot

File Last touched Status
README.md 2026-04-22 (#189) Partial — covers manager auto mode but nothing later
docs/configuration.md 2026-04-30 (#228) Mostly current for automation toggles
docs/troubleshooting.md 2026-04-24 (#208) Has a stop-hook fix; nothing newer
docs/architecture.md 2026-04-10 (#155) Predates ~20 PRs
docs/cli-reference.md 2026-04-15 (#176) Missing several CLI surfaces
docs/getting-started.md 2026-04-10 (#155) Predates ~20 PRs
CHANGELOG.md 2026-04-05 (#87) Stale — needs all recent entries
CLAUDE.md 2026-04-15 (#176) Predates many automation hooks/flows

Themes that shipped and need coverage

1. Automation & auto-modes (largest gap)

→ Needs: a single "Automation" doc (or major section) explaining the full lifecycle: assignment → workspace → session → review → PR open → status response → completion. Cross-link from configuration.md and getting-started.md.

2. Review board & session management

→ Needs: a Review Board doc / section, plus updates to getting-started screenshots and session-management coverage.

3. Terminal runtime & rename

→ Needs: cli-reference.md updates for crow rename-terminal (or whatever the verb landed as), troubleshooting entry for Ghostty recovery, and a new section in architecture.md explaining the dual Ghostty/tmux backend and the env flag.

4. GitLab path

→ Needs: configuration.md note on multi-host GitLab setup; troubleshooting.md note on nested-group repos.

5. Branding / minor

Proposed deliverables

  1. Audit pass — a single PR or commit walking each doc file and flagging concrete drift against this list. (Output: a checklist comment on this issue.)
  2. Automation doc — new docs/automation.md covering the full auto-flow lifecycle and every toggle in Settings → Automation, cross-referenced from README.md and configuration.md.
  3. CLI reference refresh — sweep docs/cli-reference.md against the actual CLI surface (terminal rename, any new flags from the past two weeks).
  4. Architecture refresh — add the Ghostty/tmux backend split (Add tmux backend behind CROW_TMUX_BACKEND feature flag (#198) #229) and the CROW_TMUX_BACKEND flag.
  5. Troubleshooting refresh — Ghostty surface recovery (Recover from failed Ghostty surface creation (#217) #218), GitLab nested-group slugs (Fix glab fetch failures from non-repo cwd and nested-group slug truncation #233), GITLAB_HOST mismatch (Fix GitLab fetch failing on GITLAB_HOST mismatch #215).
  6. CHANGELOG backfill — entries for everything from Add session analytics via Claude Code OpenTelemetry #137 forward. Decide whether to group by week or by version.
  7. README skim — update screenshots if needed (Replace CorveilBrandmark PNG with SVG for crisper rendering #185, Per-section select all and icon-only cancel button #226, Add quick action buttons to session detail header #231 changed visible UI), confirm feature-list accuracy.

Acceptance criteria

  • Each merged PR from Add session analytics via Claude Code OpenTelemetry #137 onward is either reflected in a doc or explicitly marked "no doc impact" in the audit checklist.
  • docs/automation.md exists and is linked from README.md.
  • docs/cli-reference.md matches actual crow CLI output as of HEAD.
  • CHANGELOG.md is current through the latest release/tag.
  • README screenshot reflects current UI.

Out of scope

  • Writing the docs themselves — that happens in follow-up PRs.
  • Restructuring the docs site / adding tooling (mkdocs, etc.) — separate concern.

Notes

The dev acceptance and feature-flag-cleanup docs for the tmux backend (#229) probably want to live in the automation doc once the flag flips on by default. For now, document the flag and the opt-in path.

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentation

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions