ForgeKit OS Extraction

Timeline

1. 1

   Start

   Pulse bug surfaced the coupling

   ReferenceError in pulse.mjs led to the architectural question: why is all this in forgekit-website?

2. 2

   30m

   Pulse fixed, OS extraction designed

   Anvil Check confirmed forgekit-os/ at monorepo root, not packages/

3. 3

   2h

   Scripts migrated with explicit path constants

   pulse, retro, engine-guard, build-session, build-trends — all rewritten

4. 4

   3h

   All 4 commands verified from c:\ForgeKit

   pulse, guard, build:session, build:trends all pass

5. 5

   Close

   Docs updated, retro written against new path

   First retro to run through the new forgekit-os/ pipeline

What shipped

• forgekit-os/ directory at monorepo root with scripts/, sessions/, package.json, deferral-ledger.json

• pulse.mjs — rewritten with explicit path constants (MONOREPO_ROOT, OS_ROOT, SESSIONS_DIR); bug fix: color constants moved before use

• retro.mjs — rewritten with full explicit path constant block; runs from c:\ForgeKit, not from inside forgekit-website/

• engine-guard.mjs — rewritten; root → WEBSITE_ROOT, repoRoot → MONOREPO_ROOT, session arg resolved against MONOREPO_ROOT

• build-session.mjs — rewritten; 7 path substitutions including DEFERRAL_LEDGER, BUILD_LOG_INDEX, BUILD_LOG_OUTPUT, SESSIONS_DIR

• build-trends.mjs — rewritten; 6 path substitutions including ENGINE_HEALTH_DOCS, ENGINE_HEALTH_SITE_COPY, DEFERRAL_LEDGER

• Root package.json: pulse, guard, build:session, build:trends, retro commands all wired to forgekit-os/scripts/

• ignition.md §6 CLOSE updated: sessions path → forgekit-os/sessions/, retro command → runs from c:\ForgeKit

• gates.md Session-Close Gate updated: session JSON path → forgekit-os/sessions/

• CLAUDE.md Core principle updated: session retro path → forgekit-os/sessions/