alkgen/tasks/implementation/w3-publish.md

id, name, status, depends_on, scope, risk, impact, level

id	name	status	depends_on	scope	risk	impact	level
w3-publish	Wave 3: the publish of alkgen 0.1.0	completed	review-wave-3	narrow	medium	project	implementation

Description

The publish, which is the plan's closing act (docs/plans/ implementation.md §Plan closure): executes only over the green review-wave-3 verdict (the gate stays a pure review; the publish is its own task). The checklist:

• Manifest sanity: version 0.1.0 (verify, no bump), the rust-version/edition posture, license files present, the dep pins as ADR-002 records them (handlebars 6.4 on default features off the crate's default = []), the feature graph (bast-codegen declared, gating nothing), the fixed exclude list.
• The full verification set at the publish commit: cargo test, cargo test --all-features, clippy × 2 (--all-targets -D warnings), cargo fmt --check, cargo doc --no-deps, the wasm release build (standing), taskgraph validate, plus the ADR-002 tree inspection (no dir_source, no script_helper).
• The dry-run: cargo publish --dry-run --allow-dirty clean at the publish commit, the package file list spot-checked once more.
• The tag: the crate-qualified alkgen-v0.1.0 on the publish commit (the family convention: a bare v0.1.0 would be ambiguous across the family).
• The publish: cargo publish; the published version verified resolvable on crates.io afterward. If the publish credential is unavailable, the task stops and books it, never silently skipping; everything before the credential step still lands (tag
  • records).
• The plan's closure recorded in docs/plans/implementation.md: the wave-3 row, the status flip to closed at the publish, and the closure note (the freeze inventory's surfaces are one-way from the publish: the public API shape, the strict-mode and determinism postures, the error model's evolution policy, the handlebars pin's behavior).

Acceptance Criteria

• Manifest sanity verified and recorded
• The full verification set green at the publish commit
• The dry-run clean at the publish commit, file list checked
• The alkgen-v0.1.0 tag on the publish commit
• cargo publish executed; the published 0.1.0 verified on crates.io (or the credential absence booked, never a silent skip)
• The plan's closure recorded (wave-3 row, status closed, the freeze surfaces noted one-way)

References

• docs/plans/implementation.md (§Wave 3 the publish bullet, §Plan closure, §Scope authority: v0.1.0 publishes the crate)
• tasks/implementation/review-wave-3.md (the verdict this executes over)
• /workspace/@alkdev/alkssh tasks/implementation/w5-publish.md (the sibling publish shape this mirrors)

Notes

Filled by the implementation agent (2026-11-07), executing over the green review-wave-3 verdict.

• Manifest sanity verified (no bump; 0.1.0 is the manifest value): version 0.1.0, edition 2021, rust-version 1.85, license = "MIT OR Apache-2.0" with LICENSE-MIT + LICENSE-APACHE present, the pins exactly as the freeze inventory records them (handlebars 6.4, serde 1 derive, serde_json 1 with preserve_order, thiserror 2; default = [], bast-codegen declared and gating nothing), the package-policy exclude list in its fixed form, the readme/categories/keywords metadata in place.
• The full verification set green at the publish tree: cargo test (53: 19 lib + 13 conformance + 7 code_proof + 4 ssr_proof + 5 code_fixtures + 3 ssr_fixtures + 2 doctests), cargo test --all-features (identical), cargo clippy --all-targets --all-features -- -D warnings (clean), cargo fmt --check (clean), cargo doc --no-deps (warning-free), cargo build --target wasm32-unknown-unknown --release (clean), taskgraph validate (21 tasks valid), the ADR-002 tree inspection (handlebars v6.4.4 default only), the standing em-dash grep (zero hits).
• The dry-run clean at the publish commit: cargo publish --dry-run --allow-dirty clean (48 files, 199.6KiB, package compile verification passing); cargo package --list re-checked: only src, tests + fixtures, docs/architecture/, README, CHANGELOG, both licenses, manifests; none of the excluded surface (AGENTS.md, .opencode/, docs/plans|reviews|research/, docs/sdd_process.md, tasks/).
• The publish credential is present in this environment (the registry token), following the alkssh sibling convention: the publish executes live, no operator handover; had it been absent the task would have stopped and booked it here.
• The closure records ride the publish commit: the plan file's status flipped to closed, the wave-3 row to published, and the closure note (freeze inventory one-way; future engine-owned sets through successor waves) land in the tagged commit. The closure edits touch only package-excluded paths (docs/plans/, tasks/), so the packaged payload is unchanged from the dry-run.