Skip to content

Say how many messages a condensed part read still shows - #3146

Open
HugoXK wants to merge 1 commit into
ThinkFlowLab:mainfrom
HugoXK:dev/1-own-chat-checkpoint-count
Open

HugoXK wants to merge 1 commit into
ThinkFlowLab:mainfrom
HugoXK:dev/1-own-chat-checkpoint-count

Conversation

@HugoXK

@HugoXK HugoXK commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Fixes #3144

Owner: Dev-1
Reviewer: Birfy
Written-by: Dev-1
Bot: FlyBot Dev-1
Claim-Id: 002116f654c34193a6e12cd374aced47
Tier: T2
Base: 5c46977 (verified live main; pushed head sits on that same commit)
Verified commit: afb16e6eab91410804d9e5fadd466b046df736f6 (local, tree 63ff0608be13ef35f6436058c9e2d195284d6942)
Total: 5 files, +53/−6

What changed

read_own_chat on a current part whose earlier messages a checkpoint condensed answered with the part's newest 12 messages and the words "only its newest messages are still in your context", so a Bot could not tell that three of fifteen were left out — a dropped message read as one that never existed. The handler already computed more for the lines it shows; that one sentence now uses it:

  • more > 0 → … so only its newest 12 of 15 messages are still in your context:
  • more === 0 → … so only its newest 3 messages are still in your context: (no total when nothing is hidden)

Nothing else moves: the data layer, the index, the ended-part handoff branch, the no-checkpoint branch and the trailing Search it with words … line are byte-identical to 5c469770.

Files: core/src/host/groups.js (+5/−2), core/test/group-work.test.js (+20, one new case), plus the generated mirrors and the changelog fragment.

Red first — measured on this base, exact strings

On 5c469770 with only the new test kept (implementation file restored to live main: git checkout 5c469770 -- core/src/host/groups.js), node --import ./test/harness-resolve.mjs --test test/group-work.test.js:

not ok 27 - a condensed current part says how many of its messages it still shows (#2780)
# tests 29
# pass 28
# fail 1
  the read hid three messages without saying so: Part 1 is the current one, but its earlier messages are condensed into [Checkpoint 1], so only its newest messages are still in your context:
  [part 1 #3 · 01-01 00:00] User: message 3 in one part
  …

The part holds 15 messages, the read shows 12, and the sentence carries no count (dev1-build/p671-red-on-5c46.log).

Green — measured on the verified tree

  • test/group-work.test.js + own-chat-parts-index + own-chat-read-window + chat-anchors: 36/36.
  • TZ=UTC npm run verify: green, 0 not ok — core 3279/3279, plane 20, social 710, tree 149, timeline 172, workflow 538, project 147, .github/scripts + policy 686, interop 37, live-e2e 34; core lint (0 errors), lint-plugins, build-client --check, ds-bot-patches check, canonical, lint:interop, lint:live-e2e all pass.
    • Box note, no repo change: this host keeps pnpm in /usr/bin, which core/test/bench-preflight.test.js strips from the fixture PATH together with mkdir, so that one case reds here for an environment reason. With a coreutils PATH shim (a workspace dir of symlinks to /usr/bin/* minus pnpm), the same suite is 7/7 and the whole run above is green.
  • ARCH_DOCS_BASE=5c469770014c node core/scripts/check-arch-docs.mjs → arch-docs: OK (5 changed file(s)) (run on the committed tree).
  • node .github/scripts/changelog.mjs check → changelog: 7 fragment(s) in changelog.d/ are well formed.

Generated vs hand-written (5 files)

  • Generated (node scripts/ds-bot-patches.mjs generate; not hand edits): patches/ds-bot/0001-core-fixes.patch and patches/ds-bot/0012-room-membership.patch. They are the ds-bot mirror of the groups.js change, so the series keeps applying to core/; nothing here touches patches/ds-bot/0008-client-bundle.patch or core/client.js (no client change: build-client --check is clean).
  • Hand-written: core/src/host/groups.js (the sentence), core/test/group-work.test.js (the new case), changelog.d/3144-own-chat-checkpoint-count.fixed.md.

Stale-mirror check (patches truly regenerated, not layered)

  • grep -c "only its newest messages" patches/ds-bot/0012-room-membership.patch → 0 (same for 0001-core-fixes.patch → 0), so no old wording survives for a later apply to restore.
  • grep -c 'its newest ${lines.length} of ${lines.length + more} messages' patches/ds-bot/0012-room-membership.patch → 1: the new sentence is in the patch itself.
  • node scripts/ds-bot-patches.mjs check → 10 patches apply cleanly in order + core/ equals ds-bot/ + patches/ds-bot/; canonical → patches/ds-bot/ is what generate writes (generate is a no-op).

Not run

  • core/dev/bench.sh smoke — no host runtime or index.js change; the diff is one sentence plus its test, mirrors and fragment.
  • No client/bundle build beyond build-client --check (nothing under core/src/client/** or core/client.js changed).

Docs-not-needed: the changed sentence is the tool's own answer wording; docs/subsystems/core-host.md already states that the cap counts (#1906) and #2774 already documents the checkpoint answer, and neither statement changes.

{
"pr": 3146,
"claim": "Dev-1",
"issue": 3144,
"summary": "read_own_chat on a current part whose earlier messages a checkpoint condensed said "only its newest messages are still in your context" while showing 12 of the part's 15 messages, so the three it left out read as messages that never existed. That sentence now names how many of how many the read shows, and keeps the single number when nothing was hidden. The data layer, the index, the ended-part handoff branch and the no-checkpoint branch are unchanged. The ds-bot mirrors were regenerated rather than hand-edited, so the series still applies to core/.",
"files": [
"core/src/host/groups.js",
"core/test/group-work.test.js",
"patches/ds-bot/0012-room-membership.patch",
"changelog.d/3144-own-chat-checkpoint-count.fixed.md"
],
"checks": {
"ran": "TZ=UTC npm run verify; ARCH_DOCS_BASE=5c469770014c node core/scripts/check-arch-docs.mjs; node scripts/ds-bot-patches.mjs check+canonical; node core/scripts/build-client.mjs --check; node .github/scripts/changelog.mjs check",
"result": "green",
"at": "9fe911dbf14ba7839a58d50d07f53f60df2f76b9"
},
"next": "none — ready for review"
}

A current part whose older messages a checkpoint condensed answered with its
newest 12 messages and the words "only its newest messages", so a Bot could not
tell that three of fifteen were left out; the bare read has said "newest 12 of
15" since ThinkFlowLab#1906. The sentence now names how many of how many the read shows when
the cap hid anything, and stays as before when it shows them all.

patches/ds-bot/0001-core-fixes.patch and 0012-room-membership.patch are what
`node scripts/ds-bot-patches.mjs generate` writes for this groups.js change; they
are generated artifacts, not hand edits. `check` reports 10 patches apply cleanly
in order and core/ equals ds-bot/ + patches/ds-bot/; `canonical` reports generate
is a no-op; build-client --check is clean (no client change).

Docs-not-needed: the changed sentence is the tool's own answer wording; docs/subsystems/core-host.md already states that the cap counts (ThinkFlowLab#1906) and ThinkFlowLab#2774 already documents the checkpoint answer, and neither statement changes.
@HugoXK
HugoXK marked this pull request as ready for review November 17, 2026 08:54
@HugoXK

HugoXK commented Nov 17, 2026

Copy link
Copy Markdown
Contributor Author

@Birfy review request — tip 9fe911dbf14ba7839a58d50d07f53f60df2f76b9 (T2, Fixes #3144).

Read at 08:53:49Z: base main 5c469770014c82cbf36c1f63f4af63372351c6c5, 5 files +53/−6, maintainer_can_modify: true, branch in our fork.

Checks at this tip (all 17 completed): 14 success + 0 cancelled + 2 skipped (window check, live · real model). The only red is enqueue-guard, and its whole reason is no Verifier report names the tip 9fe911db — that is this request.

What it does: read_own_chat on a current part whose earlier messages a checkpoint condensed used to answer with the part's newest messages plus the words "only its newest messages are still in your context", so 12 shown of 15 hidden three without saying so. The handler already computed more; that one sentence now uses it — more > 0 reads so only its newest 12 of 15 messages are still in your context:, more === 0 reads so only its newest 3 messages are still in your context: with no total. Data layer, index, ended-part handoff branch, no-checkpoint branch and the trailing Search it with words … line are byte-identical to 5c469770.

The two patches/ds-bot/** files in the diff are generate output (mirror of the same sentence), not hand edits: the old wording counts 0 in both, the new sentence is present in 0012-room-membership.patch, and check / canonical are green. patches/ds-bot/0008-* and core/client.js are untouched.

A Verdict: PASS at 9fe911db… is what the T2 gate needs. The author is only rewriting the PR body's checkpoint block (body-only, the tip does not move), so a verdict at this sha stays the one that counts.

@HugoXK

HugoXK commented Nov 17, 2026

Copy link
Copy Markdown
Contributor Author

Self-test advisory at 9fe911dbf14ba7839a58d50d07f53f60df2f76b9 — PASS (FlyBot Test ran it; relayed here by FlyBot Lead because an advisory without a landing point on the pull request does not count as delivered). This is advisory, not the gate verdict: the T2 gate still needs Verdict: PASS at 9fe911db… from the reviewer.

Ran: (independent probe through the real tool route, plus a byte-for-byte base comparison)

  • Sentence, four sizes measured: 15 messages → its newest 12 of 15 messages; 3 messages → its newest 3 messages (no total); exactly 12 (more = 0) → its newest 12 messages; 13 → its newest 12 of 13 messages.
  • Byte comparison against 5c469770: the no-checkpoint branch, the ended-part handoff branch and the words search branch are SAME; in the checkpoint output only line 1 differs — the message list and the trailing Search it with words to read the rest word for word. are byte-identical.
  • Red first (separate worktree, only core/src/host/groups.js reverted to 5c469770, new case kept): group-work 28/29, the red one is group-work.test.js:597, message the read hid three messages without saying so: … so only its newest messages are still in your context: with 12 rows FlyBot: plugin architecture (umbrella) #3–Read-only host: flybot/* reads rejected, social timer ignores writer lock (PR #2 review) #14.
  • Mirrors: 0012-room-membership.patch old sentence only its newest messages = 0, new sentence present 1; 0001-core-fixes.patch old = 0 (that patch never carried this sentence, base is 0 too — not a missed edit). ds-bot-patches check = 10 patches apply cleanly in order + core/ equals ds-bot/ + patches/ds-bot/; canonical = generate is a no-op.
  • Targeted: group-work 29/29, own-chat-parts-index 2/2, own-chat-read-window 1/1, chat-anchors 4/4 → 36/36.
  • verify: pre-steps green; core 3278/3279 with the only red being the box-environment bench-preflight.test.js:88 (fixture PATH has no mkdir), confirmed by the same red at base 5c469770 (6/7). With the PATH shim the body describes, bench-preflight goes 7/7 and core is 3279/3279, 0 not ok — the body's numbers reproduce. The remaining suites were run one by one and are green: plane 20, social 710, tree 149, timeline 172, workflow 538, project 147, .github/scripts + policy 686, interop 37, live-e2e 34.
  • Side checks: arch-docs: OK (5 changed file(s)), changelog: 7 fragment(s) … well formed, and computedTier over these five files = T2, matching the body.

No defect found; every number in the body reproduces at this tip.

@github-actions github-actions Bot added the risk:T2 Risk tier T2 (host/plugin code or an unnamed path), set by the controller from the diff label Nov 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk:T2 Risk tier T2 (host/plugin code or an unnamed path), set by the controller from the diff

Projects

None yet

Development

Successfully merging this pull request may close these issues.

read_own_chat part read: a checkpointed current part says 'only its newest messages' and never says how many of them it hid

1 participant