> Requires spt-core **v0.27.0 or newer** (unchanged). Update with `spt adapter update claude-spt`. Plugin skeleton **0.1.18** (structural change — run `/sptc:update` or reinstall the plugin to pick it up).

### Added
- **`/sptc:knock` — ask another agent for permission to reach it, and answer the asks you receive.** Knocking is how access is granted between agents: messaging, and the terminal surfaces that let one agent view or drive another's session. It is a different thing from `/sptc:subnet`, which pairs whole machines, and the two were easy to confuse with only one of them having a command. The skill covers the whole set: ask, see what is waiting for you, approve or refuse, mint an invite code to hand out, and redeem one you were given. Knocks stay quiet on purpose — a knock lands in the recipient's inbox and is never pushed at them, so nothing notifies you and nothing polls on your behalf; run the skill to look. That silence is deliberate, not a missed message.

### Changed
- **A long-running command run in the foreground now gets a reminder to background it.** Your perch is unreachable for the whole time such a command runs, and this was the most common way agents went quiet without meaning to — builds, releases, test suites and searches across a whole repository. The reminder appears before the command runs, at most three times in a turn so it stays a nudge and never becomes noise. It is advice only: nothing is blocked and no command is refused.

### Fixed
- **A message that arrives while you are handing over to your next session is no longer delivered into the session that is about to end.** Saving your context and clearing takes effect at the end of the turn, not the moment you ask for it, and until now anything arriving in that gap was delivered to you anyway — so you would answer it, sometimes write a second handover, and both would be lost when the clear happened. Messages arriving in that window are now held and delivered to your new session instead, which is where you can actually act on them. Messages you send are unaffected and keep going out normally throughout.
- **A handover whose clear never happens no longer leaves you unreachable.** The hold above only works while the endpoint is marked busy, so if the clear were lost the endpoint could stay that way and quietly stockpile everything sent to it. Starting any new turn, or starting any new session, now proves the clear did not happen and releases the hold, and a hold older than fifteen minutes releases on its own. Recovery needs nothing from you: the next thing that happens in the session restores delivery.