ahmido
f24e72269c
## Summary - add the Spec 305 docs-only readiness gate package under `specs/305-feature-readiness-gate-audit/` - record a repo-based readiness audit after Specs 301-304 across workspace/admin runtime, environment-bound surfaces, legacy route retirement, governance, OperationRun links, evidence/reports, findings, reviews, RBAC, audit, navigation, and test lanes - document the final recommendation as `GO WITH CONDITIONS` - explicitly block a fresh greenfield `Decision Register & Approval Workflow v1` restart because repo truth already includes Spec 265 runtime and tests - capture the required follow-up: reconcile stale product queue docs or start a narrowly scoped follow-up that builds on existing Decision Register truth ## Scope - docs-only audit artifact plus Spec Kit files - no application runtime changes - no migrations - no UI or route changes - no test edits ## Key Conditions Recorded - do not create a duplicate fresh Decision Register v1 spec - reconcile stale `docs/product/implementation-ledger.md` and `docs/product/spec-candidates.md` before using them as queue truth - keep future work on canonical workspace/environment admin routes - split future artifact lifecycle or approval-mutation changes into explicit follow-up specs ## Filament / Runtime Notes - remains compliant with Filament v5 on Livewire v4 - no provider registration changes; provider registration location remains `apps/platform/bootstrap/providers.php` - no globally searchable resources were added or changed in this docs-only PR - no destructive actions were added or changed - no asset registration changes; existing deploy posture for `cd apps/platform && php artisan filament:assets` is unchanged ## Validation Notes - the audit artifact records the focused repo validation evidence used for the readiness decision - no new runtime validation was executed in this turn beyond committing and pushing the docs-only package Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #360
61 lines
3.1 KiB
Markdown
61 lines
3.1 KiB
Markdown
# Tasks: Feature Readiness Gate Audit
|
|
|
|
**Input**: Spec and plan from `/specs/305-feature-readiness-gate-audit/`
|
|
**Prerequisites**: Specs 301-304 are completed context and must remain read-only
|
|
|
|
## Format: `[ID] [P?] Description`
|
|
|
|
- **[P]**: Can run in parallel with other read-only inspection tasks
|
|
- Every task is docs-only unless explicitly listed as validation
|
|
|
|
## Phase 1: Setup
|
|
|
|
- [x] T001 Confirm current git branch and clean starting state before generating 305 artifacts.
|
|
- [x] T002 Read repo instructions, Constitution, Spec Kit templates, roadmap, and spec-candidate context.
|
|
- [x] T003 Create the 305 feature branch and initial Spec Kit plan/spec scaffold using repo scripts.
|
|
|
|
## Phase 2: Evidence Review
|
|
|
|
- [x] T004 [P] Review Specs 301-304 close-out notes and validation posture.
|
|
- [x] T005 [P] Review workspace/admin runtime provider registration and panel state.
|
|
- [x] T006 [P] Review environment-bound routes, tenant-owned resource traits, global search posture, and route retirement state.
|
|
- [x] T007 [P] Review OperationRun link and execution truth support.
|
|
- [x] T008 [P] Review governance inbox, Decision Register, findings/risk acceptance, evidence/stored report, review/review pack, RBAC, and audit/event foundations.
|
|
- [x] T009 [P] Identify relevant focused test lanes for Filament/navigation, governance, findings, evidence, reviews, OperationRun links, and legacy route retirement.
|
|
|
|
## Phase 3: Artifact Creation
|
|
|
|
- [x] T010 Replace the generated `spec.md` template with a docs-only readiness gate specification.
|
|
- [x] T011 Replace the generated `plan.md` template with a docs-only implementation plan.
|
|
- [x] T012 Create `tasks.md` for the docs-only audit workflow.
|
|
- [x] T013 Create `checklists/requirements.md` for the readiness artifact quality gate.
|
|
- [x] T014 Create `feature-readiness-audit.md` with the required repo-based matrix and GO / GO WITH CONDITIONS / NO-GO recommendation.
|
|
- [x] T015 Explicitly evaluate whether Decision Register & Approval Workflow v1 may start as the next feature spec.
|
|
|
|
## Phase 4: Validation
|
|
|
|
- [x] T016 Run focused legacy route/panel retirement tests from Specs 301-304 where practical.
|
|
- [x] T017 Run focused Filament/navigation/global-search tests from Specs 301-304 where practical.
|
|
- [x] T018 Run relevant Governance/Decision/Findings tests where practical.
|
|
- [x] T019 Run relevant Evidence/StoredReport/EnvironmentReview/ReviewPack tests where practical.
|
|
- [x] T020 Run relevant OperationRun link/legacy route tests where practical.
|
|
- [x] T021 Run `git diff --check`.
|
|
- [x] T022 Update `feature-readiness-audit.md` with validation outcomes.
|
|
|
|
## Phase 5: Close-Out
|
|
|
|
- [x] T023 Confirm `git status --short` is limited to `specs/305-feature-readiness-gate-audit/`.
|
|
- [x] T024 Confirm no application code, migrations, UI surfaces, or tests changed.
|
|
- [x] T025 Finalize the readiness recommendation and summarize residual conditions.
|
|
|
|
## Non-Goals Checklist
|
|
|
|
- [x] No runtime code changes.
|
|
- [x] No migrations.
|
|
- [x] No new UI surfaces.
|
|
- [x] No feature implementation.
|
|
- [x] No test edits.
|
|
- [x] No roadmap rewrite.
|
|
- [x] No Decision Register feature specification started.
|
|
- [x] No legacy compatibility reintroduced.
|