WO-036 / HIVE-REL-013: v1.0.4 one-pass Windows installation, automatic D:/Projects onboarding and release #170

Status

OWNER-REQUESTED PLANNED release closure, not yet implemented or published. One comprehensive Codex Desktop execution prompt should complete existing WO-032 first, then implement compatible installer/discovery fixes, validate the exact runtime and release 1.0.4 if all gates pass. The user explicitly requested a single extended execution instead of many administrative corrective rounds. Source of truth remains actual Git and canonical Project Brain.

Linked active work

• Existing WO-032 runtime qualification: WO-032: qualify and repair Codex Desktop local HIVE runtime #163, unpublished local candidate reported at 78c466b9e984931c52f0bad62fe4a04931828f5d; prior index/corpus belong to older HEAD and do not qualify the current checkout.
• Windows-mounted Git timeout and mode-160000 gitlink fix: HIVE-FV-001: fix Git index timeout and gitlink handling on Windows-mounted Fairview #168; coordinate and avoid duplicate simultaneous code writers.
• Hive Coder special mount: HCODER-WO-0027-HIVE-UNBLOCK-001 — authorize narrow local read-only mount #166 and Draft PR docs: govern narrow local HIVE mount for HCODER-WO-0027 #167 / WO-035; distinct work, do not merge blindly or mutate the same Compose/registry/index/corpus in parallel. It touches two reviewer files also modified locally by WO-032.
• Last observed protected main b7f5bd8a9c9c1737c64412ebe481c9a70d9ecfc5, published stable tag v1.0.3; fresh preflight overrides this observation.

Objective and classification

NECESSARY patch-line, backward-compatible operational repair of v1.0.3 advertised local Windows install/auto-discovery. The owner should install HIVE once globally on Windows with normal Docker Desktop + Git prerequisites, default project root D:/Projects and durable data root D:/HIVE (or explicitly selected separate secondary-disk path). Thereafter, creating a valid Git project D:/Projects/<project-name> with first commit shall trigger automatic safe registration/index/retrieval and Control Center visibility, without per-project configuration, duplicate physical identities, ad-hoc nested Docker bind mounts, copying UUIDs, or manual maintenance prompts. Backward compatibility with v1.0.3 APIs and data is mandatory. If a requested item genuinely breaks patch SemVer, separate its optional 1.1 part but do not omit the operational repair.

Required repairs

1. Close WO-032: qualify and repair Codex Desktop local HIVE runtime #163 safely: correlate actual API/PostgreSQL restart records and isolate other writers; use the MCP structured UUID and REST from the same runtime; verify exact host/container project path, restore-tested current backup; only then use one remaining verified official index retry (unless auto-discovery already completed the exact HEAD) and one lexical sync only if necessary. Historic incident C5 attribution remains UNKNOWN without primary logs.
2. Owner's new explicit bounded authorization: if and ONLY if required after a verified fresh lexical corpus, execute at most one qualified, idempotent local semantic sync using the already configured Ollama embedding profile; dedup/rebind compatible existing vectors first, measure and justify any genuinely missing vectors and bounded provider calls. Never cloud provider, unbounded retry, manual CURRENT, destructive rebuild or historical evidence deletion. This narrowly supersedes the earlier WO-032 prohibition on additional semantic sync; preserve the original record.
3. Repair/install scripts/hive_install.py, effective Compose mount verification (not just declared config), safe idempotent fresh/repair/upgrade separation, Windows global CLI and user-friendly doctor/status/repair, reversible user-scope startup behavior. Do not silently reinstall over nonempty durable state or commit .env/keys.
4. Auto-discover only safe immediate child Git repositories under D:/Projects after first commit; debounce incomplete Git operations, detect HEAD and content/inventory changes, per-project idempotency/backoff, cross-process/project lock, restart recovery, errors and truthful fleet progress. Avoid scans that repeatedly create failed runs for unchanged bad projects.
5. Include HIVE-FV-001: fix Git index timeout and gitlink handling on Windows-mounted Fairview #168 Git timeout bounded configuration and gitlink/submodule-safe fingerprint/index behavior if not already independently accepted. Add tests proving Windows-mounted slow Git, negative security cases and zero cross-project regression.
6. Real Windows Docker Desktop fresh ZIP install, existing v1.0.3 upgrade with restore-tested backup, two new Git projects, restarts, old project preservation, MCP UUID round-trip, Control Center, 10-query accepted benchmark (recall@5 >= .9, MRR >= .8, zero critical misses/leaks/stale), complete backend/frontend validation and protected CI evidence.
7. Version and publish via current docs/VERSIONING.md, docs/RELEASING.md and release publisher: exact-head owner self-audit NOT INDEPENDENT, required Validate/Integration health/Review Evidence, security CodeQL and Dependency Review as applicable, zero unresolved HIGH/CRITICAL, squash-only protected main, mandatory post-merge CI, fresh security triage, release request lineage, immutable annotated v1.0.4 tag, ZIP/SHA256/manifest/review bundle and final release receipt. Never claim release before these exist.

Governance simplification explicitly approved

The user authorized eliminating repeated administrative and sequencing deadlocks within the consolidated single execution. Keep B1 local prereq checks distinct from B2 PR-specific hosted checks; allow the executor to diagnose, fix and retest authorized technical defects in the same long run, and create sequential governed PRs within the same prompt. This does not authorize bypassing protected main, code review evidence, safety checks, backup/rollback or evidence-based completion. Where current allowlists/registries block this expressly approved scope, amend them visibly with negative regression tests instead of weakening fail-closed defaults. The owner is the sole account KayzenRoot; no self-native-APPROVE on authored PR.

Start/stop

Do not begin implementation of a separate release PR until WO-032 qualification passes; one long prompt can finish both phases in order. Stop only for actual irrecoverable safety/identity/privilege/external-access blockers or unresolved severe bugs, report the smallest precise handoff; never manufacture 100% status. Objective completion requires verified global onboarding on the real Windows machine and published, checksum-verified v1.0.4 release. This issue is planning/authorization, not proof of implementation.