BUG: instructions — inbox skill rollout omits the station02 executable

[andrei-hasna]

Reproduction

On station02, the installed inbox skill resolves, but both canonical executable paths are absent. Running inbox --help exits 127.

On station01, the same canonical helper is installed as inbox 1.3.0; its SHA-256 is 14381a75dae08caca7980eefb1c3f352bc45ddbfa77964532ba898db929299d4 and the local launcher symlink resolves to it.

The supported machines-file-transfer dry-run accepted a no-clobber station01-to-station02 recovery plan, but apply failed closed with remote_operation_failed. No raw scp fallback was used.

Expected

The instructions/skills rollout that installs the inbox skill also installs the package-owned executable and launcher on every managed station, and verifies inbox --help plus a nonzero subscription/status baseline.

Impact

Interactive sessions on station02 cannot arm the required package-owned inbox watcher and must rely on scheduled coordination reads. This is a fleet rollout drift, not an inbox command defect.

Deduplication evidence

Public GitHub searches for open Hasna issues with inbox in the title and open Hasna pull requests mentioning inbox found no matching live fixer. The production Todos search path is intentionally non-runnable until the protected task-manifest authority in the Email Triage prerequisite is deployed; no unsafe collection read was used.

Acceptance

• Identify and repair the source-owned rollout/install path.
• Add a regression proving a managed target cannot report the inbox skill present while the executable is absent.
• Roll out to station02 through the supported distribution path.
• Verify the installed executable checksum/version, launcher resolution, seeded status, and watcher startup.
• Land through a reviewed PR; no manual copied binary is the terminal fix.

[andrei-hasna]

Impact evidence: while station02 lacked the package-owned inbox executable, this interactive session published and installed @hasna/todos@0.15.7 on station02 and station01 before seeing incidents#677782 / the subsequent deprecation. No authority write occurred; both stations were restored to their exact pre-install versions. The existing 15-minute coordination loop was repeatedly deferred while the session was busy, so it did not provide the required incident-delivery latency. This makes executable rollout plus actual prompt delivery an acceptance gate, not optional monitor hygiene.

[andrei-hasna]

PR #66 is open at exact head 652a96f66f4af7233363ec514819bf6dddc6ff4e.

The source fix replaces the missing legacy inbox executable dependency with a package-owned skill contract and managed runtime reconciliation. It updates installed skill homes atomically, refuses symlink/non-regular targets, and keeps a bounded digest/DM/blockers fallback while hosted watch is degraded.

The readiness gate is intentionally split:

• package/version/watch flags must pass;
• hosted heartbeat must pass;
• one subscribed-channel canary and one direct-message canary must actually arrive.

As of August 7, 2026, hasnaxyz/iapp-conversations#6 is merged, but hasna/conversations#95 remains open and live hosted watcher acceptance has not been recorded. Heartbeat-only is therefore not reported as ready.

Validation: full suite 628/0, affected lane 14/0, typecheck/build/storage-kit clean, Instructions and package scans clean, explicit profile render dry-run clean, package dry-run contains the inbox skill asset, and staged scans are clean. No station02 managed output was changed.