Skip to content

chore: release v0.0.3#54

Open
ScriptedAlchemy wants to merge 1 commit into
masterfrom
release-plz-2026-06-19T00-58-01Z
Open

chore: release v0.0.3#54
ScriptedAlchemy wants to merge 1 commit into
masterfrom
release-plz-2026-06-19T00-58-01Z

Conversation

@ScriptedAlchemy

Copy link
Copy Markdown
Owner

🤖 New release

  • tracedecay: 0.0.2 -> 0.0.3
Changelog

0.0.3 - 2026-06-19

Other

  • stabilize Windows GC test and cancel stale runs


This PR was generated with release-plz.

@changeset-bot

changeset-bot Bot commented Jun 19, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 5154b85

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5154b85419

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@@ -1,1748 +0,0 @@
# TokenSave LCM Session Rewrite Implementation Plan

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Restore historical superpowers plans/specs

This release commit deletes the LCM rewrite plan, and the same diff removes the matching spec plus the daemon plan/spec, but these historical artifacts are not moved elsewhere (rg for their headings returns no remaining copy). That contradicts the repo’s rebrand policy, which explicitly says old plans/specs should remain unless factually wrong (docs/REBRAND-COMPATIBILITY-POLICY.md:63-68, :292) and the compatibility audit calls these files high-archival-value history (docs/TOKENSAVE-COMPATIBILITY-AUDIT.md:79); losing them also breaks the source anchors embedded in the plan/spec set for future maintenance work.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant