Repository navigation
HIVE-FV-001: fix Git index timeout and gitlink handling on Windows-mounted Fairview #168
Description
Narrow HIVE 1.0.x maintenance issue, cross-referenced from Fairview KayzenRoot/fairview#1. Evidence from local R5: project READY, index FAILED git_status_unavailable when Windows-mounted Git took 6.87s vs hardcoded 5s indexer cap; Fairview also contains a pinned GEF git submodule whose mode 160000 is currently rejected by HIVE indexer. Authorization sought for backwards-compatible bounded config (HIVE_REPOSITORY_GIT_TIMEOUT_SECONDS, default 30s, bounded 5..120), avoid recursive submodule status, ignore gitlink content while keeping gitlink SHA in fingerprint; focused tests for timeout/race/symlink/gitlink, CI and deployment docs. No migration, no provider keys, no operation on other user's local HIVE instance, no alteration of published v1.0.3 tag. Merge/publish only after required HIVE checks and authorized exact-head review; future Fairview pin must cite immutable accepted commit. This is source remediation only, not proof of user's Windows runtime.
Activity
KayzenRoot commentedon Sep 27, 2026
HIVE-FV-001 candidate status and governance boundary
The bounded indexer/giklink fix is in PR #169 at exact candidate SHA
2fbe0e6f5239c91d7ccae9e605a9f087f30ad095; its hosted Validate job in CI run36349473286passed (899 Python tests, dashboard checks, formatter/typecheck). Integration health is still in progress, and the upstream Review Evidence job may reject the newHIVE-FV-001PR marker becausescripts/review_evidence.pyhas an explicit fail-closed registry and does not recognize that identifier. This is a separate HIVE governance constraint; do not bypass it, relabel this PR as unrelated WO-032, auto-merge or invent a v1.0.4 release.Fairview's own narrow R6 PR #8 uses a SEPARATE
UNPUBLISHEDcandidate source lock for isolated local development only, while the official published HIVE v1.0.3 stable pin stays immutable. Candidate promotion in the Fairview dev lock requires real exact-head Validate+Integration success. The Windows host's existing global HIVE and data remain untouched. HIVE #168 stays open for authorized upstream registration/review and later compliant release; Fairview #1 stays open until actual host index/corpus/retrieval and MCP proof. This comment is engineering evidence, NOT product approval.KayzenRoot commentedon Sep 27, 2026
Coordinated v1.0.4 repair scope
The owner explicitly requested a single long execution to finish WO-032 (#163), fix global Windows D:/Projects installation and onboarding, and publish v1.0.4 after actual verification. Release planning/authorization: #170 (WO-036/HIVE-REL-013). This issue's documented 5s Git timeout vs 6.87s Windows mount and mode-160000 gitlink rejection are included as necessary backward-compatible repairs UNLESS already independently merged and validated. Preserve existing issue evidence and coordinate with any live executor/PR before edits. No concurrent writes on the shared local Compose/registry/index/corpus while WO-032 is stabilizing. The single executor PDF is attached through owner chat; it does not bypass PR checks or approve publication.
KayzenRoot commentedon Sep 28, 2026
HIVE-FV-001 / PR #169 | FV-BOOT-001 R8 actual-host gitlink corpus defect (same maintenance scope)
Owner provided a 3-page sanitized Codex execution report dated 2026-09-28. This is executor-reported host evidence, not an independently inspected DB/Evidence Bundle. In the isolated Fairview-only HIVE deployment (not D:/HIVE global), operator reports current restore-tested off-Git PostgreSQL/CAS backup (17 restored tables, 11 registered projects, 0 referenced CAS blobs), explicit exclusive maintenance window with discovery OFF and >=120s unchanged PG write counters; PostgreSQL/Redis/dashboard IDs and starts remained stable; original discovery setting was restored after the safe STOP. HIVE candidate source exact
2fbe0e6f5239c91d7ccae9e605a9f087f30ad095; Fairview cleana1495aed386c3990a31c2ae6a48b9be149150ffewith successful 4/4 exact SHA CI.One Fairview index run COMPLETED at current HEAD (78 indexed content paths, 14 indexed / 64 reused), but the ONE corpus sync was BLOCKED
repository_index_stalebefore writing chunks. Git staged inventory contains 79 tracked entries, currentrepository_filescontains 78 content paths; the sole excess entry isvendor/gef-bootstrap, mode 160000. The HIVE PR #169 indexer intentionally ignores gitlink contents while including the pointer SHA in its inventory fingerprint. Direct source inspection ofbackend/app/retrieval.pyon the SAME candidate exposes two divergent all-pathgit ls-files --cached -zcomparisons in_load_repository_sourcesand_revalidate_bundlethat still require the gitlink to appear inrepository_files. It also retains a hard-coded 5-second Git timeout, despite PR #169's bounded configurable Windows Git timeout (default 30s). The runtime image digest has no verified source-build provenance.Necessary bounded scope clarification of EXISTING HIVE-FV-001, not a new WO: align corpus preflight AND final promotion revalidation with the existing indexer's Git stage mode=160000 semantics. Keep gitlink SHA tracked and reject pointer mutations during corpus build; continue rejecting missing/unindexed real source files, unmerged/malformed stage records, changed HEAD or changed real file bytes; use the same configured bounded Git timeout in retrieval read-only inventory calls. Add direct actual-Git focused regression including GEF-style gitlink and negative pointer/real-file races, with NO migrations, DB repair, reset, forced indexing, Docker lifecycle action or release. Update this PR's existing maintenance scope document before implementation. Correct the explicit Review Evidence registry if this already-authorized maintenance identifier is not recognized, with a negative regression; NEVER bypass review, relabel as WO-032 or auto-merge. PR #169 stays DRAFT and v1.0.4 release #170 stays PLANNED until governed upstream gates and real host evidence pass.
Separate condition: the isolated Fairview semantic profile is presently disabled/unconfigured. Source correction cannot make semantic CURRENT without a real authorized local provider (e.g. qualified local Ollama), current backup and separately proven corpus; no fabricated FULL status. Do not retry the already-consumed index/corpus on the host on the basis of this comment alone.
fix(HIVE-FV-001): bounded Windows Git and gitlink-safe corpus
KayzenRoot commentedon Sep 28, 2026
HIVE-FV-001 | Upstream source remediation merged and post-merge CI verified
CLOSURE SCOPE: SOURCE REMEDIATION ONLY. PR #169 was squash-merged to protected
mainasf51c13487a21f22c7c8e873c42722bfac5fd88f8after the exact PR headc06d37d6d07cbb44c846509f78cb91655e178f59passed mandatory Validate, Integration health and Review Evidence plus CodeQL/Dependency Review and resolved review threads. Owner self-audit was recorded asOWNER_SELF_AUDIT_APPROVED / NOT INDEPENDENTunder ADR-019/020; no native author APPROVE was used.Post-merge verification: push CI
36448785315on exact main SHAf51c13487a21f22c7c8e873c42722bfac5fd88f8completed SUCCESS: Validate PASS, Integration health PASS; post-merge Review Evidence is correctly skipped on push. CodeQL push36448785045PASS. Release Publisher36450269940also completed SUCCESS as a guarded no-op: the release-request resolver ran, while metadata validation, package/tag creation and GitHub Release publication steps were all SKIPPED. Therefore this merge did NOT publish v1.0.4 and did not alter the existing stable release contract.Accepted fix: bounded configurable Git timeout propagated through registry/discovery/index/retrieval/executor/context-manager; mode-160000 gitlink contents excluded from source corpus while pointer SHA remains part of inventory/race integrity; retrieval preflight/revalidation use matching gitlink semantics; staged superproject gitlink pointer changes remain visible; exact
HIVE-FV-001governance marker is registered without wildcard/release broadening. Exact-head evidence reported 909 backend tests and 41 dashboard tests PASS plus real temporary-Docker registry/index/retrieval/semantic/hybrid/restart/context-manager integration.Boundary: no global Windows
D:/HIVErepair, no Fairview isolated-host deployment, no semantic provider installation, no MCP/durability host proof and no v1.0.4 publication are implied. Fairview FV-BOOT-001 R8 must consume the accepted upstream commit only through its isolated maintenance lock and repeat its guarded operator-host window. WO-032 #163 and release plan #170 remain separate/open.Issue #168 can now close because its bounded source defect has been merged and post-merge verified.