Plans Inventory 2026-05-16

Cold-start orientation doc. If you’re an agent or a human landing in dididecks-ai/ for the first time after 2026-05-16, read this first. The plans on disk are largely accurate (they were status-swept on 2026-05-16 per the new Maintain-Status-Discipline-Across-Context-V-Files habit), but this doc is the cheaper map.

Read this first — Scroll-UI vs. Play-UI

Scroll-UI and Play-UI are not “two views of the same content.” They are two coordinated implementations of every slide:

• Scroll-UI slide = a section component inside src/pages/scroll/{deck}/{variant}/index.astro. Responsive CSS, vertical reading, JS allowed. The surface Claude (and humans) design in.
• Play-UI slide = a standalone file at src/components/slides/{variant}/{slot}-{slug}.astro, rendered by the shell’s /play/[slot] route inside SlideCanvas. Rigid 16:9 at 1920×1080. No responsive CSS. No JS. Static-only. The surface Claude is bad at without explicit constraint.

Coupling is by slot identity only (pitch/enhanced-v3/05 is the same conceptual slot in both). The two files are unrelated and require a deliberate recreate-don’t-extract conversion (Phase 1 → Phase 2 of the deck-iteration-workflow, encoded in /api/slide-decompose). A deck has Play-UI only insofar as its per-slide files exist.

If this framing is new to you, also see: dididecks-ai/CLAUDE.md “Naming is fuzzy here”, context-v/sitemap/README.md, and the agent memory feedback_scroll_vs_play_are_different_components.

What shipped between 2026-05-12 and 2026-05-16

Beyond Phase A+ (which the prior inventory covers), the substantive deltas:

Restore-Calmstorm-Nav-Elegance (partial, 2026-05-14)

• apps/deck-shell/src/styles/chrome-tokens.css — the --ddd-chrome-* token namespace
• apps/deck-shell/src/components/DeckChrome.astro (470 LOC) — floating themable capsule replacing v0.1 PlayChrome
• apps/deck-shell/src/styles/themes/neutral.css — default theme
• PlayChrome.astro now an @deprecated shim around DeckChrome
• The event contract (ddd:section-changed, ddd:section-prev/next) — wired in DeckChrome, ready for Phase 2’s scroll-side PageAsDeckWrapper

DeckOverlay components (new, 2026-05-15)

• <DeckOverlay--Scroll-UI> + <DeckOverlay--Play-UI> — composition wrappers in the shell. Named slots for nav / classify / notes / telemetry. Establishes the --Scroll-UI / --Play-UI paired-suffix discipline for any component where UI mode matters.
• SlideRankPill position prop (bottom-right default, top-right for Play-UI) — resolves the corner-stacking conflict with DeckChrome.
• Chroma’s /scroll/pitch/enhanced-v3/ swapped its <SlideRankPill> mount for <DeckOverlay--Scroll-UI>.

/play/ chooser fix (new, 2026-05-16)

• DeckFormat axis retired from chroma-decks/src/data/decks.ts.
• chroma-decks/src/data/play-availability.ts — runtime-detects Play-UI availability via import.meta.glob over src/components/slides/**. AND-intersects file existence with SLOTS[variant] so it’s structurally incapable of linking to a route the shell can’t emit.
• /play/index.astro ported the card-grid pattern from /scroll/index.astro; primary CTA points at the newest playable variant.
• SLOTS["proto"] populated (13 entries matching the existing per-slide files; slot 06 deliberately skipped).

Context-vigilance amendments (new, 2026-05-16)

• context-v/sitemap/ — new directory in dididecks-ai with 13 shell-side mini-specs (components/* + routes/*) and a README codifying the convention.
• client-sites/chroma-decks/context-v/sitemap/ — consumer-side counterpart with 5 mini-specs.
• dididecks-ai/CLAUDE.md — new “Naming is fuzzy here” section codifying Scroll-UI vs. Play-UI.
• Memory: feedback_scroll_vs_play_are_different_components.md saved at user-memory level.

Lossless-skills + monorepo (out of scope for dididecks-ai but worth knowing)

• context-vigilance skill amended with a status-discipline framework. New deep-reference at references/status-discipline.md.
• New habit at lossless-monorepo/context-v/habits/Maintain-Status-Discipline-Across-Context-V-Files.md.
• All 9 plans in dididecks-ai/context-v/plans/ swept and status-promoted on 2026-05-16.

Plans on disk — current status

Working URLs (smoke-tested 2026-05-16)

Buttoning-up remainders (context-v hygiene, not code)

After this session, the following hygiene items are still pending. Roughly in order of cheapness × value:

1. Changelog entries. No changelog/2026-05-15.md or 2026-05-16.md in either dididecks-ai/changelog/ or client-sites/chroma-decks/changelog/. Several days of commits go undocumented; per changelog-conventions skill, shipping a coherent chunk should produce a changelog entry.
2. Sitemap stubs for planned-but-not-built components. ContentFit.md, DeckHeader.md, ModeToggleScrollPlay.md should exist as status: planned mini-specs under context-v/sitemap/components/, back-linked to the Restore plan. Sitemap currently documents only what’s built; should document the intended architecture so the gap is legible.

The other items from the original buttoning-up list have been addressed:

• ✅ Plan status updates (this session, items 1 & 2 of the original list)
• ✅ Plans-Inventory refresh (this very doc)
• ✅ Historical-doc correction header (added to Plans-Inventory-and-Phase-A-Outcome.md frontmatter on supersession)

Three reasonable next iterations

When you (or the next agent) pick this up, three candidates close meaningful gaps:

Path A — A++.2 route refactor (founder-facing impact)

Refactor /play/[deckSlug]/[variantSlug]/[slot].astro to consume <DeckOverlay--Play-UI>. Closes A++.2 — in-play classifier ranking. Medium risk (touches a working route used daily). The overlay is already built, props-shaped, and exported. The migration is mainly: import the overlay, pass DeckChrome props through to it, and pass the slide as the default <slot>. The overlay’s section-wrap is the play-mode adapter for SlideRankPill’s IntersectionObserver — no changes needed to the pill itself.

Estimated effort: 1–2 hours including dev-server verification.

Path B — Restore Step 7 (themable-contract validation)

Author client-sites/chroma-decks/src/styles/dididecks-chrome.css with chroma’s brand palette (orange #f05100, cream rgb(251 248 241 / 0.92), dark brown #27201c) scoped to :root[data-deck-skin="chroma"]. Wire the data-deck-skin="chroma" attribute somewhere appropriate (likely a top-level layout). Smoke-test the result: the floating capsule should pick up the orange/cream skin instead of the neutral default.

Estimated effort: 1 hour. Low-risk; purely additive; validates the entire --ddd-chrome-* contract end-to-end.

Path C — A++.1 empty-state for variants without SLOTS (cheap completeness)

Refactor apps/deck-shell/src/routes/play/[deckSlug]/[variantSlug]/index.astro to gate the redirect on SLOTS[variantSlug]?.length. If empty, render a “no Play-UI yet for this variant” panel with a link back to /scroll/{deck}/{variant}/ and /toc/{deck}/{variant}/. This closes the last typed-URL 404 path (chroma’s enhanced-v1).

Estimated effort: 30 minutes. Smallest contained change; lowest risk.

There are other directions too — Restore Steps 3 + 4 (DeckHeader + ModeToggleScrollPlay), ContentFit lift (A++.3-other-half), unblocking A.7 publish (org-name decision). Pick whichever matches the energy of the next session.

Cross-references

• [[Plans-Inventory-and-Phase-A-Outcome]] — the doc this supersedes (frozen at 2026-05-12)
• [[Chroma-Parity-and-the-Path-to-a-Shared-Deck-UI-Module]] — the architecture exploration whose Phases A–E this inventory traces
• [[../plans/Phase-A-Plus-Plus-Play-Fidelity-In-Play-Ranking-and-Variant-URL-Safety]] — the partial-shipped plan most relevant to Paths A and C above
• [[../plans/Restore-Calmstorm-Nav-Elegance-as-Themable-Shell-Primitives]] — the partial-shipped plan most relevant to Path B above
• [[../sitemap/README]] — the living map of shell artifacts (routes + components)
• [[../../client-sites/chroma-decks/context-v/sitemap/README]] — consumer-side living map
• [[../../CLAUDE.md]] — “Naming is fuzzy here — Scroll-UI vs. Play-UI” section
• context-v/skills/context-vigilance/references/status-discipline.md (in lossless-agent-skills) — the framework that produced 2026-05-16’s status sweep
• lossless-monorepo/context-v/habits/Maintain-Status-Discipline-Across-Context-V-Files.md — the habit for future sweeps