docs(tasks): close w5-publish — alkssh 0.1.0 published, resolvable on crates.io

tasks/implementation/w5-publish.md

@@ -1,7 +1,7 @@
 ---
 id: w5-publish
 name: Wave 5 — the publish of alkssh 0.1
-status: in-progress
+status: completed
 depends_on: [review-wave-5]
 scope: narrow
 risk: medium
@@ -47,15 +47,15 @@ The checklist:
 
 ## Acceptance Criteria
 
-- [ ] Manifest sanity verified + recorded (no version bump needed —
+- [x] Manifest sanity verified + recorded (no version bump needed —
       0.1.0 is the manifest value)
-- [ ] The full verification set green at the publish commit
-- [ ] The dry-run clean at the publish commit
-- [ ] The `alkssh-v0.1.0` tag on the publish commit
-- [ ] `cargo publish` executed; the published 0.1.0 verified
+- [x] The full verification set green at the publish commit
+- [x] The dry-run clean at the publish commit
+- [x] The `alkssh-v0.1.0` tag on the publish commit
+- [x] `cargo publish` executed; the published 0.1.0 verified
       resolvable on crates.io (or the credential absence booked —
       never a silent skip)
-- [ ] The plan's closure recorded in
+- [x] The plan's closure recorded in
       `docs/plans/implementation.md`
 
 ## References
@@ -110,7 +110,34 @@ green `review-wave-5` verdict at `9383e95`.
   status → `closed`, the wave-5 row → `published`, and the §Plan
   closure note (the freeze inventory one-way; the still-booked
   upstream asks) land in the tagged commit.
+- **The publish-commit dry-run rider**: the closure edits touch only
+  package-excluded paths (`docs/plans/`, `tasks/`), but the dry-run
+  was nonetheless re-executed at the publish commit itself (`e59ef79`)
+  — clean again, same 76-file package.
 
 ## Summary
 
-> To be filled on completion
+**`alkssh 0.1.0` published — crates.io, 2026-10-30.** Publish commit
+`e59ef79`, tagged **`alkssh-v0.1.0`** (crate-qualified, the alkgit
+tag convention), pushed to `origin/main` with the tag. The checklist
+ran in order over the green `review-wave-5` verdict at `9383e95`:
+manifest sanity verified (no bump — 0.1.0 the manifest value;
+edition 2024; `rust-version` 1.89; both license files; the pins
+exactly as ADR-002 records them; the package-policy `exclude` list;
+the feature graph exactly ADR-003's); the full verification set green
+(`scripts/matrix.sh` — six builds' `cargo test`, clippy ×2 -D
+warnings, fmt, doc with the doctests compile-checked; the fuzz
+corpus gate 11/11); `cargo publish --dry-run --allow-dirty` clean
+twice (76 files, packaged-compile verified, once pre-commit and once
+at `e59ef79`; the package list against policy — architecture docs
+ship, process surface and `fuzz/` do not). `cargo publish` completed
+live (`Published alkssh v0.1.0 at registry crates-io` — the
+environment carried the credentials, no operator handover, no silent
+skip). Resolvability verified post-publish: `cargo search alkssh`
+lists `alkssh = "0.1.0"` and a fresh `cargo add alkssh` in a clean
+scratch project resolved it off the index. The plan's closure is
+recorded in `docs/plans/implementation.md` (§Plan closure) on the
+publish commit: the freeze inventory (mapping contracts, honest
+advertisement, decline-matrix behavior, fingerprint format, the
+russh pin's wire posture) is one-way from here; the upstream asks
+stay booked with their owners. **The implementation plan is closed.**