Files
linuxcncWebWASM/docs/linuxcnc-web-wasm-release-remediation-intake.md

38 lines
2.1 KiB
Markdown

# K8 Release Remediation Intake
`coverage/release-remediation-intake.report.json` is the deterministic intake
for K8-REL-07. It consumes the frozen K8 closeout, post-release audit, release
gate, closure, evidence index and context lock. Regenerate it with:
```bash
python3 scripts/generate_release_remediation_intake.py
```
The intake verifies the source hashes, context identity, blocker identity and
owner/evidence fields before creating six ordered work items (`K8-REL-08` to
`K8-REL-13`). Each item remains `blocked` until its accountable owner supplies
the required evidence and its review trigger is satisfied. Intake completion
therefore means that remediation is traceable; it does not mean that any
release prerequisite is accepted.
The release conclusion remains `blocked_not_release_candidate` with
`release_action: STOP_RELEASE` and `candidate_eligible: false`. The intake
does not alter the ABI, protocol, schema versions, context lock, manifest
classification, license decision, or any prior evidence. Missing inputs,
hash drift, context drift, deleted samples, lowered checks, `REAL-EXCLUDED`
reclassification and promotion of blocked entries all remain stop conditions.
The six work items are ordered by the audit's stable blocker order:
| Task | Blocker | Required owner action |
|---|---|---|
| `K8-REL-08` | `manifest_seed_unassigned` | Assign feature owners to all `needs_owner` seeds and regenerate the index |
| `K8-REL-09` | `accepted_entries_missing` | Produce acceptance evidence for eligible entries |
| `K8-REL-10` | `official_oracle_missing` | Add locked official kinematics/recovery oracle inputs and rerun comparisons |
| `K8-REL-11` | `configuration_resources_missing` | Resolve missing/unindexed resources without dropping rows |
| `K8-REL-12` | `browser_matrix_unverified` | Pin Chromium, Firefox and Safari minimums and execute checks |
| `K8-REL-13` | `license_closure_incomplete` | Approve SPDX/NOTICE metadata for the 57 Web/WASM entries |
Each follow-up task must regenerate the release closure, post-release audit,
milestone closeout and intake before it can change the release conclusion.