#24137 Agent chat: Chat Minimap is one choice (Rail, Full Map, Off), found as "tick rail" in the palette and Settings

Summary

Leo (2026-10-22):

yo where'd the scrolling thing on the left go? we had this then a session fucked it up and now it's gone? plus the option to show it left or right? default on, default left? option for minimap like vscode on the other side?

After searching the command palette for “TICK RAIL”: “doesn't show as an option…”

Chat Minimap is now a searchable Rail / Full Map / Off choice in Settings > Agents > Agent Chat and the command palette. Search finds tick rail, wave rail, prompt rail, scroll rail, thread minimap and minimap. The default is Rail (compact), matching the current experiment and preserving the rail restored by #24058. The separate VS Code Minimap toggle from #25275 remains available.

Old boolean true selects Full Map; false leaves the experiment in control. Settings and the chat bridge agree. Switching the choice preserves the transcript's measured layout snapshot. Session Info placement, Minimal Mode and current rail rendering remain intact. The historical App Store card slice was dropped: base moved Features into Settings (extensibility-DESIGN.md, R7).

Validation

Review (independent Codex xhigh): SHIP at ffb48223ab7bfc8a6324e40f7bff1639250d30a4. Whole final diff reviewed against c5d22ac381e68bc470a1049649984485fe85e70d; primary diff/worktree review and prepush checks pass. Four new strings cover all 21 locales; existing translations are unchanged.

The legacy-value regression failed on test-only commit 9c3defdd507360270c038b9783f387b120f5a738 in fleet step f1a21472fca44b745fd61501, then the seven AgentPaneDisplaySettingTests passed in d180ce46641945e9b60a7ad9 at d590a342. The measured-layout test failed before repair and passed afterward (4/0 integration tests). Setting/Settings/palette search tests pass 15/0. At exact final head ffb48223ab7bfc8a6324e40f7bff1639250d30a4, fleet step 9861bd7e633747a760ad0ae2 passed all three focused suites: AgentPaneDisplaySettingTests 7/7, SettingsSchemaExportTests 5/5, and ManagedPreferencesManifestTests 4/4. Tagged Mac build e287c39f21b977635d336c0a passed at the exact final head on aws-m4pro-6. Release compile job121805205275 is also green. The tagged build is nx24137.

Native export step 574f4ce3667b51f1d9123c3f passed MDM 4/4 and schema 5/5 before the later comment cleanup. Final-head schema and MDM freshness tests also pass. Its generated schema and MDM patch was applied with the owning helper; the docs generator produced the matching reference. Base's #23915 retired the committed source stamp, which stays removed; bot-only defaults were excluded.

Before and after

Matched Claude's settings-transcript-controls.png reference: quiet inline settings controls. These are real gallery captures of the Settings page using its existing fixture host. Native bridge behavior is covered separately by Swift tests. Before source c80354516c120e04a3adba32258268611a5e1a73: run40381329263. After source 1f01e4c67f610cb4f68bf336b7f1b684409e1157: run40387326961; subsequent changes remove obsolete Store code and correct comments, leaving this Settings renderer/schema byte-identical.

Before	After: default Rail

Full Map selected by an actual radio click; the separate VS Code Minimap remains off:

Dark	Light

Check reconciliation

The original named god-files/concurrency/crash-safety/l10n check and nightly Guard status/release-notary checks passed after the repair. At d590, every gallery shard failure matches the pinned base exactly: 13/13 fixture failures, zero PR-only findings (base run40378078083, PR run40383020556). The fast-gates work passed, but its reporting job received GitHub installation quota HTTP403 (job121786758567). At final head, all 13 gallery fixture failures again match base exactly (run40388162652). The merge-tree publisher failed HTTP422 (job121801815018); same-tree validation reports an unpublished daemon tree (job121805111037). The daemon tree is byte-identical to base; no pin branch or artifact was used. The CLI/MCP docs freshness failure also has byte-identical inputs on base; managed base run 40392785755 executed that exact freshness test at c5d22ac381e68bc470a1049649984485fe85e70d and failed with the same diff. Two earlier attempts stopped at runner setup (missing next-intl, then missing Bun); neither was counted as product evidence. The generated settings reference test passes. Broad Swift/react-app checks remain pending; the focused Swift16 and web19 behavior checks ran and passed. No HOLD label or HOLD instruction is present.

Exact-head native capture

Blacksmith run40390961121 passed all four steps at the final head: deep-link to Chat Minimap, set Full Map, then search TICK RAIL. Primary visual inspection confirms the palette result and Full Map value in both themes; privacy and errors are empty.

Capture steps-bf8c144ab6 at ffb48223ab7b (fleet build, Blacksmith macOS capture, text checked for private data)

Light	Dark

Agent session: nx-settings