[Tracking] Editor next steps: Slash hardening, heading links, and MCP reads #328

Purpose

This issue tracks the next round of pad work. First, make the shipped Slash menu honest and fix bugs in shipped code. Then make heading links land where they point. Then give connected apps the heading links and changes that docs.plus already computes. Each row links one issue with its own Agent brief. An agent can start any row whose blockers are closed. A Later row opens only when its gate in the Gates table is met.

Now

The next two to four weeks.

Next

Later (gated)

Build these only after the gate in the Gates table is met.

Checks and releases

Rulings

Gates

A Later row opens on a signal docs.plus can measure. "When users ask" alone is not a gate.

The maintainer sets these numbers.

Order

1. Start Refuse a connected-app rewrite of a section that holds media #329 first, because it stops live data loss. Then start the Now rows that unblock others: Build stored heading and message links from the pad path, not the address bar #331, Undo a Slash pick with one Mod-z, and hide rows that lift their own block #332, Announce an empty Slash menu result, and give each option a stable id #333, Mark MCP chat posts with a fixed connected-app metadata key #336 and Land a heading link on its heading, even when the heading is folded or filtered #338. Ship Mark MCP chat posts with a fixed connected-app metadata key #336 early: a post made before it can never be marked.
2. Ship the other Now rows in any order. Build the Richer internal-link chips, and a kind icon beside the pad link #174 kind icon after Build stored heading and message links from the pad path, not the address bar #331.
3. Ask for the rulings early, because they run beside the build work. Rename the Slash row Picture to Media, and name the media button Insert media #334 waits on the Slash menu to insert a block #251 row-name ruling.
4. Run Confirm the bounce alert link migration is applied on production #354 before the bounce alert row of Run the PWA device checklist and close each #249 child that passes #355. Save the Measure cursor traffic per edit in production after the cursor guards deploy #353 baseline by 2026-10-10.
5. Start each Next row when its blockers close.
6. Run Measure how often writers type @username in pad text #348 before any work on Add a pad @ list where Members open a Comment and Headings insert a link #349. Open other Later rows only when their gate is met.