Restore topology command dispatch and fix stale soon badges (#180)

## Summary
- `specsync topology` was silently broken by PR #174's rebase (its
source branch predated the command's dispatch wiring) — restores
`"topology": true` in `knownSubcommands` and the `case "topology":
runTopology(rest)` arm.
- Drops the stale `"status": "soon"` badge from three feature cards on
specsync.se whose features actually shipped weeks ago (design notes
overflow #139, topology #168, adopt #160).

Found while verifying the #174/#177 deploys were fully correct.

Closes #179

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Author: androidand

cmd/specsync/main.go

@@ -33,7 +33,7 @@ var knownSubcommands = map[string]bool{
 	"sync": true, "audit": true, "audit-tasks": true, "validate": true,
 	"spinoff": true, "pr-body": true, "verify": true,
 	"agent-help": true, "doctor": true, "idea": true, "ideas": true, "archive": true,
-	"epic": true, "adopt": true,
+	"epic": true, "adopt": true, "topology": true,
 }
 
 // knownConfusions maps a word someone might reach for by habit (e.g. git's
@@ -94,7 +94,7 @@ func deprecatedSlugFlag(args []string) error {
 func main() {
 	cmd, rest, err := resolveSubcommand(os.Args[1:])
 	if err != nil {
-		fmt.Fprintf(os.Stderr, "specsync: %v\n\nRun with no subcommand (optionally with flags) to sync, or use one of: pull, adopt, link, scan, trace, release-plan, changelog, install-skill, changes, set-stage, set-priority, note, audit, audit-tasks, validate, spinoff, pr-body, verify, idea, ideas, archive, epic\n", err)
+		fmt.Fprintf(os.Stderr, "specsync: %v\n\nRun with no subcommand (optionally with flags) to sync, or use one of: pull, adopt, link, scan, trace, release-plan, changelog, install-skill, changes, set-stage, set-priority, note, audit, audit-tasks, validate, spinoff, pr-body, verify, idea, ideas, archive, epic, topology\n", err)
 		os.Exit(2)
 	}
 
@@ -151,6 +151,8 @@ func main() {
 		runArchive(rest)
 	case "epic":
 		runEpic(rest)
+	case "topology":
+		runTopology(rest)
 	default:
 		runSync(rest)
 	}

openspec/changes/restore-topology-dispatch/proposal.md

@@ -0,0 +1,26 @@
+# Restore the topology command and fix stale "soon" badges on the site
+
+## Why
+PR #174 (store support) was rebased from a branch that predated two pieces of
+already-shipped work: the `topology` subcommand's dispatch wiring in
+`cmd/specsync/main.go`, and the "See who's already working what" feature card
+on specsync.se. The flat-diff reapplication silently dropped the `topology`
+case from `knownSubcommands` and the `main()` switch, so `specsync topology`
+now fails with "unknown subcommand" even though `runTopology` and all its
+tests are still present and working.
+
+Separately, while reviewing the site after that merge: three feature cards
+(design notes overflow #139, topology #168, adopt #160) still carry a "soon"
+badge even though all three shipped weeks ago.
+
+## What Changes
+- Restore `"topology": true` in `knownSubcommands`, the `case "topology":
+  runTopology(rest)` dispatch arm, and `topology` in the subcommand list
+  printed on an unknown-subcommand error.
+- Drop the stale `"status": "soon"` / `"issue"` fields from the three
+  already-shipped feature cards in `site/features.json`.
+
+## Impact
+- Affected code: `cmd/specsync/main.go`, `site/features.json`
+- No spec delta: restores previously-specified, previously-tested behavior
+  that regressed in a merge; doesn't change any contract.

openspec/changes/restore-topology-dispatch/tasks.md

@@ -0,0 +1,2 @@
+- [x] Restore topology to knownSubcommands and the dispatch switch
+- [x] Drop stale soon/issue fields from the three shipped feature cards

site/features.json

@@ -9,9 +9,7 @@
     "group": "plan",
     "icon": "flow",
     "title": "Design notes survive the worktree",
-    "body": "A <code>design.md</code> renders as <code>## Design notes</code> in the synced issue, so decisions made while planning aren't lost if the local worktree is force-removed. Oversized notes overflow to a linked issue comment instead of getting truncated.",
-    "status": "soon",
-    "issue": 139
+    "body": "A <code>design.md</code> renders as <code>## Design notes</code> in the synced issue, so decisions made while planning aren't lost if the local worktree is force-removed. Oversized notes overflow to a linked issue comment instead of getting truncated."
   },
   {
     "group": "plan",
@@ -23,9 +21,7 @@
     "group": "plan",
     "icon": "flow",
     "title": "See who's already working what",
-    "body": "<code>specsync topology</code> joins every change with its tracker issue, git branch, and worktree across coordinated stores — a read-only check before an agent starts, so it doesn't duplicate work already in flight.",
-    "status": "soon",
-    "issue": 168
+    "body": "<code>specsync topology</code> joins every change with its tracker issue, git branch, and worktree across coordinated stores — a read-only check before an agent starts, so it doesn't duplicate work already in flight."
   },
   {
     "group": "plan",
@@ -49,9 +45,7 @@
     "group": "collaborate",
     "icon": "idempotent",
     "title": "Adopt an existing issue",
-    "body": "<code>specsync adopt -issue 3691 -change my-change</code> binds a change and an issue that already exist independently, writing the ref cache before touching the issue body so the link holds immediately instead of racing search indexing.",
-    "status": "soon",
-    "issue": 160
+    "body": "<code>specsync adopt -issue 3691 -change my-change</code> binds a change and an issue that already exist independently, writing the ref cache before touching the issue body so the link holds immediately instead of racing search indexing."
   },
   {
     "group": "collaborate",