lda.chat/lda-wf
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: complete presentation opening title slice

Browse Source
This commit is contained in:
lda
2026-07-12 00:17:11 +07:00 Verified
parent 96e6e93c87
commit 6a3e9c5a82
2 changed files with 27 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/current_roadmap.md
+11 -10
View File
@@ -186,11 +186,12 @@ Presentation visual audit, July 11:
- Baseline-good: Scenes 3, 4, and 5 are good enough for now. Do not churn them
unless a later rehearsal exposes a concrete problem.
- Partially complete: Scenes 2, 6, and 7 have concrete focal artifacts, and
Scenes 8-10 share a prepared authoring/run spine. Scene 1 still needs a
title-composition repair so it introduces the agent-shaped product goal
before Scene 2 explains the automation problem. Design:
[`presentation opening title`](superpowers/specs/2026-07-11-presentation-opening-title-design.md).
- Completed: Scene 1 introduces the agent-shaped product goal through
`Planner -> Tool surface -> Runner / platform`, then identifies the last
role as the implemented contribution. Scene 2 remains responsible for the
automation problem. Scenes 2, 6, and 7 retain their concrete focal artifacts,
and Scenes 8-10 share a prepared authoring/run spine. Implementation:
[`presentation opening title`](historical/superpowers/plans/2026-07-11-presentation-opening-title.md).
- Completed: Scenes 11-12 now use decision-led approval, continuation-led
resume/output, and compact factual trace rows so approval, resume, output,
and trace remain factual without competing panels or repeated low-signal
@@ -242,11 +243,11 @@ Recommended next visual slices:
authentic external-agent handoff and factual prepared-authoring proof.
Implementation:
[`presentation agent authoring story plan`](historical/superpowers/plans/2026-07-11-presentation-agent-authoring-story.md).
7. Next: rebuild Scene 1 as an agent-shaped title composition: `Planner ->
Tool surface -> Runner / platform`, with the last role labelled
`Implemented contribution`. Keep Scene 2 responsible for the automation
problem. Design:
[`presentation opening title`](superpowers/specs/2026-07-11-presentation-opening-title-design.md).
7. Completed: Scene 1 now introduces the agent-shaped product goal through
`Planner -> Tool surface -> Runner / platform`, then identifies the last role
as the implemented contribution. Scene 2 remains responsible for the
automation problem. Implementation:
[`presentation opening title`](historical/superpowers/plans/2026-07-11-presentation-opening-title.md).
8. Next: harden the live/replay defense rehearsal path, including submitted and
revision-requested same-run resumes, replay fallback, exact deep links, and
reset instructions. Design:
docs/superpowers/plans/2026-07-11-presentation-opening-title.md → docs/historical/superpowers/plans/2026-07-11-presentation-opening-title.md
+16 -16
View File
@@ -41,7 +41,7 @@ presentation CSS and concept SVG primitives.
- Produces: `OpeningThesisScene` markup with `data-opening-focus="title" |
"contribution"`, a main heading, and an agent-role group.
- [ ] **Step 1: Write failing title-beat assertions**
- [x] **Step 1: Write failing title-beat assertions**
```tsx
const opening = screen.getByRole("region", { name: /thesis opening/i });
@@ -52,7 +52,7 @@ expect(screen.queryByRole("heading", { name: "Thesis" })).not.toBeInTheDocument(
expect(screen.queryByText("Decomposed")).not.toBeInTheDocument();
```
- [ ] **Step 2: Run the title-beat test and verify it fails**
- [x] **Step 2: Run the title-beat test and verify it fails**
Run:
@@ -63,7 +63,7 @@ pnpm --dir web --filter @lda/console test -- src/presentation/opening/OpeningThe
Expected: FAIL because the main heading is currently `Thesis` and the agent
roles retain the old `AI agent components` label.
- [ ] **Step 3: Write failing contribution-beat assertions**
- [x] **Step 3: Write failing contribution-beat assertions**
```tsx
render(<OpeningThesisScene scene={thesisScene} beat={findBeat("thesis", "substrate")!} />);
@@ -77,7 +77,7 @@ expect(screen.getByText("Planner")).toBeInTheDocument();
expect(screen.getByText("Tool surface")).toBeInTheDocument();
```
- [ ] **Step 4: Run the contribution-beat test and verify it fails**
- [x] **Step 4: Run the contribution-beat test and verify it fails**
Run:
@@ -88,7 +88,7 @@ pnpm --dir web --filter @lda/console test -- src/presentation/opening/OpeningThe
Expected: FAIL because the current label is `Workflow Platform` and no
`Implemented contribution` scope exists.
- [ ] **Step 5: Implement the semantic opening composition**
- [x] **Step 5: Implement the semantic opening composition**
Replace the old title-card strings and decomposition labels with this structure:
@@ -134,7 +134,7 @@ Keep `scene.evidencePointer` after the section. If `ConceptNode` needs to
accept multi-line metadata, change its `children` wrapper to retain nested
content without changing its behavior in Scene 2.
- [ ] **Step 6: Run the focused tests and verify they pass**
- [x] **Step 6: Run the focused tests and verify they pass**
Run:
@@ -145,7 +145,7 @@ pnpm --dir web --filter @lda/console test -- src/presentation/opening/OpeningThe
Expected: PASS. Scene 1 tests enforce the new title and contribution wording;
Scene 2 integration assertions remain unchanged.
- [ ] **Step 7: Commit the semantic composition**
- [x] **Step 7: Commit the semantic composition**
```powershell
git add web/apps/console/src/presentation/opening/OpeningThesisScene.tsx web/apps/console/src/presentation/opening/OpeningThesisScene.test.tsx
@@ -164,7 +164,7 @@ git commit -m "feat: reframe presentation opening as agent roles"
- Produces: distinct title and contribution layouts controlled solely by
`data-opening-focus`.
- [ ] **Step 1: Add a failing structural assertion for the connected system**
- [x] **Step 1: Add a failing structural assertion for the connected system**
```tsx
const roles = screen.getByRole("group", { name: "AI agent roles" });
@@ -172,7 +172,7 @@ expect(roles).toHaveClass("opening-thesis__agent-system");
expect(roles.querySelectorAll("[data-concept-emphasis]")).toHaveLength(3);
```
- [ ] **Step 2: Run the test and verify it fails**
- [x] **Step 2: Run the test and verify it fails**
Run:
@@ -183,7 +183,7 @@ pnpm --dir web --filter @lda/console test -- src/presentation/opening/OpeningThe
Expected: FAIL because Scene 1 currently uses the generic concept rail class
without a Scene 1 system hook.
- [ ] **Step 3: Implement Scene 1-specific layout rules**
- [x] **Step 3: Implement Scene 1-specific layout rules**
Add `className="opening-thesis__agent-system"` to the Scene 1 `ConceptRail`.
Replace the existing `.opening-thesis` and `.opening-thesis__title-card` block
@@ -247,7 +247,7 @@ role. It may use cyan text and a solid stage-surface background, but the planner
and tool roles remain connected context rather than dimmed generic cards. Add a
`prefers-reduced-motion` override matching the existing presentation rules.
- [ ] **Step 4: Run the focused tests and typecheck**
- [x] **Step 4: Run the focused tests and typecheck**
Run:
@@ -258,7 +258,7 @@ pnpm --dir web --filter @lda/console typecheck
Expected: PASS with no TypeScript errors.
- [ ] **Step 5: Capture both 720p opening beats and inspect them**
- [x] **Step 5: Capture both 720p opening beats and inspect them**
Run:
@@ -273,7 +273,7 @@ Expected: the first screenshot has `An AI Agent for Workspace Workflows` as its
largest text; the second makes `Runner / platform` clearly dominant without
clipping the formal title, footer, or role labels.
- [ ] **Step 6: Commit the visual system**
- [x] **Step 6: Commit the visual system**
```powershell
git add web/apps/console/src/presentation/opening/OpeningThesisScene.tsx web/apps/console/src/presentation/opening/OpeningThesisScene.test.tsx web/apps/console/src/presentation/presentation.css
@@ -292,7 +292,7 @@ git commit -m "style: connect presentation opening agent roles"
- Produces: a roadmap that accurately marks the Scene 1 title slice complete
and retains the separate rehearsal slice as next work.
- [ ] **Step 1: Update the roadmap entry**
- [x] **Step 1: Update the roadmap entry**
Replace the current Scene 1 next-slice wording with:
@@ -304,7 +304,7 @@ Replace the current Scene 1 next-slice wording with:
[`presentation opening title`](historical/superpowers/plans/2026-07-11-presentation-opening-title.md).
```
- [ ] **Step 2: Run the full web verification suite**
- [x] **Step 2: Run the full web verification suite**
Run:
@@ -318,7 +318,7 @@ git diff --check
Expected: all workspace tests, typechecks, and builds pass. The existing Vite
chunk-size warning may remain; do not change bundle configuration in this slice.
- [ ] **Step 3: Archive the completed plan and commit documentation**
- [x] **Step 3: Archive the completed plan and commit documentation**
```powershell
Move-Item docs/superpowers/plans/2026-07-11-presentation-opening-title.md docs/historical/superpowers/plans/2026-07-11-presentation-opening-title.md