chore(engagement): regenerate the manifest for coreApi ^1.21.0 #74

wtclaude · 2026-10-30T16:55:11-05:00

wtclaude commented

2026-10-30 16:55:11 -05:00

Fixes the red server-tests on the v0.7.0 cutover (#73, run 83). The tests passed (# fail 0); check:engagement failed with "engagement-triggers.json is stale".

Cause. engagement-triggers.json embeds coreApi. #72 raised it to ^1.21.0 and didn't regenerate the file. #72's own server-tests job died on the runner's full disk before it reached this check (run 82), so nothing flagged it until #73.

Change. npm run engagement:manifest in server/. The only line that changes is "coreApi": "^1.20.0" → "^1.21.0". No trigger, stream, audience or seeded rule changes.

No release needed. The file ships in the tarball (ci/bundle.json), but neither core nor the module reads it at runtime; it's a record for reviewers. v0.7.0 behaves correctly, and this rides the next edge → main cutover. chore, so it won't cut a release on its own.

Checked: npm run check:engagement reports "engagement-triggers.json is current".

AI-assisted: Claude Code (Claude Opus 5.5)

🤖 Generated with Claude Code

https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

Fixes the red `server-tests` on the v0.7.0 cutover (#73, run 83). The tests passed (`# fail 0`); `check:engagement` failed with "engagement-triggers.json is stale". **Cause.** `engagement-triggers.json` embeds `coreApi`. #72 raised it to `^1.21.0` and didn't regenerate the file. #72's own `server-tests` job died on the runner's full disk before it reached this check (run 82), so nothing flagged it until #73. **Change.** `npm run engagement:manifest` in `server/`. The only line that changes is `"coreApi": "^1.20.0"` → `"^1.21.0"`. No trigger, stream, audience or seeded rule changes. **No release needed.** The file ships in the tarball (`ci/bundle.json`), but neither core nor the module reads it at runtime; it's a record for reviewers. v0.7.0 behaves correctly, and this rides the next edge → `main` cutover. `chore`, so it won't cut a release on its own. **Checked:** `npm run check:engagement` reports "engagement-triggers.json is current". - [x] AI-assisted: Claude Code (Claude Opus 5.5) 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

wtclaude added 1 commit 2026-10-30 16:55:13 -05:00

chore(engagement): regenerate the manifest for coreApi ^1.21.0

PR Checks / client-build (pull_request) Successful in 1m7s

Details

PR Checks / server-tests (pull_request) Successful in 1m24s

Details

PR Checks / frozen-manifest (pull_request) Successful in 2m25s

Details

68a8d637f5

#72 raised coreApi to ^1.21.0 without regenerating
engagement-triggers.json, which embeds it, so check:engagement has
failed since. That went unseen on #72 (its server-tests job died on a
full runner disk before the check) and surfaced on the cutover (#73).
Only the coreApi line changes; no trigger, stream, audience or rule.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

whitlocktech merged commit 3c3286357a into edge

2026-10-30 16:56:18 -05:00

whitlocktech referenced this issue from a commit

2026-10-30 16:56:21 -05:00

Merge pull request 'chore(engagement): regenerate the manifest for coreApi ^1.21.0' (#74) from fix/engagement-manifest into edge

whitlocktech deleted branch fix/engagement-manifest

2026-10-30 16:56:22 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: RunicGateway/Module-Rust#74