Release v0.4.0 — Phase 2 (Governed Learning) close-out - #102
Merged
Conversation
Fill the deferred middle tier of the world-fact cap: the install-wide default, mirroring the already-shipped three-tier recall budget (#60/PR #83). - `install_settings` gains a `world_fact_cap` column (additive, idempotent migration); `InstallSettingsRepository` gains get/set/clearWorldFactCap, each touching only its own column so the two install-wide defaults coexist. - `resolveWorldFactCap` is now three tiers: per-agent override ?? install-wide default ?? DEFAULT_WORLD_FACT_CAP. - Surfaced CLI-only (like the install-wide recall budget — no HTTP/console surface): `asterism config world-fact-cap --default <n>` (set/--unset/show), the per-agent verb now reports the install-wide default as the effective fallback, and `config show` gains the install-wide header + the `[install-wide default]` label. Help + docs updated. - Tests: install-settings world-fact-cap (set/clear/validate/coexistence), 3-tier resolveWorldFactCap precedence, and the CLI install-wide suite (replacing the old "not available yet" rejection test). Suite 1112 → 1123, tsc clean, verify:node + verify:deno 15/15. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…on flip The documentation half of the v0.4.0 cut (rides the release PR; version-string flip lands with the tag). Stacked on the install-wide world-fact-cap branch. - Document the shipped, opt-in **cognition trace** (Lodestar slice 1/2a): new `## trace` section + `config cognition-provider`/`cognition-capture` under `## config`, and a "Cognition trace" concept. Honest framing throughout — opt-in, off by default, observe-only (never changes what an agent may do), references-only by default, best-effort content scrub. - `notes accept`/`reject` + the proposed-note review path (the `## notes` section had said notes are never reviewed — now corrected). - Reflection's Type-B "objective looks finished" suggestion in the `reflect` and `objective` sections (advisory; only an operator apply retires it). - Event-log table: add objective.* / world_fact.* events; fix the stale agent.setting_changed row. - Version/phase flip → v0.4.0: README status reframed (Phase 2 complete; Lodestar wired in as an opt-in observe-only trace; belief-grade learning framed as further out), "What you get" gains a Cognition trace row, container tags 0.4.0/0.4 (README + docs/container.md). Logical-scoping caveat intact. Reviewed through the Priya persona. tsc clean; CLI/help suite green. Package version bumps (package.json ×6) + tag are the final release step. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Codex review [P2]: the v0.4.0 docs advertised a release while the package and CLI version metadata were still 0.3.0, which release.yml rejects (tag must match committed versions) and which would publish/report 0.3.0. Bump them in the same change as the docs version-flip so the branch is internally consistent. - All 8 @qmilab/* package.json → 0.4.0 (deps stay workspace:*). - packages/cli/src/version.ts VERSION → 0.4.0 (asserted to match package.json). - bun.lock workspace versions synced (bun install --frozen-lockfile passes). Verified: release.yml version-match check PASS for all 8 packages + the CLI constant; bun run build clean; bun test 1123 pass / 0 fail; the real CLI binary reports 0.4.0. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
v0.4.0 — Phase 2 (Governed Learning) close-out release
The release that ships the unreleased batch since v0.3.0 and marks Phase 2 complete. Combines the final Phase-2 carry-forward, the v0.4.0 docs gate, and the version bump. Supersedes #101 (its commit is included here).
What ships
Feature — install-wide world-fact-cap tier (#100 carry-forward, was #101)
resolveWorldFactCapis now three tiers: per-agent override → install-wide default →DEFAULT_WORLD_FACT_CAP, mirroringresolveRecallBudget.install_settings.world_fact_capcolumn (additive migration) +InstallSettingsRepositoryget/set/clear; the two install-wide defaults coexist on the single row.asterism config world-fact-cap --default <n>(set /--unset/ show),[install-wide default]label inconfig show. CLI-only, like the install-wide recall budget.Docs gate (v0.4.0)
## tracesection +config cognition-provider/cognition-capture+ a "Cognition trace" concept — honest framing (opt-in, off by default, observe-only, references-only default, best-effort scrub).notes accept/reject+ the proposed-note review path (the section had wrongly said notes are never reviewed).reflect/objective.objective.*/world_fact.*added, staleagent.setting_changedrow fixed.0.4.0/0.4.Version bump
@qmilab/*package.json+packages/cli/src/version.ts+bun.lock→0.4.0.Review
Codex (
/codex:review --scope branch) returned one [P2] — docs advertised v0.4.0 while package metadata was still 0.3.0 — fixed in5e9c95e(the bump above). Re-verified against the release gates:bun install --frozen-lockfileconsistent ·bun run buildclean ·bun test1123 pass / 0 fail · node + deno acceptance 15/15--version→0.4.0Release mechanics (after merge)
Tag the merged commit
v0.4.0and push it.release.ymlpublishes the 8 npm packages (bun pm pack) + a GitHub Release;docker.ymlbuilds the multi-arch image. Then verify livebunx @qmilab/asterism@0.4.0andghcr.io/qmilab/asterism:0.4.0(image tag is0.4.0, nov). Gotchas:NPM_TOKENmust be a granular Automation token (bypass-2FA); a brand-new scoped package can 404 for ~5 min post-publish (propagation — don't re-publish).Carried from #100 (Phase 2 deferred follow-ups); the install-wide world-fact-cap item is now done.
🤖 Generated with Claude Code