Main Confidence / confidence (push) Failing after 44s

Details

spec: finalize 223 AstroDeck rebuild planning consistency (#262 )

## Summary
- finalize Spec 223 planning artifact set for AstroDeck website rebuild
- align `spec.md`, `plan.md`, `tasks.md`, `research.md`, `data-model.md`, `quickstart.md`, and contract schema
- add/complete inventory, mapping, exception, drift-follow-up, and supersession artifacts
- mark legacy website-spec task references as superseded and wire follow-up ownership

## Key Outcomes
- no remaining cross-artifact consistency findings in the Spec 223 bundle
- explicit Spec 213 handling path added
- material-drift follow-up rules normalized
- exception register and documented exception model made explicit and schema-backed

## Validation
- Integrated browser smoke check passed for main website routes (`/`, `/product`, `/trust`, `/changelog`, `/contact`, `/privacy`, `/imprint`, `/legal`, `/security-trust`)
- no console errors/warnings observed during route smoke navigation
- YAML contract parses successfully

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #262

2026-04-22 07:52:32 +00:00

16 KiB

Raw Blame History

Tasks: Website Reset and AstroDeck Rebuild

Input: Design documents from /specs/223-astrodeck-website-rebuild/
Prerequisites: plan.md, spec.md, research.md, data-model.md, quickstart.md, contracts/rebuild-planning-artifacts.yaml

Tests: N/A - docs-only planning feature. This slice adds no runtime behavior, so no automated test tasks are required here. Follow-up implementation slices own corepack pnpm build:website and cd apps/website && corepack pnpm exec playwright test.

Test Governance Checklist

Lane assignment is N/A because this feature changes planning artifacts only.
No runtime or browser test family is added in this slice.
No new helpers, fixtures, seeds, or shared defaults are introduced.
Runtime proof remains explicitly deferred to follow-up website implementation slices.
The governance outcome stays documented in-feature rather than becoming a separate cleanup item.

Phase 1: Setup (Shared Infrastructure)

Purpose: Create the planning workspace files that the inventory, classification, mapping, and exception workflow will use.

T001 Create the current-site and AstroDeck inventory stubs in specs/223-astrodeck-website-rebuild/current-website-inventory.md, specs/223-astrodeck-website-rebuild/astrodeck-source-intake.md, and specs/223-astrodeck-website-rebuild/astrodeck-primitive-inventory.md
T002 [P] Create the governing-spec, legacy-task disposition, and material-drift follow-up stubs in specs/223-astrodeck-website-rebuild/governing-website-spec-classification.md, specs/223-astrodeck-website-rebuild/legacy-task-disposition.md, and specs/223-astrodeck-website-rebuild/material-drift-follow-up.md
T003 [P] Create the per-spec mapping workspace and exception stub in specs/223-astrodeck-website-rebuild/exception-register.md, specs/223-astrodeck-website-rebuild/mappings/spec-213-website-foundation-v0.md, specs/223-astrodeck-website-rebuild/mappings/spec-214-website-visual-foundation.md, specs/223-astrodeck-website-rebuild/mappings/spec-215-website-core-pages.md, specs/223-astrodeck-website-rebuild/mappings/spec-217-homepage-structure.md, and specs/223-astrodeck-website-rebuild/mappings/spec-218-homepage-hero.md

Phase 2: Foundational (Blocking Prerequisites)

Purpose: Establish the shared baseline, intake rules, and crosswalk logic that every user story depends on.

⚠️ CRITICAL: No user story work should begin until this phase is complete.

T004 Capture the current route, content, component-family, and smoke-suite baseline in specs/223-astrodeck-website-rebuild/current-website-inventory.md
T005 [P] Record AstroDeck source provenance, intake constraints, and review assumptions in specs/223-astrodeck-website-rebuild/astrodeck-source-intake.md
T006 [P] Define the page, section, and component inventory columns plus demo-content flags in specs/223-astrodeck-website-rebuild/astrodeck-primitive-inventory.md
T007 Build the shared crosswalk from current website surfaces to Specs 213, 214, 215, 217, and 218 in specs/223-astrodeck-website-rebuild/governing-website-spec-classification.md

Checkpoint: The planning workspace, current-site baseline, AstroDeck intake rules, and governing-spec crosswalk are in place. Story work can now proceed.

Phase 3: User Story 1 - Start Rebuild Work From One Visible Substrate (Priority: P1) 🎯 MVP

Goal: Make the retired current website and the new AstroDeck substrate visible side by side so future work starts from the right base.

Independent Test: A reviewer can open the current-site inventory and AstroDeck inventory documents and see that the old apps/website implementation is historical context while forward work starts from identified AstroDeck pages, sections, and components.

Implementation for User Story 1

T008 [P] [US1] Complete the current website surface inventory with route roles, source files, dependencies, and initial keep/adapt/remove/redirect candidates in specs/223-astrodeck-website-rebuild/current-website-inventory.md
T009 [P] [US1] Complete the AstroDeck primitive inventory with page, section, and component candidates plus demo-content flags in specs/223-astrodeck-website-rebuild/astrodeck-primitive-inventory.md
T010 [US1] Reconcile the current-site baseline with the AstroDeck intake summary so the forward substrate is explicit in specs/223-astrodeck-website-rebuild/astrodeck-source-intake.md, specs/223-astrodeck-website-rebuild/current-website-inventory.md, and specs/223-astrodeck-website-rebuild/astrodeck-primitive-inventory.md

Checkpoint: The rebuild now has one visible implementation substrate and a clear retired baseline.

Phase 4: User Story 2 - Preserve Old Task History While Creating a New Forward Plan (Priority: P1)

Goal: Keep legacy website task history readable while producing AstroDeck-specific replacement planning for the continuing website specs.

Independent Test: A reviewer can inspect the classification and legacy-task artifacts and then open the per-spec mapping sheets to see which old tasks were superseded and which new AstroDeck-specific task lists now own delivery.

Implementation for User Story 2

T011 [US2] Classify Specs 213, 214, 215, 217, and 218 as continuing, partially valid, or superseded and record the classification rationale, scopeSummary, and followUpPlan reference for each spec in specs/223-astrodeck-website-rebuild/governing-website-spec-classification.md, including whether Spec 213 points to a dedicated rebuild plan in specs/223-astrodeck-website-rebuild/mappings/spec-213-website-foundation-v0.md
T012 [US2] Mark legacy implementation tasks as superseded by AstroDeck rebuild in specs/213-website-foundation-v0/tasks.md, specs/214-website-visual-foundation/tasks.md, specs/215-website-core-pages/tasks.md, specs/217-homepage-structure/tasks.md, and specs/218-homepage-hero/tasks.md, and summarize the replacement references in specs/223-astrodeck-website-rebuild/legacy-task-disposition.md
T013 [P] [US2] Create the Spec 213 disposition-or-rebuild mapping sheet, recording either a full AstroDeck plan with its embedded replacement task list naming the relevant AstroDeck page, section, component, or mapping activity or an explicit supersession closure, in specs/223-astrodeck-website-rebuild/mappings/spec-213-website-foundation-v0.md
T014 [P] [US2] Create the Spec 214 and Spec 215 disposition-or-rebuild mapping sheets, recording either full AstroDeck plans with embedded replacement task lists naming the relevant AstroDeck pages, sections, components, or mapping activities or explicit supersession closures, in specs/223-astrodeck-website-rebuild/mappings/spec-214-website-visual-foundation.md and specs/223-astrodeck-website-rebuild/mappings/spec-215-website-core-pages.md
T015 [P] [US2] Create the Spec 217 and Spec 218 disposition-or-rebuild mapping sheets, recording either full AstroDeck plans with embedded replacement task lists naming the relevant AstroDeck pages, sections, components, or mapping activities or explicit supersession closures, in specs/223-astrodeck-website-rebuild/mappings/spec-217-homepage-structure.md and specs/223-astrodeck-website-rebuild/mappings/spec-218-homepage-hero.md
T016 [US2] Cross-check the per-spec mapping sheets against the spec classifications, followUpPlan references, legacy-task replacements, and material-drift follow-up ledger in specs/223-astrodeck-website-rebuild/governing-website-spec-classification.md, specs/223-astrodeck-website-rebuild/legacy-task-disposition.md, specs/223-astrodeck-website-rebuild/material-drift-follow-up.md, specs/223-astrodeck-website-rebuild/mappings/spec-213-website-foundation-v0.md, specs/223-astrodeck-website-rebuild/mappings/spec-214-website-visual-foundation.md, specs/223-astrodeck-website-rebuild/mappings/spec-215-website-core-pages.md, specs/223-astrodeck-website-rebuild/mappings/spec-217-homepage-structure.md, and specs/223-astrodeck-website-rebuild/mappings/spec-218-homepage-hero.md

Checkpoint: Legacy work remains readable, and the forward-looking AstroDeck task ownership exists for every continuing website spec.

Phase 5: User Story 3 - Allow Bounded Exceptions Only When the Base Primitives Are Insufficient (Priority: P2)

Goal: Make custom non-AstroDeck work possible only through an explicit, scoped exception path.

Independent Test: A reviewer can inspect any custom-primitive proposal and see the failed AstroDeck search, the unmet spec requirement, the bounded deviation, and the approval reference without ambiguity.

Implementation for User Story 3

T017 [US3] Define the exception workflow, adequacy rubric, required evidence, approval boundary, and embedded documented-exception record shape for non-AstroDeck primitives in specs/223-astrodeck-website-rebuild/exception-register.md
T018 [P] [US3] Review the Spec 213, Spec 214, and Spec 215 mapping sheets for unmet requirements and record either approved exceptions or explicit no-exception outcomes in specs/223-astrodeck-website-rebuild/exception-register.md, specs/223-astrodeck-website-rebuild/mappings/spec-213-website-foundation-v0.md, specs/223-astrodeck-website-rebuild/mappings/spec-214-website-visual-foundation.md, and specs/223-astrodeck-website-rebuild/mappings/spec-215-website-core-pages.md
T019 [P] [US3] Review the Spec 217 and Spec 218 mapping sheets for unmet requirements and record either approved exceptions or explicit no-exception outcomes in specs/223-astrodeck-website-rebuild/exception-register.md, specs/223-astrodeck-website-rebuild/mappings/spec-217-homepage-structure.md, and specs/223-astrodeck-website-rebuild/mappings/spec-218-homepage-hero.md
T020 [US3] Add spread-control and acceptance-trace notes for every exception-backed or no-exception mapping in specs/223-astrodeck-website-rebuild/exception-register.md, specs/223-astrodeck-website-rebuild/mappings/spec-213-website-foundation-v0.md, specs/223-astrodeck-website-rebuild/mappings/spec-214-website-visual-foundation.md, specs/223-astrodeck-website-rebuild/mappings/spec-215-website-core-pages.md, specs/223-astrodeck-website-rebuild/mappings/spec-217-homepage-structure.md, and specs/223-astrodeck-website-rebuild/mappings/spec-218-homepage-hero.md

Checkpoint: The rebuild has a controlled exception path instead of a silent greenfield bypass.

Phase 6: Polish & Cross-Cutting Concerns

Purpose: Reconcile the finished planning artifacts with the contract, force explicit spec-update follow-up for material drift, and lock the handoff order for implementation slices.

T021 [P] Reconcile the completed inventory, classification, mapping, exception, and material-drift artifacts against specs/223-astrodeck-website-rebuild/contracts/rebuild-planning-artifacts.yaml and specs/223-astrodeck-website-rebuild/quickstart.md
T022 [P] Update the affected continuing website specs or create named follow-up website specs when material page inventory, CTA logic, navigation, or trust messaging drift is logged in specs/213-website-foundation-v0/spec.md, specs/214-website-visual-foundation/spec.md, specs/215-website-core-pages/spec.md, specs/217-homepage-structure/spec.md, specs/218-homepage-hero/spec.md, and specs/223-astrodeck-website-rebuild/material-drift-follow-up.md
T023 [P] Verify that superseded legacy-task markers and replacement references are visible from specs/213-website-foundation-v0/tasks.md, specs/214-website-visual-foundation/tasks.md, specs/215-website-core-pages/tasks.md, specs/217-homepage-structure/tasks.md, specs/218-homepage-hero/tasks.md, and specs/223-astrodeck-website-rebuild/legacy-task-disposition.md
T024 Record the final follow-up execution order for the AstroDeck inventory slice, the conditional Spec 213 slice, and the Spec 214/215/217/218 mapping slices, each already carrying its embedded replacement task list or supersession closure, in specs/223-astrodeck-website-rebuild/plan.md, specs/223-astrodeck-website-rebuild/quickstart.md, and specs/223-astrodeck-website-rebuild/governing-website-spec-classification.md

Dependencies & Execution Order

Phase Dependencies

Setup (Phase 1): Starts immediately.
Foundational (Phase 2): Depends on Setup and blocks all user stories.
User Story 1 (Phase 3): Depends on Foundational only.
User Story 2 (Phase 4): Depends on User Story 1 because the completed inventories from US1 are required before classification and mapping can start.
User Story 3 (Phase 5): Depends on the mapping sheets from US2.
Polish (Phase 6): Depends on all targeted user stories being complete.

User Story Dependencies

US1: MVP slice. No dependency on US2 or US3.
US2: Depends on US1 because the current-site and AstroDeck inventories must be complete before classification and mapping.
US3: Depends on the per-spec mapping sheets, including the conditional Spec 213 artifact, so exceptions can be evaluated against real candidate searches.

Within Each User Story

Establish or complete the relevant artifact first.
Record explicit dispositions before writing replacement task lists.
Link exceptions only after the mapping decision shows a real gap.
Finish each story’s cross-check task before moving to the next story.

Parallel Opportunities

T002 and T003 can run in parallel after T001.
T005 and T006 can run in parallel after T004 starts.
In US1, T008 and T009 can run in parallel before T010.
In US2, T013, T014, and T015 can run in parallel after T012.
In US3, T018 and T019 can run in parallel after T017.
In Phase 6, T021, T022, and T023 can run in parallel before T024.

Parallel Example: User Story 2

# First record legacy-task supersession after classification:
Task: "T012 [US2] Mark legacy implementation tasks as superseded"

# After legacy-task supersession is recorded, launch the per-spec planning artifacts in parallel:
Task: "T013 [US2] Create the Spec 213 disposition-or-rebuild mapping sheet"
Task: "T014 [US2] Create the Spec 214 and Spec 215 disposition-or-rebuild mapping sheets"
Task: "T015 [US2] Create the Spec 217 and Spec 218 disposition-or-rebuild mapping sheets"

# Then run the consistency pass:
Task: "T016 [US2] Cross-check the mapping sheets against the classification, legacy-task, and material-drift records"

Implementation Strategy

MVP First (User Story 1 Only)

Complete Phase 1: Setup.
Complete Phase 2: Foundational.
Complete Phase 3: User Story 1.
STOP and VALIDATE: Review the current-site and AstroDeck inventories together.
Use that MVP substrate view as the basis for the follow-up mapping work.

Incremental Delivery

Complete Setup + Foundational to establish the planning workspace.
Add US1 to make the rebuild substrate explicit.
Add US2 to preserve legacy history and produce forward AstroDeck task ownership.
Add US3 to harden the exception path.
Finish with Phase 6 to reconcile the artifacts and publish the handoff order.

Suggested MVP Scope

Deliver through User Story 1 if the smallest first slice is needed.
Add User Story 2 next to preserve task history and create per-spec forward plans.
Finish with User Story 3 to ensure custom work remains exception-bound.

Notes

[P] tasks touch different files or independent artifacts and can run in parallel once dependencies are satisfied.
[US1], [US2], and [US3] map directly to the user stories in spec.md.
This is a docs-only planning feature, so no runtime test tasks are included here.
The intended follow-up split after this feature is one AstroDeck inventory slice, a conditional Spec 213 slice, and per-spec mapping slices for Specs 214, 215, 217, and 218, with each per-spec artifact carrying its replacement task list or explicit supersession closure and with spec updates or follow-up specs when material drift is discovered.

16 KiB Raw Blame History Unescape Escape