2.9 KiB
Blockers
2 November 2026. Severity describes impact/gate importance, not an invented vulnerability rating.
| ID | Feature / description and known cause | Severity / dependency | Required action | Elsewhere / gate scope / status |
|---|---|---|---|---|
| B01 | P10 publication: Gitea pre-receive SIGSEGV rejected prior pushes | Mandatory checkpoint; external server fault | Normal push and exact readback | RESOLVED: remote 1692142295950e390a4cf807d9df86cc5cf96290; no server repair performed |
| B02 | P10-01 candidate approval absent; addendum explicitly retains this gate | Mandatory owner decision D01 | Approve/reject exact CLEAN-20 scope | Independent authorised planning allowed; blocks cleanup implementation; AWAITING_APPROVAL |
| B03 | Ordered roadmap implementation lacks accepted predecessor phases | Mandatory dependency | Complete/accept predecessors and stage-specific scopes | Explicitly independent planning allowed; blocks dependent development; BLOCKED |
| B04 | Physical device/AT/contrast/native-language/actual print qualification missing | Release qualification | Human review with actual evidence | Unaffected planning can proceed; production and affected acceptance; NOT_TESTED |
| B05 | Real CV-model compatibility/semantic quality unqualified; adapter withheld | High activation gate | Separately approve safe immutable model qualification; retain disabled state | Model-independent work allowed; AI activation/claims; BLOCKED |
| B06 | Hosted CI/isolation, production TLS/advisories, native parser/image isolation, backup/restore and deployed identity lack current qualification | High release gate; inherited evidence limits | Operator/isolated release evidence and scoped security disposition | Unrelated planning allowed; production; BLOCKED/NOT_TESTED by lane |
| B07 | SQLite retirement lacks complete transfer, restore, parity, cutover and retention evidence | High data-preservation gate | Separate approved staged retirement | Unrelated cleanup/planning allowed; SQLite removal; BLOCKED |
No material security risk or missing test is accepted by this register. Current dependency advisory status has not been refreshed; historical findings are not claims about a new scan. Additional source-specific entry decisions are recorded after eligibility review.
Execution interruption: the three delegated workers hit a service usage limit. Parent continued and published partial I18N, homepage and release discovery checkpoints. Remaining audit/context/legal/rendered work is IN_PROGRESS/PENDING, not falsely classified as an external blocker. Resume locations are in NEXT_ACTIONS.md. No workers are running in the background.
Security entry: the master prompt's DO NOT START THIS NOW! and feature-completion dependency remain unresolved; conflicting README immediate-review wording does not authorise a formal scan. No new vulnerability findings or material risk acceptance are claimed.