Skip to content

superself 0.8.0

Choose a tag to compare

View all tags
@tonite31 tonite31 released this 24 Aug 13:46
· 51 commits to main since this release
v0.8.0
d808ff9
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Superself 0.8.0: carry complete work state between agents

Superself 0.8.0 gives a fresh agent the project rules, work state, reports, and recovery commands it needs to continue active work. It also lets a person revise an unstarted work proposal without replacing its id.

Hand active work to a fresh agent

Run:

self handoff <work-id> [--project <slug>]

The command emits one deterministic packet with the common Superself protocol, applicable conventions, bounded project context, complete work and report history, and recovery guidance for the current lifecycle and execution location.

The packet is read-only. The command accepts exact work ids, appends no event, creates no file, and does not start or switch an agent. Project-controlled text stays inside renderer-owned framing so report or convention content cannot become a packet section.

Revise a proposal before work starts

Run:

self work revise <id> "<revised plan>" --why "<what changed>"

The work id and every earlier plan version remain in the same unit. A revision invalidates the previous acceptance, so a person must accept the new plan before an agent can start it. The first self work start freezes the plan; later corrections use a successor work unit.

Upgrade after publication

After the v0.8.0 release workflow finishes, install the published package:

npm install -g superself@0.8.0

Release preparation checklist

  • Merge the accepted release PR with apps/cli/package.json at 0.8.0.
  • Confirm CI verify, contribution-policy, and dco are green on the release PR.
  • Stop before creating a tag, GitHub Release, or npm publication. Those actions require a separate publication instruction after this preparation is accepted.

Publication handoff after separate approval

These steps are not part of this release preparation. After a maintainer separately authorizes publication:

  1. Create annotated tag v0.8.0 on the release merge commit.
  2. Confirm the tag-triggered Publish workflow successfully publishes npm superself@0.8.0.
  3. Create the GitHub Release for v0.8.0 using the reviewed reader sections above.
  4. Confirm both npm superself@0.8.0 and the GitHub Release are visible before announcing availability.

Evidence

  • PR #357 adds one-id revision of standalone work proposals until first start.
  • PR #359 adds complete read-only work handoff packets.
  • Release policy defines the version, tag, and publication path.
Assets 2
Loading