# Requirements Checklist: Spec 413 - Focused Pilot Gate Recheck

**Purpose**: Preparation readiness checklist for a read-only focused pilot gate recheck after Spec 412.
**Feature**: `specs/413-focused-pilot-gate-recheck/`
**Created**: 2026-06-24

## Applicability And Low-Impact Gate

- [x] The selected candidate was directly provided by the operator as Spec 413.
- [x] The active candidate queue in `docs/product/spec-candidates.md` was checked and has no automatic next-best-prep target.
- [x] Manual promotion is justified by the supplied candidate and the Spec 407 -> Spec 412 -> Spec 413 sequence.
- [x] No existing `specs/413-focused-pilot-gate-recheck/` package existed before this prep.
- [x] Related completed context was checked: Spec 407 is read-only audit context and Spec 412 contains completed tasks/implementation report.
- [x] Completed specs are preserved and not rewritten.
- [x] The scope is read-only and focused, not a full browser audit.
- [x] No application implementation or test-file change is planned or allowed.

## Product Surface Contract

- [x] Product Surface Contract is referenced as the evaluation lens.
- [x] Product Surface Impact records `N/A - no rendered product surface changed`.
- [x] Browser proof is required because the future gate output is browser/runtime evidence.
- [x] Human Product Sanity is planned for the final gate report.
- [x] Product Surface exceptions are `none` for preparation.
- [x] Final report requirements include Livewire v4 compliance, provider registration location, global search posture, destructive/high-impact action posture, asset strategy, tests/browser result, deployment impact, visible complexity outcome, and completed-spec rewrite assertion.

## Scope And Requirements

- [x] The problem statement is clear: verify whether Spec 412 actually closed Spec 407 pilot-readiness blockers.
- [x] User value is clear: provide PASS, PASS WITH CONDITIONS, or FAIL before Spec 414 controlled pilot preparation.
- [x] Functional requirements cover management PDF surfacing, report/PDF state agreement, signed/unsigned report behavior, OperationRun load, finding hash demotion, readonly provider no-access, focused regression checks, and final report structure.
- [x] Out-of-scope boundaries forbid fixes, tests, migrations, runtime data mutation, full audit, new surfaces, and completed-spec rewrites.
- [x] Acceptance criteria and success criteria are measurable.
- [x] Assumptions and risks are explicit.
- [x] No open question blocks safe read-only gate execution.

## RBAC, Isolation, Auditability, And Truth Semantics

- [x] Workspace and managed-environment entitlement checks are included.
- [x] Unauthorized and cross-workspace report/PDF probes are included.
- [x] Signed/unsigned report boundaries are included.
- [x] OperationRun authorization checks are included.
- [x] Provider readonly and authorized comparison checks are included.
- [x] Customer-safe output and internal technical detail demotion are included.
- [x] Report/PDF artifact truth, execution truth, customer-safe truth, and provider boundary truth are distinguished.
- [x] No audit log writes or runtime mutations are introduced.

## Tasks Quality

- [x] `tasks.md` exists.
- [x] Tasks are ordered by execution phase.
- [x] Tasks are small and verifiable.
- [x] Tasks include baseline/dirty-state capture.
- [x] Tasks include Spec 412 implementation-report inspection.
- [x] Tasks include route/fixture probe before browser work.
- [x] Tasks include required matrices and final gate decision.
- [x] Tasks include no-implementation and no-completed-spec-rewrite assertions.
- [x] Tasks do not require application code, tests, migrations, seeders, factories, routes, policies, views, config, assets, or runtime data changes.

## Test Governance

- [x] Test purpose is classified as Browser/read-only audit evidence.
- [x] No new or modified tests or test family are planned.
- [x] Existing tests may be run only as validation commands with exact results.
- [x] Fixture/helper/factory/seed cost remains none.
- [x] Browser proof is focused and does not claim full browser audit coverage.
- [x] Missing fixtures or actors must be recorded as limitations, not pass evidence.

## Review Outcome

- **Outcome class**: acceptable-special-case.
- **Workflow outcome**: keep.
- **Reason**: The package is a bounded read-only gate after a completed remediation spec, with no runtime changes and explicit completed-spec protections.

## Candidate Selection Gate

**PASS**. The candidate is directly provided, not already covered by an active/completed Spec 413 package, aligned with the roadmap path toward controlled pilot preparation, scoped as a small focused gate, and preserves Spec 407/412 history.

## Spec Readiness Gate

**PASS FOR IMPLEMENTATION PREPARATION**. `spec.md`, `plan.md`, `tasks.md`, and this checklist exist and are aligned for a later read-only gate execution.