Skip to content

docs: accuracy audit, Overdeck Anywhere (21 pages) #5500

Closed

Description

@eltmon

Part of the docs overhaul epic #5467. Operator direction 2026-11-17: "I am pretty sure there are huge gaps in our documentation and lots of stuff that is outdated, I want a thorough cleanup and really get documentation into tip top shape."

The feature inventory checked which features have docs, not whether each page is accurate. This issue is a line-by-line accuracy audit of every published page in the Overdeck Anywhere nav group (21 pages) against current main (v0.88 or later).

Pages

  • anywhere.mdx
  • configuration/session-vault.mdx
  • configuration/remote-access.mdx
  • configuration/linked-machines.mdx
  • configuration/shared-sessions.mdx
  • configuration/triggers.mdx
  • configuration/tailscale.mdx
  • configuration/mcp.mdx
  • configuration/bots.mdx
  • configuration/phone.mdx (also edited by docs: fix published pages that contradict the product (state branch, Cloister routing, Inspect, phone apps, introduction) #5472: audit it after that PR merges, on top of its result)
  • configuration/push-notifications.mdx
  • cli/vault.mdx
  • cli/pair.mdx
  • cli/tailscale.mdx
  • cli/account.mdx
  • cli/share.mdx
  • cli/devices.mdx
  • cli/machines.mdx
  • cli/token.mdx
  • cli/mcp.mdx
  • cli/triggers.mdx

For each page

  1. Read the whole page. List every factual claim: commands and flags, config keys and defaults, UI labels and locations, file paths, behavior, limits, supported harnesses/trackers/platforms, maturity.
  2. Verify each claim against current code (git grep), pan <verb> --help, src/lib/config-yaml/defaults.ts, the dashboard source, and changelog.mdx. Do not trust other docs pages as proof; several are stale.
  3. Fix wrong claims, delete claims about removed features, and add what a user needs that is missing (short; link to the dedicated page instead of duplicating it). Label early, experimental (Settings → Experimental) and testing features as such.
  4. Frontmatter: specific searchable title, description 50 to 160 characters, no em or en dashes in either. Remove em dashes from the body too.
  5. Check every link on the page resolves.
  6. Tick the page above in the PR body with a one-line note of what changed (or "verified, no change").

Every PR for this issue

  • Run the Mintlify validator (npx mint validate or the current equivalent) and the link check (npx mint broken-links) and paste the clean result in the PR body.
  • Zero U+2013/U+2014 in titles and descriptions of the touched pages.
  • Docs-only: no changelog.d entry unless behavior changed.
  • Where a page talks about getting help, link the Overdeck Discord (https://discord.gg/ZpHE2ZTv5P) and GitHub Issues.

Activity

  1. eltmon commented on Nov 17, 2026

    @eltmon
    OwnerAuthor

    Known stale item for this audit (from the site critic, 2026-11-17): configuration/triggers.mdx still says webhook triggers are "Available from the next release". Check the shipped state and fix the wording.

  2. added
    planningIssue is in planning/discovery phase
    in-progressWork is actively being done
    and removed
    planningIssue is in planning/discovery phase
    in-progressWork is actively being done
    on Nov 19, 2026
  3. eltmon commented on Nov 19, 2026

    @eltmon
    OwnerAuthor

    🤖 Agent completed work:

    docs: accuracy audit of the Overdeck Anywhere docs group (21 pages). No deviations from the PRD. All 24 page/validation items complete, each committed and pushed separately. Validators (dash rule, stale-release check, frontmatter, help-link, lint:docs, mint validate, mint broken-links) all pass; 3 pre-existing broken links and 23 pre-existing duplicate-h1 warnings outside or unrelated to this change are noted as Follow-ups, not fixed. PR body draft with the 21 page lines and validation output is in the validate-and-pr-body commit message, to be appended to the PR body.

  4. added
    mergedMerged to main
    verifying-on-mainMerged — awaiting verification on main
    and removed on Nov 19, 2026
  5. eltmon commented on Nov 19, 2026

    @eltmon
    OwnerAuthor

    Closed via close-out ceremony

    Definition of Done
    # Row Status Observed
    1 Review passed ✓ pass PR #5581 reviewDecision: APPROVED
    2 Tests passed ✓ pass PR #5581 checks: all 26 check(s) green
    3 Verification green on the branch ✓ pass verification artifact: passed at 2026-11-19T04:31:41.651Z
    4 Merged to main ✓ pass Pull request #5581 merged at 2026-11-19T04:50:07Z; PR #5581 MERGED at 2026-11-19T04:50:07Z
    5 Post-merge lifecycle ran ✓ pass canonical state: verifying_on_main; no running work/planning agents (stored running, not live: planning-pan-5500)
    6 Verified on main ✓ pass required checks concluded successfully on 2007e9a: test, lint, build (22), reject-planning-paths
    7 Version strings propagated – skip project declares no version_sync; ship step not applicable
    8 Deployed ✓ pass build commit a50ee2a contains merge 2007e9a
    9 Close-out teardown verified ✓ pass workspace removed; feature branch kept (close_out.delete_feature_branch is off); No tmux sessions or Herdr panes found; No shadow state found; No legacy planning directory found; Stopped Docker containers; No orphaned processes found; No worker worktrees; Removed git worktree; Pruned 4 agent directories (transcripts and state kept); No strike branch strike/pan-5500 found; Pruned 393 checkpoint ref(s) for agent-pan-5500, planning-pan-5500, strike-pan-5500; No specialist registry entries for PAN-5500

    Gate: passed

  6. added
    closed-outVerified and closed out
    and removed
    mergedMerged to main
    verifying-on-mainMerged — awaiting verification on main
    on Nov 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    closed-outVerified and closed outdocumentationImprovements or additions to documentation

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions