refactor: remove duplicate authoring scene
This commit is contained in:
@@ -0,0 +1,22 @@
|
||||
# Task 4 Report
|
||||
|
||||
## Status
|
||||
|
||||
Implemented in shared `main`; ready for commit as `refactor: remove duplicate authoring scene`.
|
||||
|
||||
## Changes
|
||||
|
||||
- Removed the obsolete `AuthoringScene` branch, local authoring steps, projection helper, and exclusive SceneBody authoring CSS.
|
||||
- Kept the approved Prepared Lifecycle six-step visual and exposed its migrated defense rail beneath the scene content.
|
||||
- Limited the discussion rail to Prepared Lifecycle among workflow-demo scenes; run, interrupt, and output proof scenes remain rail-free.
|
||||
- Renamed the Scene9 callback chain to `onPreparedLifecycleAdvance` and `handlePreparedLifecycleAdvance`.
|
||||
- Removed stale `authoring` route/test/presenter callers and retargeted the presenter notes to the six Prepared Lifecycle beats.
|
||||
|
||||
## TDD And Verification
|
||||
|
||||
- RED: the focused migration run failed with the expected stale authoring scene/rail/callback assertions.
|
||||
- GREEN: focused presentation tests passed: `5` files, `161/161` tests.
|
||||
- Console typecheck passed: `pnpm --dir web --filter @lda/console typecheck`.
|
||||
- `PresentationStage.test.tsx` named in the brief is not present in this checkout, so the focused run used the existing PresentationStage implementation coverage through route tests.
|
||||
|
||||
The broader presenter-note catalog test remains outside Task 4 scope and still expects the later Task 5 `architecture/node-use` note and timing ledger.
|
||||
Reference in New Issue
Block a user