Skip to content

v1.2.0 — the session-boundary pair (9 skills)

Choose a tag to compare

@MrBinnacle MrBinnacle released this 07 Sep 21:45
· 386 commits to main since this release
Immutable release. Only release title and notes can be modified.
07fe466

Delivered 2026-08-10 at 07fe466. 9 published cards, up from 7.

This release record was created on 2026-09-07. The delivery itself happened when the version-bump pull request merged to main, which is what ADR 0002 makes the release event; the tag and this page record it. The tag was pushed on 2026-09-06 and no Release object accompanied it, so this repository's Releases page showed v1.1 as the latest release while four deliveries shipped past it. That gap is what this page closes.

What it delivered

The session-boundary pair. Two cards were added under skills/engineering/, then renamed to im-down and im-up, four verification holes found while adopting them were closed, and their validator suites were wired into CI so the pair is checked on every run rather than on the day it was written.

What the version number promises

The declared surface is the install path and the card format. The card set is not part of it: adding or retiring a card is a minor change, changing the install path or a card's on-disk shape is a major change, and a correction inside a card is a patch. Both documented install routes track main, so a consumer receives changed cards when a version bump merges, not when a tag is pushed.


The session-boundary pair, and the first CI job that runs this collection's own code.

im-down and im-up carry one session's state into the next as an audited packet rather
than as conversational memory. They arrived, were hardened against four verification holes
found while adopting them in a real repository, and were renamed. Nine skills now.

Minor Changes

  • #9 20bae6c — Add the session-boundary pair under skills/engineering/: im-down (producer — one
    atomic packet with a hidden JSON manifest, deterministic snapshot script, and validator) and
    im-up (receiver — treats the packet as untrusted data, verifies branch
    and HEAD, probes typed claims, runs only repository-configured checks, and emits an explicit
    acceptance receipt). Both are human-invoked (disable-model-invocation: true), configured via
    .claude/session-boundary.json, and ship with four fixture classes (clean accepted; stale
    HEAD, missing required field, and failed probe all rejected). No Stop hook ships in this
    release.

  • #11 fc5009c — Rename the session-boundary pair to im-down (producer, session close) and im-up (receiver,
    session start). The old names described the machinery; these describe what the operator is
    actually doing — signing off, and coming back. They also resolve a real collision: the previous
    receiver name was identical to a widely-installed local skill of the same name, so the two
    could not coexist in one library.

    No behavior changes. Directory names, frontmatter name: fields, bucket README, top-level
    README, and the pair's own cross-references all move together, and the validator drift
    assertion tracks the new directory names.

Patch Changes

  • #10 fa81634 — Close four verification holes found while adopting the session-boundary pair in a real
    repository. Each was reproduced against the shipped code before it was changed.

    • A command probe was never executed, yet its claim kept verified and the packet was
      ACCEPTED on an advisory note. Refusing to run packet-supplied commands was the right call;
      leaving the status untouched let any unverifiable claim be laundered by choosing that probe
      kind. A command probe now runs only when the repository config authorises the exact command
      (receiver_checks or the new trusted_probe_commands), and an unlisted probe rejects the
      packet.
    • Receive mode without --config skipped every configured check and still returned ACCEPTED.
      It now rejects: a verification an omitted argument switches off is not a verification.
    • The example receiver_checks entry was git status --porcelain, which exits zero on a
      clean tree, a dirty tree, and a deleted tracked file alike, so the only shipped example
      could not fail. The example is now git diff --quiet && git diff --cached --quiet, and the
      validator reports a known always-zero check as a note.
    • A narrative sentence quoting a ticket title containing the word TODO rejected an otherwise
      valid packet. __REQUIRED__ remains a hard rejection; TODO and TBD now reject only as a
      whole-line placeholder or a manifest value that is nothing but the token.

    Also documents the produce-after-final-commit ordering (committing the packet moves HEAD and
    makes the packet reject itself) and adds a drift assertion so the validator copy shipped in
    both skill directories cannot diverge silently. The fixture suite grows from four cases to
    nine.

  • #12 9b5d3bb — Run the session-boundary validator suites in CI. Two skills in this collection ship
    executable code and the collection had no job that executed it — only the link check and
    the de-personalization gate.

    The job invokes each suite through its real entrypoint rather than through pytest, and
    that is the point of it. The cases run from if __name__ == "__main__" and the functions
    carry no test_ prefix, so pytest collects nothing from either file and reports
    "no tests ran" — a green line that means the opposite of what it looks like. The job
    asserts each suite's PASS: line so a suite that does not execute cannot report success,
    and a poison control asserts the shipped validator still rejects a stale packet, because a
    gate that cannot fail guards nothing. Both skills record the pytest false-green in their
    gotchas. Runs on Linux and Windows, the platform the pair is actually used on.