Link check — Command Center and its attachments

What I checked

• Command 1.5 and Command Center pages — every href and src in cc.html, index.html, home.html, map.html, search.html, clickbridge.html, cc-console.html, command-center-v2, plus the Systems index.
• Every attachment in the Command store — 109 attachment entries across all cards and steps in cc-data.js.
• Inside the attached documents — all 120 HTML and Markdown files under ! Systems/initiatives, following their own links.
• Retired names — a sweep for @ Briefs, _tasks.md, @ Investing, _FIRST-PRINCIPLES, @ Travel without the plus, and the rest of the dead folder names.
• Initiative folders — every folder on disk against every live initiative, both directions.

I did not go into the whole Singularity tree. That is a bigger sweep and a separate decision.

The 16 broken links

Each link below goes to the real file, so you can check any of them. They only open on your tailnet (your Mac or your phone).

The four renames behind them

Why it happened

Command already knows how to fix this. There is a repair step in the server called fix_attachment_paths that runs on every save: if an attachment's file is gone, but a file of the same name sits under the initiative's current folder, it re-points the link. You added it on Sep 27 after the task-card images 404'd when "Harnesses" became "Harness".

It only ever looks at card["attachments"]. Step attachments live one level down, at card["checklist"][n]["attachments"], and the loop never reaches them. So card attachments self-heal and step attachments rot.

The charter on this initiative says no step here gets wired into production, so I have not touched the server. The fix belongs to a build track, and it is one change in ! Systems/command-center/_server/cc-server.py, around line 228.

Things that look broken and are not

• Every /briefs/ link. Command points at /briefs/LEDGER.html and /briefs/ledger-data.js on the phone. That reads like a leftover from the old @ Briefs folder, but /briefs is just the Tailscale route name for the Ledger server on port 8080, and that server serves the whole drive with fallbacks for old names. I tested the live route: it answers 200. The name is historical; the links work.
• ! Main/... written without its folder. Several notes say ! Main/agent-samples. The real path is @ Singularity 🧠/Forge/! Main/agent-samples. That is your shorthand, not a link, and it resolves.
• @ Briefs in old results and notes. 33 mentions in the Command store. All but one sit in finished steps describing the move itself, which is exactly where that name belongs. The only live-looking one is in a step completed Sep 11, before the move.
• _move/ scripts and dated _tools/patch-*.js. Full of retired names on purpose — they are the migration tools and one-shot patches that have already run.
• All 120 attached documents. Zero broken links inside them. Both ClickBridge share links are live.

Smaller things, your call

• 7 stale attachment labels. Seven cards carry an attachment named ! Systems/ledger/_server/ledger-data.js with no path behind it. That file is retired — there is a RETIRED-ledger-data.md sitting where it used to be, and the server now builds the data on demand. The label is not clickable, so nothing breaks; it just says something untrue. One more, on Ledger backlog, still says @ Briefs/_server/ledger-data.js.
• 2 genuinely dead links, on pages nothing links to. command-center-v2/index.html points at ../../@ Briefs/LEDGER.html, and that folder now holds only a MOVED note. cc-console.html is the pre-1.5 console. Neither is on the Systems index, so nobody reaches them — but if you ever open one, that is why it is empty.
• 1 dead path in a finished result. The "Fix cal-sync dropping today's events" result names ! Systems/_ui/upcoming.js. No file by that name exists anywhere.
• 4 orphan initiative folders — figure-out-fridge-frost-issue, maintain-contacts, plan-a-fall-trail-race, test-initiative. Each holds 3 or 4 files and belongs to no live initiative. The server leaves these for you on purpose. Nothing points at them. Every live initiative does have its folder.

What I would do next

• Make the repair step walk steps as well as cards, then save once. That clears all 16.
• Decide whether to retire cc-console.html and command-center-v2, or fix their two links.
• Say whether you want the same sweep run across Singularity. I stopped at the edge, as you asked.