Skip to content

ContextForge v0.3.0

Choose a tag to compare

View all tags
@kallist kallist released this 10 Sep 03:09
· 25 commits to main since this release
v0.3.0
c51a7d3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

ContextForge v0.3.0

Compile what your coding agent sees. Explain it. Control it. Replay it.

V0.3 turns a context compilation into a local, inspectable lifecycle. Context
Capsules record selected and dropped candidates, source identities, evidence,
strategies and exact payload hashes. Compressed local history lets you revisit them
without silently turning your repository into a source archive.

Start contextforge studio --repository ./repo to inspect a proposal in the local
browser UI. Semantic controls let you PIN, EXCLUDE, PREFER, FOCUS or request a RANGE.
Recompilation creates a new Capsule and immediately compares before/after decisions,
ranges, evidence, roles and token contributions. Hard budgets and source safety remain
compiler invariants; impossible or stale controls fail explicitly.

Replay clearly separates offline recorded inspection from actual reproduction
verification. The product cannot restore old source bytes from source-light history.
Coverage and deterministic lint describe captured facts and tradeoffs; they do not
invent a context-completeness score or infer benchmark Gold.

The CLI exposes history, replay, diff, coverage and recompile alongside existing
pack/explain commands. The four MCP tools and public contextforge-v1 compiler
default remain unchanged. V2 remains internal/experimental with mixed measured
evidence. No cloud backend, account, telemetry, new agent runtime or V0.4 Review
product was added. AGENT SUCCESS NOT MEASURED.

Requires Node >=24.15 <25. Frontend assets and the five WASM parser assets ship
inside the existing @kallist/contextforge package. See the
product guide for exact contracts and limitations, and
validation evidence for measured gates. A normal public release
requires green post-merge main CI, immutable annotated tag, successful npm publish,
public-registry fresh install/product smoke and only then GitHub Release creation.

Verified release evidence

  • Release commit: c51a7d3ac4e92d44ea7fe90df5f09f6dedf42af4.
  • PR #12: final HEAD passed all six jobs in both PR and push CI.
  • Post-merge main CI: all six jobs passed, including the full frozen benchmark and Capsule conformance.
  • Public npm @kallist/contextforge@0.3.0, dist-tag latest, 214 files, five WASM assets, three Studio assets.
  • Public registry fresh-cache installation passed CLI, official-client MCP, Capsule/history/Replay/Diff/Coverage/recompile, and a real installed-package Chromium workflow including stored XSS and restart checks.
  • Published integrity: sha512-OhLzfCngDkJZ9xy5scBYdi7khln8GHbfPQdwaXU981bGcGaq7KTRaRWGINXrWWY6UPXYoPH8RcE7BeHT5Hf8uA==.
  • Public default remains contextforge-v1. Agent success is not measured. V0.4 is not started.
Assets 2
Loading