TenantAtlas/specs/363-explicit-uiactioncontext-contract/checklists/requirements.md

Requirements Checklist: Spec 363 - Explicit UiActionContext Contract for Scoped No-Record Actions

Purpose: Preparation analysis for Spec 363 readiness Created: 2026-06-07 Feature: /Users/ahmeddarrazi/Documents/projects/wt-plattform/specs/363-explicit-uiactioncontext-contract/spec.md

Candidate Selection And Guardrails

• CHK001 The candidate source is explicit: the direct user-provided Spec 363 draft from /Users/ahmeddarrazi/.codex/attachments/36f3aea8-0303-4548-a83c-9f1cdd15f527/pasted-text.txt.
• CHK002 No specs/363-* package existed before Spec Kit branch creation.
• CHK003 No existing 363-* branch was found before Spec Kit branch creation.
• CHK004 The active candidate queue's empty-state note is respected; this package is an intentional manual promotion, not an auto-selected queue item.
• CHK005 Related completed specs were checked and treated correctly: Specs 338, 340, 358, 359, 360, 361, and 362 remain historical/context packages and were not modified.
• CHK006 Repo-truth deviations from the user draft are recorded in spec.md, especially the explicit preparation boundary, no application implementation, and the guard that broader OperationRun authorization hardening becomes a follow-up only if repo-verified.

Required Prep Artifacts

• CHK007 spec.md exists and contains no template placeholders.
• CHK008 plan.md exists and is repo-aware.
• CHK009 tasks.md exists and is ordered, small, and verifiable.
• CHK010 This checklist exists.

Spec Quality

• CHK011 Spec Candidate Check is completed and scores above the approval threshold.
• CHK012 The spec explains why new request-time context classes and enums are justified under PROP-001 / ABSTR-001 / BLOAT-001.
• CHK013 The spec keeps scope bounded to scoped no-record action context, representative retrofits, first-click modal/no-run tests, and a static recurrence guard.
• CHK014 The spec keeps OperationRun, RBAC, policies, migrations, panel providers, assets, routes, capabilities, and global search unchanged unless a later implementation proves a blocker and updates artifacts first.
• CHK015 The spec preserves record-backed action context as a valid source and does not force broad record action churn.

Plan / Task Alignment

• CHK016 The plan identifies actual repo surfaces likely to change, including UiEnforcement, ResolvesPanelTenantContext, representative Filament action classes, and test/guard files.
• CHK017 The plan keeps Filament v5 / Livewire v4 posture and provider-registration location visible.
• CHK018 The plan explicitly states no migration, no new panel/provider, no global-search change, and no new asset strategy are expected.
• CHK019 The tasks start with repo truth and failing tests before runtime edits.
• CHK020 The tasks include anti-creep guardrails against compatibility shims, OperationRun redesign, product-feature expansion, and broad record-backed action migration.
• CHK021 The tasks include final validation and close-out requirements.

UI / Action Lifecycle Coverage

• CHK022 UI Surface Impact is completed and classifies existing action/page behavior changes without claiming a new page family.
• CHK023 Dangerous/high-impact action implications are explicit: destructive/high-impact actions keep confirmation, authorization, audit, and tests.
• CHK024 First-click modal mount and modal-no-run/no-job behavior are explicit acceptance criteria and tasks.
• CHK025 Missing-context UX is distinct from permission denial and avoids low-level Livewire/Filament copy.
• CHK026 OperationRun start behavior is limited to submit/execute and reuses existing OperationRun UX helpers.

Test Governance

• CHK027 The declared test families are the narrowest honest proof: Unit + Feature/Filament-Livewire + Architecture/guard; Browser optional only if visible hierarchy/copy changes materially.
• CHK028 Planned validation commands are explicit and scoped to Spec 363 plus directly related existing action tests.
• CHK029 No heavy-governance, PGSQL-only schema, or browser family is introduced by default.
• CHK030 Shared test helper growth is bounded and justified only if it reduces duplication across at least two retrofitted actions.

Filament v5 Blueprint Output Contract

• CHK031 Livewire v4.0+ compliance is stated in spec.md, plan.md, and tasks.md.
• CHK032 Provider registration location remains apps/platform/bootstrap/providers.php; no provider change is planned.
• CHK033 No globally searchable resource is added or changed; global search behavior remains unchanged.
• CHK034 Destructive/high-impact action confirmation + authorization handling is explicitly preserved.
• CHK035 Asset strategy remains unchanged; no new asset registration or filament:assets deployment impact is expected from this spec.
• CHK036 Testing plan names Filament/Livewire action tests, static guard tests, and optional Browser smoke boundary.

Readiness Gate Outcome

• CHK037 Candidate Selection Gate passes.
• CHK038 Spec Readiness Gate passes.
• CHK039 Runtime implementation has not started in this preparation step.
• CHK040 Recommended next step is implementation, not more prep.

Review Outcome

• CHK041 Outcome class: acceptable-special-case
• CHK042 Workflow outcome: keep
• CHK043 Final note location: active feature PR close-out entry Guardrail / Smoke Coverage
• CHK044 Preparation analyze result: pass via repo-based cross-artifact review; no standalone local speckit.analyze generator command was exposed in this repo surface beyond prompts and agent instructions.
• CHK045 Tooling note: Spec Kit branch/spec creation succeeded via create-new-feature.sh, setup-plan.sh generated the plan file, and tasks.md plus this checklist were authored manually to match the repo's Spec Kit templates and agent instructions.