Skip to content

Release v1.5.2 - #174

Closed
Phototonic wants to merge 12 commits into
mainfrom
promote/1.5.2
Closed

Phototonic wants to merge 12 commits into
mainfrom
promote/1.5.2

Conversation

@Phototonic

Copy link
Copy Markdown
Owner

Summary

Promotes dev at 530dffc to main. Merge with Create a merge commit, not squash, so the source ancestry stays. That push makes the release workflow run its checks and then publish the v1.5.2 tag, the curated release Agent Progress v1.5.2: A stable system prompt, and steadier Tidy, and the extension and companion ZIPs automatically.

Closes #161

What's in 1.5.2

Protocol and schema stay at 2, and the minimum host remains OpenChamber 2.7.1.

Verification

  • Promotion shape: parents are main 13f4123 then dev 530dffc; the tree is exactly dev plus the nine generated outputs; the promotion command's two builds matched; every version stamp reads 1.5.2.
  • Main-push rehearsal in a fresh full-history clone with its remote removed and a cleared environment, run as a push to main from 13f4123: eligible, version 1.5.2, release name Agent Progress v1.5.2: A stable system prompt, and steadier Tidy and body matching release-notes/1.5.2.md; the extension and companion ZIPs and checksum inventories are accepted.
  • Portable CI on this exact commit in a second fresh full-history clone with a cleared environment: see the table below; nine-output parity and package verification passed.
Gate Result
Promotion command (two builds, version stamps) Passed
Tree equals dev plus the nine outputs Passed
Main-push rehearsal: nine-output rebuild parity, release notes, publication eligibility, ZIPs and checksums Passed on Node 24.19.0, the CI release gate version, and again on 24.22.2 (each 2,189 tests: 2,163 passed, 26 skipped, 0 failed)
Portable CI, fresh clone Passed on Node 24.22.2 (2,189 tests: 2,163 passed, 26 skipped, 0 failed)
Package verification, including isolated service and companion lifecycle checks Passed (part of both CI runs)
Native-host Git, folder and ZIP install Not run: no isolated OpenChamber 2.7.1 host module is available here
Companion lifecycle on a real host Not run: needs the same isolated host module; the packaged-companion lifecycle checks inside package verification above are not a host run
Real-host release journeys Not run: needs an isolated OpenChamber 2.7.1 host module and an independent OpenCode 2.2.7 binary, neither available here
Native-only runtime tests CI excludes (production-runtime, plugin-failure-runtime, progress-activation-runtime, subagent-activity-runtime, subagent-upgrade-runtime) Not run: need an independent OpenCode binary
Release credit reminder (advisory) Ran: baseline v1.5.1, 11 merged pull requests, no outside contributors
Windows native suite Runs in this PR's CI
Maintainer's Windows, phone and live-agent checks Not run here: maintainer checks on this branch before merge

The 26 skipped tests are Windows-native tests that skip off Windows (three Windows journeys also need the full-Windows opt-in that PRs into main set in CI) and one opt-in built-service restart test. The Windows suite runs in this PR's CI.

Checklist

  • Scope and target branch follow CONTRIBUTING.md.
  • Relevant tests and documentation/contracts are updated, or not applicable.
  • Affected generated runtime files are included, if applicable; unrelated bundles are unchanged.
  • Diff, examples, and attachments contain no credentials, raw logs, private paths/content, or internal tracker data.
  • Third-party license notices are preserved, if applicable.

…#160)

* docs(openspec): propose the 1.5.2 cleanup, QA and guidance follow-ups

* docs(openspec): tighten the 1.5.2 change after review

* docs(openspec): fix a support scenario and pin the archive steps

* docs(openspec): apply the second review round and keep the system prompt section stable

* docs(openspec): deliver request notes in a carrier valid for the latest message
… and validate receipts (#162)

* fix(companion): clear dependency blocks against current prerequisites and validate receipts before refusing

The moved-back guidance in the skill, tool description and inline guidance now
unblocks against the plan's current prerequisites: a prerequisite the plan no
longer lists no longer holds the task, and a still-listed skipped one counts as
unfinished. Coordinator refusal guidance validates pending and reserved
receipts as the per-plan reader does and reports incomplete evidence instead of
a closed refusal. The retry baseline and point-lookup applicability are
documented.

* docs: describe how malformed delegation receipts affect coordinator guidance
…163)

* fix(ui): report unconfirmed cleanup results apart from skipped plans

A bulk Tidy or selection run now keeps the failure class of each request. A plan the service refused, left out before sending, or never sent after Stop is skipped; an attempted request with no valid answer is reported as unconfirmed and may have been applied. The result line says so in English, Russian and Simplified Chinese. Undo still restores validated receipts only and Try again keeps its behaviour.

The cleanup fixture's service calls wait 30 seconds while its readiness probe stays short, and the selection driver asserts that every plan was archived before it uses Undo.

* fix(ui): agree Russian unconfirmed wording and share the refusal check

Pick the Russian pronoun and participle by the exact count of one, so 21, 31 and 101 read as plural. Export cleanupRefused from the refusal codes cleanupError already uses, and use it in the run engine. Reword the Select bullet about a withdrawn store and the fixture probe comment.

* docs(openspec): mark the fixture check done; the failing drivers predate this change
* fix(ui): bind cleanup busy state to its request, keep capability from the latest health

* fix(ui): drop stale health on announced account change and guard retired Try again
…sts (#165)

* fix(companion): keep the system prompt section identical across requests

The companion's system section carried the one-request hint, the sub-agent
resume capsule (with its plan revision) and the delegation refusal note, so
it changed between requests and defeated provider prompt caching.

The section is now the fixed activation guidance only, byte-identical on
every request where it is present. The hint, capsule and refusal note are
added for one request after the content of its latest message, on a copy so
the stored conversation never carries them: a text part on a user message,
the output of the last tool result on a tool message (not the Code Mode
wrapper result), and nothing on any other role, where the text waits for the
next request with a valid carrier. Providers that drop plugin system
sections now receive these notes too.

Fixes #161

* docs(openspec): keep delivered context notes in place on later requests

* docs(openspec): pin re-delivery, cleared line, keys and memory for context notes
…t it cannot compare (#166)

* test(browser): make the large-library gate count by request and report what it cannot compare

Bound each timed window by log offsets read in the evaluations that start and stop its timer, and take every count the gate compares from the request log inside them. Count run reads once per window as an informational row, keep health reads out of per-refresh traffic, record the attribution method and both inbox forms, compare the list-carried inbox form per list start, and report a budget without a comparable baseline as unverified with a non-zero exit. Document how a baseline is recorded for the current artifact format.

* test(browser): pin the one-uncomparable-candidate rule and align the gate docs

* test(browser): drop measurement data from the baseline docs and tighten the gate's reasons
…ts (#167)

* fix(companion): keep delivered context notes in place on later requests

A context note present on one request and absent from the next still edits the
history: the provider writes its cache at the end of the latest message, where
the note sits, and never reads that entry again. Standing notes (an assigned
child's capsule, an outstanding refusal) went out on every request, so those
sessions got no conversation-history cache, and extended thinking bound to the
prefix was lost too.

The companion now remembers each delivered note per session with its carrier
(tool result: call id, position and a digest of its original output; user
message: its id, else position and a digest of its content) and adds the same
bytes in the same place on every later request that still holds the carrier, so
each request's messages begin with the previous request's. Notes due together
are one note; a capsule or refusal is delivered again only when its text changed
or its carrier is gone; a refusal that stops applying gets one fixed cleared
line after a complete read. The memory is bounded (128 sessions, 64 carriers and
64 KiB per session) and every path that removes the section removes the notes.

Refs #161

* fix(companion): tighten context note memory after review

- An incomplete empty refusal read still delivers the omission text but no
  longer opens the cleared line; only a real refusal does.
- A note too large for its carrier leaves an armed capsule armed.
- The cleared line is delivered again when a revert removes it but keeps the
  refusal it clears.
- Notes stay on the message they were delivered on when user messages share an
  identifier.
- A session has memory only once it holds a note, and the memory is recorded
  only after the notes were added to the request.
- The array is restored again just before keys are computed, so overlapping
  requests on a reused event never hash their own copies.
- Raise the per-session bound to 256 carriers and 128 KiB, so long sessions
  keep the cache of the start of the conversation.
- Hash binary parts by their raw bytes and take the latest carrier once.
…rson (#168)

* fix(ui): keep cleanup repaints and focus moves from disturbing the person

A count that finishes by itself, a Tidy run's progress and the end of a run now repaint as background data, so they wait for a held control or an open picker instead of replacing it. A refresh no longer expires a result that has not been painted yet. A deferred focus move is decided when it is applied and is dropped once focus is anywhere other than the control it was queued from.

* fix(ui): judge a deferred focus move from the control that had focus before the paint

The recheck read the focused element after the paint had replaced the root, so a rebuilt control such as Undo looked like no focus and lost it to Tidy or Cancel. Emptiness and identity are now taken before the root is replaced. forgetPlans keeps its dev signature and no longer bumps a version; each caller picks the repaint lane. The harness replaces a focused control on every paint, and the rendered driver checks that focus on Undo survives the return of Tidy.
* fix(ui): keep Tidy and selection counts exact while plans change

A Tidy or Select all count taken from a list read in more than one page now
says some plans may have been missed, on both steps, without adding a read.
Search freshness replies certify only the result page they were asked about
and only when they covered every plan it shows, are retired by a cleanup in
the frame, and report plans they show gone to the selection whichever page is
shown. A page opened by Load more starts unchecked. A Select all departure
carries the cleanup generation that took the plan out, so a plan restored
elsewhere is counted again.

* fix(ui): keep selection rows, counts and scans in agreement on departed plans

A departed plan known at a newer cleanup generation is now treated the same by
the row, the selection count, the snapshot plans and a scan. PlanSelection.forget
takes only a map of plan to generation. A selection that throws while following
plans a freshness reply showed gone no longer leaves the search half updated.
Document the qualified zero line, clarify the multi-page flag, and run the two
slow search scenarios on one smaller backend.
Run the port-bound backend group in its own lane beside the typechecks, the parallel backend group and the browser and automation tests, so the Linux check step finishes sooner. The serial group stays one --test-concurrency=1 invocation; a listen probe found no other lane binding Setup ports, and the built-service cleanup test joins the serial group when CP_BUILT_SERVICE=1.

- Node compile cache under node_modules/.cache, emptied at each run start and turned off with a note if it cannot be created.
- The Linux jobs skip the zip/unzip install when the tools are present.
- The Windows job runs its two native files concurrently, each waited on as a whole process tree.
- New bun run test:fast and test:all share one plan with CI.
- The lane runner stops every process group it starts on every exit path, retires groups once empty, never signals an unsafe or reused id, handles SIGINT, SIGTERM and SIGHUP, and exits 128 plus the signal when interrupted. Stopping on Windows is best effort and was not run there.

No tests were removed and the counts are unchanged.
Archive the 1.5.0, 1.5.1 and 1.5.2 OpenSpec changes in that order, bump the version to 1.5.2, and add the 1.5.2 release notes and changelog entry.
@Phototonic Phototonic added the area:release Packaging, release files and CI label Nov 18, 2026
Comment thread plugin/activation.ts Resolved
@kilo-code-bot

kilo-code-bot Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 1
WARNING 0
SUGGESTION 0
Issue Details (click to expand)

CRITICAL

File Line Issue
plugin/activation.ts 548 The companion resends cached plan titles and former assignment IDs after deletion or unlinking, even when the current Store read excludes the plan. A different provider used for the same session could receive that data for the first time.
Files Reviewed (124 files)
  • .github/workflows/ci.yml - 0 issues
  • CHANGELOG.md - 0 issues
  • CONTRIBUTING.md - 0 issues
  • background/main.js - 0 issues
  • build/companion/SKILL.md - 0 issues
  • build/companion/index.js - 0 issues
  • build/companion/package.json - 0 issues
  • build/service/main.js - 0 issues
  • build/setup/main.js - 0 issues
  • docs/backend.md - 0 issues
  • docs/compatibility.md - 0 issues
  • docs/contracts.md - 0 issues
  • docs/ui.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-0/design.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-0/proposal.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-0/specs/closed-plan-tidy/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-0/specs/dependency-map-arrow-state/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-0/specs/dependency-map-view-controls/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-0/specs/device-remembered-view-state/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-0/specs/incomplete-count-indicator/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-0/specs/interface-localization/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-0/specs/native-extension-updates/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-0/specs/needs-you-inbox/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-0/specs/phone-progress-surfaces/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-0/specs/plan-mirroring-guidance/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-0/specs/progress-surface-hierarchy/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-0/specs/release-built-outputs/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-0/specs/session-progress-context/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-0/specs/subagent-loss-notices/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-0/specs/windows-setup-responsiveness/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-0/tasks.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-1/design.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-1/proposal.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-1/specs/active-plan-cleanup/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-1/specs/closed-plan-tidy/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-1/specs/dependency-map-view-controls/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-1/specs/incomplete-count-indicator/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-1/specs/large-library-responsiveness/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-1/specs/needs-you-inbox/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-1/specs/plan-mirroring-guidance/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-1/specs/plan-selection-actions/spec.md - 0 issues
  • openspec/changes/archive/2026-11-18-release-1-5-1/tasks.md - 0 issues
  • openspec/changes/archive/2026-11-19-release-1-5-2/design.md - 0 issues
  • openspec/changes/archive/2026-11-19-release-1-5-2/proposal.md - 0 issues
  • openspec/changes/archive/2026-11-19-release-1-5-2/specs/closed-plan-tidy/spec.md - 0 issues
  • openspec/changes/archive/2026-11-19-release-1-5-2/specs/delegation-intent-visibility/spec.md - 0 issues
  • openspec/changes/archive/2026-11-19-release-1-5-2/specs/large-library-responsiveness/spec.md - 0 issues
  • openspec/changes/archive/2026-11-19-release-1-5-2/specs/plan-mirroring-guidance/spec.md - 0 issues
  • openspec/changes/archive/2026-11-19-release-1-5-2/specs/plan-selection-actions/spec.md - 0 issues
  • openspec/changes/archive/2026-11-19-release-1-5-2/tasks.md - 0 issues
  • openspec/specs/active-plan-cleanup/spec.md - 0 issues
  • openspec/specs/closed-plan-tidy/spec.md - 0 issues
  • openspec/specs/delegation-intent-visibility/spec.md - 0 issues
  • openspec/specs/dependency-map-arrow-state/spec.md - 0 issues
  • openspec/specs/dependency-map-view-controls/spec.md - 0 issues
  • openspec/specs/device-remembered-view-state/spec.md - 0 issues
  • openspec/specs/incomplete-count-indicator/spec.md - 0 issues
  • openspec/specs/interface-localization/spec.md - 0 issues
  • openspec/specs/large-library-responsiveness/spec.md - 0 issues
  • openspec/specs/native-extension-updates/spec.md - 0 issues
  • openspec/specs/needs-you-inbox/spec.md - 0 issues
  • openspec/specs/phone-progress-surfaces/spec.md - 0 issues
  • openspec/specs/plan-mirroring-guidance/spec.md - 0 issues
  • openspec/specs/plan-selection-actions/spec.md - 0 issues
  • openspec/specs/progress-surface-hierarchy/spec.md - 0 issues
  • openspec/specs/release-built-outputs/spec.md - 0 issues
  • openspec/specs/session-progress-context/spec.md - 0 issues
  • openspec/specs/subagent-loss-notices/spec.md - 0 issues
  • openspec/specs/windows-setup-responsiveness/spec.md - 0 issues
  • package.json - 0 issues
  • plugin/SKILL.md - 0 issues
  • plugin/activation.ts - 1 issue
  • plugin/index.ts - 0 issues
  • release-notes/1.5.2.md - 0 issues
  • scripts/ci-backend.ts - 0 issues
  • scripts/ci.ts - 0 issues
  • scripts/test-lanes.ts - 0 issues
  • scripts/test-plan.ts - 0 issues
  • scripts/test.ts - 0 issues
  • shared/release.ts - 0 issues
  • shared/subagent-runs.ts - 0 issues
  • tests/automation/ci.test.ts - 0 issues
  • tests/automation/release.test.ts - 0 issues
  • tests/automation/test-lanes.test.ts - 0 issues
  • tests/automation/workflow-triggers.test.ts - 0 issues
  • tests/backend/plan-cleanup-delegation.test.ts - 0 issues
  • tests/backend/progress-activation.test.ts - 0 issues
  • tests/backend/progress-invocation.test.ts - 0 issues
  • tests/backend/progress-provider-view.test.ts - 0 issues
  • tests/backend/progress-resume-activation.test.ts - 0 issues
  • tests/browser/cleanup-result-copy.test.ts - 0 issues
  • tests/browser/cleanup-selection-page.test.ts - 0 issues
  • tests/browser/cleanup-selection-qa.ts - 0 issues
  • tests/browser/cleanup-selection-view.test.ts - 0 issues
  • tests/browser/cleanup-selection.test.ts - 0 issues
  • tests/browser/cleanup-tidy-controller.test.ts - 0 issues
  • tests/browser/cleanup-tidy-qa.ts - 0 issues
  • tests/browser/cleanup-tidy-scan.test.ts - 0 issues
  • tests/browser/cleanup-tidy.test.ts - 0 issues
  • tests/browser/large-library-gate.test.ts - 0 issues
  • tests/browser/large-library-gate.ts - 0 issues
  • tests/browser/large-library-qa.ts - 0 issues
  • tests/browser/plan-task-search-controller.test.ts - 0 issues
  • tests/browser/refresh-attribution.test.ts - 0 issues
  • tests/browser/refresh-attribution.ts - 0 issues
  • tests/fixtures/activation-native-driver.ts - 0 issues
  • tests/fixtures/activation-observer.ts - 0 issues
  • tests/fixtures/activation-production.ts - 0 issues
  • tests/fixtures/cleanup-service.ts - 0 issues
  • tests/fixtures/latest-message-text.ts - 0 issues
  • tests/fixtures/progress-resume-observer.ts - 0 issues
  • tests/fixtures/proxy-shape-probe.ts - 0 issues
  • tests/fixtures/subagent-activity-observer.ts - 0 issues
  • tsconfig.json - 0 issues
  • ui/page/main.js - 0 issues
  • ui/page/main.ts - 0 issues
  • ui/panel/main.js - 0 issues
  • ui/shared/app.ts - 0 issues
  • ui/shared/cleanup-view.ts - 0 issues
  • ui/shared/cleanup.ts - 0 issues
  • ui/shared/model.ts - 0 issues
  • ui/shared/search.ts - 0 issues
  • ui/shared/source.ts - 0 issues
  • ui/status/main.js - 0 issues

Static review only. The GitHub commit patch omitted the generated promotion entries; those were checked against source without rebuilding. No tests or native-host checks were run.


Reviewed by gpt-6.2-sol · Input: 36 · Output: 9K · Cached: 796.4K

@Phototonic

Copy link
Copy Markdown
Owner Author

Superseded by #177, which promotes dev with the Windows fix for #172.

@Phototonic Phototonic closed this Nov 18, 2026
@Phototonic Phototonic mentioned this pull request Nov 18, 2026
5 tasks done
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:release Packaging, release files and CI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

这个扩展会破坏我的缓存命中率

1 participant