You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
G00 — Reset repository governance and provenance #108
Every planning link, backlog issue record, and product identity string resolves to its intended target after the loop2 → loop rename.
Owner
Repository maintainers. This is repository governance, not a product module.
Entry dependencies
None.
Exit gate
No dead or number-colliding issue references remain in issues, overlays, docs, or the roadmap, and product name, identifiers, version, and default branch are decided on the exact head.
The roadmap intake sources and pending architecture proof obligations have reviewed ownership/disposition registers (#209 and #210).
studio-berry/loop2 now serves as studio-berry/loop, and the legacy repository is no longer visible under studio-berry. Legacy issue numbers overlap this suite's 1–104 range, so a bare number can silently resolve to an unrelated issue.
Sources
Approved master roadmap §2 and §6.1 · Gap review of the issue suite against the approved roadmap, 2026-09-27.
Implementation head: 78f9c0bce909bca7f95cc5b6c701043e61332087. The required check-change gate passed using the existing build with identical plugin ABI inputs. 117 Python cases and the mapped ABI test passed; one optional PdfTool runtime case skipped. Hosted CodeQL checks passed at this head; the native CI build is still running. Full package qualification remains pending. This record does not grant release admission.
Activity
Merge pull request #262 from studio-berry/chore/g00-governance