Every path in Important Paths, Useful Commands, and External Context named the
lost E: drive. CLAUDE.md is a bare @AGENTS.md import, so those dead paths were
loaded into every session in this repo.
Swapping E: for F: would only reset the timer, so the paths are now
repo-relative and gamecult-ops is named as a sibling repo rather than an
absolute location. All ten referenced files were confirmed present after the
move; none were lost with the drive.
The interpreter guidance was worse than stale. It pointed at a venv under the
dead drive, and the documented fallback did not work either: this workstation
had no Python at all, and both `python` and `python3` resolved to Microsoft
Store aliases that print an install prompt and exit 0. Python 3.13.15 is now
installed to the user scope and ahead of WindowsApps on PATH, both tools were
run under it, and the section documents that failure mode so the next agent
installs an interpreter instead of hard-coding a path to someone else's.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The recipe validates. It encodes the build sequence that previously lived
only in the host's shell manifest -- npm ci in vendor/CultLib, then build
cultcache-ts, cultnet-ts and cultmesh-ts, then pnpm install, test, build --
so the source seal now covers how Heimdall is built, not just what from.
Artifacts are dist/ plus the production node_modules, because the unit runs
dist/src/index.js and Node resolves imports at runtime; the release is not
the compiled output alone.
Marked NOT YET DEPLOYABLE in the file, because validation only proves the
declaration is well-formed, not that the service honours it. src/index.ts
binds config.port (4100, fixed), and `grep -r GAMECULT_IDUNN src/` returns
nothing. Warm-then-cutover needs a candidate to bind where Idunn tells it
via GAMECULT_IDUNN_CANDIDATE_BIND, because candidate and incumbent run at
once under distinct UIDs and namespaces -- a service pinned to one port
cannot warm alongside itself. The process write lease and runtime bundle
are declared and unread too.
Odin, Ghostlight and CodexConnector all read these variables; every target
with a recipe implements the contract. Heimdall publishes Idunn health
already via src/idunn-rudp-health.ts and stops short of the rest. That
implementation is the remaining work, and it is app code rather than
deployment configuration.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Heimdall took CultLib as file:../CultLib/packages/*, a sibling checkout
outside this repository. Nothing pinned which CultLib a given Heimdall
commit was built against, and a sealed source could not reach it. The
deploy manifest worked around this by cloning CultLib separately to
/srv/build/CultLib with cultlib_commit=5cefa0db hardcoded in shell -- the
pin existed, it just lived in an untyped place where no build could see it.
vendor/CultLib is now a submodule pinned at exactly 5cefa0db, the commit
the manifest already used, so this change is purely structural: the
dependency does not move. Bumping to a current CultLib is a separate
change, and should be, or a failure could not be attributed.
This also uncovered that the build was never reproducible from a clean
checkout. The sibling directory had dist/ present because someone had
built it by hand at some point; a fresh CultLib clone has none, and the
packages' main/types point straight at dist/. Building Heimdall against a
fresh CultLib fails with thirteen TS2307s. The manifest knew -- it runs
npm ci then npm run build for cultcache-ts, cultnet-ts and cultmesh-ts
before touching Heimdall -- but that knowledge lived only in the shell
script. It belongs in the recipe's steps, which is where it goes next.
Verified end to end on a fresh submodule clone: the three CultLib packages
build, pnpm install resolves, tsc exits 0, dist/src/index.js is produced
(the exact path heimdall.service runs), and vitest passes 38 tests in 9
files.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The import was added on 2026-09-03 as "shared with Codex". The estate has
since left Codex as a supplier and the global doctrine no longer maintains
a Codex twin, so that half of the sentence describes a reader that is not
coming. The mechanism is unchanged and still correct: AGENTS.md holds this
repo's doctrine, CLAUDE.md imports it, and neither is duplicated.
Renaming AGENTS.md across the swarm is a separate sweep and not worth
doing incidentally here.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The repository was public but carried no license, so default copyright applied
and all rights were reserved. Readers could look at the code and had no right to
run, copy, modify, or self-host it. GitHub's terms grant forking within GitHub
and nothing past that.
This matters now because Erycina is being prepared for founding creators to
self-host, and its intended one-click deployment installs Idunn to bring up
Odin, Heimdall, and Erycina together. Erycina is MIT, and Heimdall alone owns
identity, grants, revocation, and signed entitlement claims: without a license
here a creator could take payment and have nothing entitled to mint the claim
that unlocks the media they sold.
MIT to match CultLib, VoidBot, Eve, and Odin, and the stated intent for GameCult
projects.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude Code reads CLAUDE.md, not AGENTS.md, so this repo's doctrine was
invisible to it. This one-line import makes the existing AGENTS.md load
without duplicating or renaming it. Codex is unaffected.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>