- add sect 11 correction lenses: three meanings of zero usage,
residue-vs-workflow (branches are core SDD scaffolding, stale
branches are cleanup debris), no incumbent surface-shape
inheritance (alkcall ACL model, not gitea's anonymous OpenAPI),
workarounds are unmet-need signals, the primary user (the SDD
workflow) is invisible to telemetry; 0.1 = day-to-day replication,
gitea catalog is a selective long-term backlog
- re-bucket: branching load-bearing (was inertia residue); stale
branches deferred as per-branch migration decisions
- new finding (owner-stated): push-mirrors to GitHub for all public
OSS repos, currently half-implemented with a plaintext PAT on
gitea; alkforge posture = alkvault reference + assembly-layer
bearer injection (alkhttp precedent); migration step added
(enumerate + rotate, never copy); new OQ-FG-11 seeds the 0.1
scope question
- clarify why issues/PRs/wiki/CI were unused: in-session workflows
and distrust of gitea, not no-need-forever
glm-5.3-flash
92519fa0c9