# Lodestar 2.0.0

> **Development checkpoint.** This package version was never published to npm. This note records a local 2.x checkpoint, not an installable public release. See the [2.1.2 release notes](v2.1.2.md) and [current installation guide](../installation.md).

Package: `lodestar-agent-context@2.0.0`.

Lodestar 2.0 is the single-current-contract release. It ships one contract-5
envelope, schema 5, one guarded mutation owner, explicit database instance and recovery
epoch, idempotent request receipts, accepted-revision ordering, raw history, and writer
fences that reject retained older clients.

Project orientation is now a fresh read. Ordinary reads and writes never initialize,
migrate, or replay a startup cache. A caller receives source status and a usable write
basis, then records one consequential correction, decision, work outcome, or continuity
change through the same checked mutation path. Lost responses replay from the exact
request; stale or cross-store bases fail before mutation.

The release contains one explicit, backup-verified schema-4 conversion. It does not
ship schema-1 through schema-3 production converters. Forward recovery of a fully
accounted schema-5 image retains the database instance and allocates a new epoch.

The Codex integration now consists of an automatic Lodestar skill and three MCP tools
that import the installed CLI's command, mutation-input, request, and contract
declarations. The prior hook, host-attestation token, message-tail capture, and
session-start injection runtime has been removed. MCP cannot authenticate a Codex user
or session by itself, so identity-required claims need an actual host route that supplies
those fields; the adapter never fabricates them.

The package retains seven complete skills and verifies exact file membership and raw
bytes from a contract-5 manifest. Private Golden Rules content is no longer bundled.
Four Golden-starting-point skill trees keep later named repository repairs, including
removal of arbitrary candidate, evidence, retry, and output quotas; `director-protocol`
already matched its Golden source.

Windows and WSL continue to use the Windows-owned one-shot executable. WSL never opens
the SQLite file directly. Lodestar remains dependency-free and requires Node.js
24.15.0 or newer.

```text
npm install --global .\lodestar-agent-context-2.0.0.tgz
lodestar init
lodestar start --cwd .
```

The tarball is the supplied pre-publication artifact. Use the registry coordinate
only after 2.0.0 is published. Existing schema-4 stores require paused writers, a
restore-inspected backup, and `doctor --migration-preflight`, followed by the explicit
`init --migrate --file <request.json>` flow documented in the README.