[entelecheia]

Refs #331.

Prepare agent-mem 0.24.0 so hosts can exact-pin a release containing 1632be8 and CaptureStore.countOutsideRecent({event,since}) / CaptureOutsideCount. The commit is on main 224b2bc and absent from published0.23.1. Package, Claude plugin and README version facts advance together; Unreleased notes are promoted to 0.24.0 and each affected surface states Compatibility with N-1(0.23.1). The #331 note explicitly covers the additive bounded indexed count, unavailable fallback and host pin requirement. Past release notes are byte-identical.

This metadata proposal changes no product source, dependency, schema or format floor. It prepares the existing Unreleased feature set, including the person-gated0.24.0 curated-cache reader floor; that floor is not raised by the release metadata.

Release readiness is staged:

1. Review/merge the proposed metadata version.
2. Recheck the five stale documents against that merged origin/main source and prepare a separate docs/verified.json refresh. Stamps must name origin/main, never this release branch; changing package.json after stamping the old main would leave README/contracts stale again.
3. Require the final resulting main commit's push check to be green on both stable OS gates for that exact tree, followed by the release workflow proof/gates.
4. The person explicitly authorized 0.24.0 on 2026-11-11. Before tag push, report that final main commit and green push run to the reviewer and await confirmation; only then push v0.24.0. No tag, publishing dispatch, registry mutation or floor change has been made. After publication, read back the registry with cache busting and the Release body.

Current main 224b2bc has eligible manual check 42935250440 green on both OSes; its push 42934443076 was red on the known macOS M1 transcript wall class. The manual green does not prove this version-bump tree or the later stamp tree. The latest published version remains 0.23.1. Publication and registry/Release readback remain future steps after authorization and all gates.

Validation at 7ad4be2:

• Local short checks: README facts, boundary and pack dry-run (182 files) passed.
• Final head 7ad4be2517cbbf37768a9106b1918ffabf02a609, remote Bun 1.4.2: typecheck, boundary (172), README facts, 10 count tests (31 assertions), and pack dry-run (182 files) passed. Full suite: 3,678 pass, 26 existing platform skips, 0 fail; 50,455 assertions, 3,704 tests across 337 files (1369.45 s); verify exited 0 in 1385 s. The normal docs check still reports five stale stamps; require-fresh remains a release blocker. Full log: scratchpad/temp/task218/full-7ad4be2.log, SHA-256 5731100c01c8f82a77fba9dd0e6917aad184198bcc65b9974dd032483954ff52.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.

[chatgpt-codex-connector]

Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-11T03:14:09.330459Z	7ad4be2	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.