Skip to content

revert(twister): withdraw the per-focus memory and status-brief surface - #380

Merged
KrisBraun merged 1 commit into
mainfrom
revert-plot-memory-surface
Aug 7, 2026
Merged

revert(twister): withdraw the per-focus memory and status-brief surface#380
KrisBraun merged 1 commit into
mainfrom
revert-plot-memory-surface

Conversation

@KrisBraun

Copy link
Copy Markdown
Contributor

Reverts the addition of getMemory(), setMemory() and getBriefs() to the Plot tool, along with the FocusMemoryEntry and FocusBrief types.

Why

The platform does not implement these methods yet. As things stand, a twist that declares FocusAccess.Full and calls any of them type-checks cleanly against the SDK and then fails at runtime — the SDK surface promises an answer the platform has no handler for. Withdrawing them keeps the declared surface an accurate description of what the platform actually responds to.

They will return alongside the platform support, unchanged in shape.

No published version is affected

The methods were added after 0.92.0 and their changeset was never consumed by a release, so they never reached npm. 0.92.0 — the current latest — does not contain them, and no twist can be depending on them from a published package.

The changeset is therefore deleted rather than replaced with a "removed" entry: nothing user-visible changed between published versions, so a changelog line describing the removal would document a version that never existed.

Verification

  • twister build clean, 77 tests passing.
  • pnpm validate-changesets passes on the two remaining changesets.
  • No other reference to the removed symbols anywhere in the repository — the only hits are in twister/src/llm-docs/, which is generated at build time and gitignored, and regenerates without them.

🤖 Generated with Claude Code

Reverts the addition of getMemory(), setMemory() and getBriefs() to the
Plot tool, along with the FocusMemoryEntry and FocusBrief types.
The platform does not implement these methods yet, so a twist that
declared FocusAccess.Full and called them would type-check against the
SDK and then fail at runtime. Withdrawing them keeps the SDK surface an
accurate description of what the platform actually answers.
No published version is affected: the methods were added after 0.92.0
and their changeset had not been consumed by a release, so they never
reached npm. The changeset is removed with them rather than replaced,
because nothing user-visible changed between published versions.
They will return alongside the platform support.
@KrisBraun
KrisBraun merged commit 4117c50 into mainAug 7, 2026
1 check passed
@KrisBraun
KrisBraun deleted the revert-plot-memory-surface branch August 7, 2026 04:42
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@KrisBraun