Lodestar v1.4.1
Lodestar 1.4.1
Agent startup doctrine and native instruction files now have one owner instead of
competing copies of reality.
npm install --global lodestar-agent-context@1.4.1
lodestar skills sync --target all
lodestar skills verify --target all
One rule, one owner
The Director Golden Operating Rules now ship as the sole required global governance
record, g:lodestar:required-governance. Its machine-readable source is
managed-assets/governance.json; docs/GOLDEN-RULES.md is generated from that same
source as the complete human-readable recovery copy. Historical governance IDs no
longer compete in required startup context.
Lodestar supports two deliberate project shapes:
- A full native
AGENTS.mdor equivalent owns version-controlled project rules and
directs the agent to Lodestar for durable decisions, knowledge, work presence, and
continuity. - A minimal native file bootstraps Lodestar only when
lodestar startis proven to
return every required governing rule without truncation or omission.
The two shapes are alternatives. Evolving the same rule in both places creates a
split-brain contract in which a native agent file and Lodestar startup can instruct an
agent differently.
The minimal stub is generated truth
The shipped minimal AGENTS.md stub now matches the package-owned bootstrap exactly.
The package test enforces that identity, so command-surface changes cannot leave a
second hand-written stub stale.
Published model-facing assets are also scanned for the retired handoff save,
handoff validate, and handoff clear verbs. The supported continuity surface remains:
lodestar handoff arm|status|checkpoint|now|disarm
Startup headroom restored
Lodestar's general default startup envelope is now 24 KiB, leaving the established
4 KiB minimum project headroom after the complete Golden Rules are loaded. Explicit
budgets still win, and the Codex adapter retains its measured 16 KiB host boundary.
Codex startup and stop-hook recovery now shed oversized optional continuity content
without truncating or inferring required authority.
Upgrading
There is no schema change and no registry migration. Install the package, then sync and
verify the managed client skills so every configured agent receives the same template
contract.
npm install --global lodestar-agent-context@1.4.1
lodestar skills sync --target all
lodestar skills verify --target all
Requires Node.js 24.15.0 or newer.
