[GeekCmore]

Release

Fix-only follow-up to 0.1.4-rc.1, published to the npm rc tag; latest stays on the previous stable line.

• /btw keeps its side conversation after the answer and no longer runs the primary's unclaimed queued/steering messages.
• Conversation disclosure stays per view; a turn folded under Ctrl+O does not reopen by itself.
• The native session catalog is retained through Cordis traceable service proxies.
• /preset and plan mode run before the first session; pre-refactor error formatters restored.

Verification

Local release gate (the release workflow steps) passed end to end:

• release:preflight 0.1.4-rc.2 and --artifact 0.1.4-rc.2
• test:repo-workflow, typecheck, lint, diagrams:check, check:lib, check:agent-docs, shots:check, check:examples, website:build
• vitest run --coverage — 6394 passed, 1 skipped
• check:pack — 3 tarballs, library 244 files / 3,305,772 bytes

Website preview for content acceptance: http://192.168.8.188:4183/

As on the fix PR, the unrelated mergeConversations / mergeHeights / mergePanels scenario goldens remain stale on main; the release workflow does not run those goldens.

[GeekCmore]

Release run: https://github.com/Ephemeral-AI-Lab/mayfly/actions/runs/39662899253

@ephemeral-ai/mayfly-ui@0.1.4-rc.2 and @ephemeral-ai/mayfly@0.1.4-rc.2 are on the candidate tag and verified. The CLI publish was accepted into npm's staged/processing queue but did not become visible within the 10-minute window; the first run failed on visibility and the rerun hit E409 Cannot publish over previously staged version "0.1.4-rc.2".

Next step for an owner with npm 2FA:

npx npm@12 stage list
npx npm@12 stage approve <stage-id>

Then rerun the release workflow (gh run rerun 39662899253 --failed) so the registry-install and rc promotion jobs run.