CHANGELOG: v0.2.14 shipped without the Project Assistant entry, and its changelog fragment is now an orphan #1741

Implementation: FlyBot (ours) — PR follows within 24h. Do not pick up without a pickup-ok comment on this issue.

Written-by: FlyBot Lead
Claimed-by: FlyBot Lead
Claim-Id: 6b9e6a38031f46ce85dd3dcb2799471f
Branch: dev/2-changelog-1712
Base: 4916bd5
At: 2026-10-29T23:32:23Z

Written-by: FlyBot Lead

What — v0.2.14 shipped without the Project Assistant entry, and the fragment that should have carried it is now an orphan on main. At live main 4916bd5f1d0caee85618d2543b3533313e90f7db:

• CHANGELOG.md has ## [0.2.14] - 2026-10-30 at line 9 and the word assistant appears 0 times in the whole file (843 lines).
• The published release body for v0.2.14 has the same gap (assistant: 0 hits).
• #1728 folded 48 changelog.d/ fragments into that release and its list does not include 1712.
• changelog.d/1712-project-assistant.added.md still exists — a fragment whose release has already shipped, so the release workflow will fold it into the next release as if it were new work.

Expected — one line is added to ### Added under ## [0.2.14] in CHANGELOG.md, using the fragment's own text verbatim (it is written in the voice the other entries use) and keeping the #1712 link:

A Project now carries its own assistant: one hidden Bot and Session, memory private to that Project (decisions, open questions, the last digest), and a 09:00 Asia/Shanghai digest that answers what merged, what closed, what is still in progress and on whom, and the next slice, from the Project State files and the board rows only. It posts as the install's own GitHub account and never as the shared app: with no connector signed in, or on a host with more than one member, it refuses and escalates, and every write names the assistant and the login it posts for. Deleting a Project removes its assistant, its schedule and its memory (#1712).

…and changelog.d/1712-project-assistant.added.md is deleted. The fragment file is the only thing deleted: changelog.d/1720-typed-task-contract.added.md, 1729.added.md, 1730-task-audit.added.md, 1731-meetings.added.md and 1733-digest-owners.added.md were merged after the release and belong to the next one — leave all five in place.

Verification (no code, no test) — grep -c 'assistant' CHANGELOG.md is at least 1 and the hit sits inside the 0.2.14 section, not Unreleased; ls changelog.d lists exactly README.md, 1720-…, 1729, 1730, 1731, 1733 and no 1712 file; the release workflow's fragment check, if it runs on the PR, stays green.

Not in scope — editing the already-published v0.2.14 release body (gh release edit). That is the release owner's action (we do not hold it); the repository changelog is what this issue fixes, the release page is a separate decision.

Duplicate check (as of my read, live main 4916bd5f): grep -rn '1712-project-assistant' CHANGELOG.md .github scripts core has no hit; issue search over changelog + 0.2.14 + assistant finds no matching report. #1728 is the release PR that missed this fragment, not a fix for it.