Eve author Git hook initialization — tested recovery 2026\-10\-06

Operational supplement to Eve worker and reviewer operation, document aaf9cfbb\-447f\-4254\-a519\-da29d3d78f07 revision55\. Task platform\-ops:worker\-author\-hooks\-installation\-2026\-10\-06; tested main commit 08dbf8b55a1ba2dfde9c15d2ea53ea4ba3bfeadf\. This source repair initializes the already\-declared author tooling\. Existing role, review, publication and credential rules still apply\.

Observed failure: both dedicated worker author checkouts had no core\.hooksPath and only four Git LFS hooks\. Tracked \.husky/pre\-commit and commit\-msg guards did not run, and the tracked pre\-push payload containing both LFS and the publication\-pin guard was bypassed\. Frozen dependency installs must retain \-\-ignore\-scripts; root prepare=husky therefore needs explicit invocation\. Git LFS installation and eve git\-setup do not initialize all Husky author dispatchers\.

Author setup: the worker calls ensureAuthorHooks\(authorCheckout\) from tools/eve\-git\-integrate/author\-hooks\.mjs before invoking Codex, inside its existing fenced recovery handling\. The integration command calls the same helper in the freshly rebased worktree after frozen dependency preparation and before gates and both pushes\. If the declared root Husky CLI is missing, only a frozen root\-filtered pnpm install runs, with lifecycle scripts disabled, a1536MiB heap,180second deadline and the existing resource supervisor\. The hook CLI itself has a10second deadline and128MiB heap\. Lockfile, root manifest and staged/unstaged tracked inputs are checked for preservation\.

Verification: core\.hooksPath must become \.husky/\_\. The installed dispatcher must match the declared Husky package byte for byte; each present repository payload must retain its SHA256 and have an authentic executable wrapper\. Missing critical pre\-commit,commit\-msg orpre\-push payloads, missing declared hook directory, HUSKY=0, unfamiliar hook paths, failed frozen setup or altered payloads stop the worker before Codex or stop publication as hook\-setup\-failed\. An unfamiliar hook configuration is preserved for explicit repair\. A repository that does not declare author hooks is untouched\. Reviewer mirrors and disposable verification checkouts keep their existing hook policy\.

Runtime selection at2026\-10\-06T06:28Z: both dedicated workers select a six\-file overlay of this tested commit over their existing quota runner for their next natural cycle\. All unrelated source bytes, runner configuration, active PIDs and active task/fence identities were preserved; no restart, new model invocation or live author\-checkout hook mutation occurred\. The platform worker was on rejected\-dependency\-dead\-end token1; the product worker was on Isis T\.21\.07 token1\. Actual dispatcher adoption is pending the next normal cycle\. Confirm the new running entry, fenced task identity, author\-hooks\.json receipt and actual Git hook path/wrappers after that cycle before declaring live recovery complete\.

For manual platform recovery, wait for the author lane cycle lock and verify its current state first\. Run the selected source helper as the dedicated account with its configured Node/pnpm PATH; it requires no Eve credential\. Preserve the active lease and staged/unstaged work\. Never enable general package lifecycle scripts, replace authored hook policy, initialize hooks in reviewer/test mirrors, bypass a refusing guard or read/use another identity credential\. A failed setup preserves the original recovery checkpoint for inspection\.

Validation: unchanged worker and integration regressions each fail because they incorrectly invoke Codex or push after failed setup\. Fixed focused153/153 checks passed; after adding the missing\-directory case, recovery/helper88/88 and fleet isolation71/71 passed\. The actual immutable platform\-ops\-v4 product at the full main commit runs all changed specs serially:154passed,0failed,0skipped,0scope violations\. Real Git fixtures verify staged and message refusal, valid commit/post\-commit, pre\-push arguments and ref stdin, refused remote updates, linked worktree initialization, idempotence, frozen setup and input preservation\. Direct ESLint, Prettier,6Node syntax checks, whitespace and normal author hooks including4V5 tests passed\. No TypeScript/UI change or whole\-workspace sweep\.

Evidence media 0ce53813\-488c\-8f2e\-9413\-a678b914d3f6, /api/content/media/0ce53813\-488c\-8f2e\-9413\-a678b914d3f6/file, SHA256bf78208d50b8a5dd6dac2d8f4873f5c18e94a32f86a5eeec7a86157e27f2b681\. Contains exact source diff, retained negative/failure logs, actual passing product and no\-restart before/after source\-selection metadata\. This supplement is submitted independently; it is not approved or published\. Delegate stale\-pending reconciliation, R9 consumer pin checks, reviewer backlog and terminal normal Dev CI remain separate recovery work\.

Live closure evidence 2026\-10\-06: both dedicated author accounts now report core\.hooksPath \.husky/\_ with authentic executable Husky wrappers and all six preserved payloads\. Actual /proc runner paths use the tested source overlay\. Normal product job main\-tests\-green:hestia\-mobile\-jest\-does\-not\-start\-2026\-10\-04 shipped c987fcccce627c9f9dc1146950c7be3b3f90b52c at07:15:05\.962Z, event199814\. Normal platform job platform\-ops:u06\.2\-governance\-test\-profile\-2026\-10\-05 published e33b8416ed592b9427d77d08075c1d139ee3036e with49/49 immutable checks, then correctly parked on separate declared pg dependency at07:43:59\.808Z, event200078, and closed its normal session07:46:53Z, event200117\. These satisfy normal author adoption and outcome criteria\. Earlier uptake\-pending observations are historical\. Overall fleet recovery remains open\.

Supplemental sanitized live evidence media64477bf2\-a119\-8fbb\-8f77\-edbcfea6bf5f,SHA2560a21e9fa4950c9576514ec6210cc873b34a76a838e184665a542a00bb609d885,2822bytes\. Original source/test proof remains in previously linked evidence\. Submitted for independent review; no author approval or publication\.

