Skip to content

Completion Report: ANU-9 - Register and Bootstrap the Anuva Bento Repository

Status: Ready for guarded Product Main merge; implementation is verified, the Bento bootstrap is merged, and the branch-protection limitation is accepted.

Delivered scope

  • Created the private independent downstream and preserved public Bento ancestry, release tags, MIT license, copyright, and third-party notices.
  • Recorded Bento v1.0.8 at 0c9600d220668a6f447bbd2edf3567558b3652ea and verified the unmodified baseline before the first Anuva-authored file.
  • Registered anuva-bento in Product Main's closed repository allowlist, publisher map, safe configuration, machine configuration, tests, architecture, workflow, and development-preview documentation.
  • Installed the normal Anuva issue, review, maintenance, and documentation skills plus repository instructions, prompts, templates, strict MkDocs, and durable bootstrap evidence in the downstream.
  • Verified the Linear repository label, Bento CLI context, port 4005 preview, bento1.girishd.com route, Cloudflare Access challenge, and a safe upstream synchronization rehearsal.
  • Expanded the approved ANU-8 implementation manifest and ran the eight-child dependency graph in dry-run mode only. No downstream Linear issue was created.
  • Made no Bento product behavior change.

Verification

Area Result
Product Main typecheck and full Bun suite Passed; 56 tests, 173 expectations, 0 failures
Product Main strict docs, recursive index validation, and diff checks Passed
Upstream npm ci and normal Vite build Passed; 0 reported vulnerabilities
Upstream synchronization test Passed; 45,362 checks
Windows-equivalent single-file build Passed; 593,771-byte artifact
Downstream CLI context and six skill validations Passed
Downstream strict MkDocs/index validation and exact HTTPS preview Passed
Remote tag/main/ref comparison and disposable sync rehearsal Passed
Linear label read-back Passed; exactly one anuva-bento child of Repository
Cloudflare route and Access Passed; authenticated HTTP 200 and unauthenticated Access redirect
Expanded implementation manifest dry run Passed; no issues created
Installed launcher and Product Main/Bento context resolution Passed
Anuva doctor repository/authentication checks Passed; overall command reports local PostgreSQL stopped, unrelated to ANU-9

Accepted limitation

GitHub returned HTTP 403 when ANU-9 attempted to protect main in the private downstream: private-repository branch protection requires a higher organization plan. The downstream documents PR-only delivery and prohibits force pushes and branch deletion, but those controls are policy rather than technical enforcement.

Girish explicitly accepted this recorded limitation for ANU-9 on 2026-07-24. Repository visibility will not be changed as a workaround. The PR-only, no-force-push, and no-deletion policy remains normative until server-side protection becomes available.

The proposed local pre-push hook is a reasonable defense against accidental pushes from a configured clone. It is not equivalent protection: Git hooks are clone-local and git push --no-verify bypasses pre-push. ANU-9 therefore records it as a possible separately reviewed safeguard rather than claiming it as remote branch protection.

For this solo-developer workflow, Girish's explicit approval in the interactive Codex task is the human review boundary. The Anuva merge guard independently enforces the reviewed PR shape, mergeability, absence of blocking requested changes, passing configured checks, exact head SHA, clean worktree, and validated completion evidence.

Recovery state

  • The one-time mirror import is complete and must not be repeated.
  • origin is the private downstream; upstream is the public source with push disabled locally.
  • Product Main and downstream work remain isolated on review branches.
  • The expanded Linear manifest is idempotent and has not been confirmed.
  • The parent ANU-8 remains In Progress.

Ready-to-merge declaration

Ready for the guarded Product Main merge. Bento PR #1 is merged and cleaned up, all implementation checks pass, the limitation decision is recorded, and Girish approved the ANU-9 merge sequence.