docs(migration): fix min session command names in activate/attach exa…

…mple

chore: added user policy reference doc and tweaked loadout docs (gomi…

…nimal#1091)

fix(ci): reclaim the session e2e's state dir so the soak stops fillin…

…g the runner (gominimal#1021)

test(switch): exclude filesystem tests from Miri (gominimal#1079)

The miri job in nightly-tests aborts on the first switch test that
touches the filesystem: tempfile::tempdir() calls mkdir, which is
unsupported under Miri's default isolation. Six resolver tests hit
this, so Miri verified almost nothing before aborting.

Annotate those six tests with #[cfg_attr(miri, ignore)] so Miri still
covers the pure subnet/MAC/vsock primitives it was added to check.
The tests run unchanged outside Miri.

Co-authored-by: gominimal-aw-bot[bot] <281738952+gominimal-aw-bot[bot]@users.noreply.github.com>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

chore(deps): update third-party crates (gominimal#991)

Bump nickel-lang-core's pinned git rev from e8a0ab95 (2026-06-17) to
0d306feb (2026-07-26), 32 commits upstream. Picks up a std.string.find
panic fix on a match at the end of the string, a parse fix for negative
number literals in match patterns, and new std.array.chunk/group plus a
merge-sort std.array.sort. Stays on the git rev deliberately: crates.io's
newest release (0.18.0) lags master by a long way, so the old "revert to
crates.io once released" note is replaced with the actual rationale.

hakoniwa is already at the latest upstream release (1.7.2); no change.

Also:
- serial_test 3 -> 4 (dev-dep; needs Rust 1.93.1, under our 1.97.0 pin).
- clap/clap_complete 4.5 -> 4.6 in the manifest. The lockfile already
  resolved 4.6.4/4.6.8 since ^4.5 admits 4.6, so this changes no
  resolution; it drops a stale comment whose stated cause
  (c2rust-bitfields' exact proc-macro2 pin via tun-rs) is no longer in
  the tree at all.
- cargo update within semver: aes, cc, jiff, rustls-pki-types, schemars,
  toml_parser.
- rand_core stays at 0.6 (documented, matches boringtun/x25519-dalek).

Document why the google-cloud-* / reqwest cluster resolves below its
latest releases: reqwest >= 0.13.2 pulls js-sys >= 0.3.85, which requires
an exact wasm-bindgen =0.2.108, while nickel's `format` feature reaches
topiary-tree-sitter-facade, which pins =0.2.100. The two cannot unify, so
the resolver silently freezes the cluster.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

fix(OSX timekeeping): self-manage timekeeping on OSX (gominimal#986)

docs: document the release and install pipeline (gominimal#867)

* docs: document the release and install pipeline

Add docs/internal/release-pipeline.md, a maintainer-facing runbook for the
release/install pipeline: release.yml, the stable/unstable/nightly channels,
staging, promotion, pruning, and the operator steps. Marked internal
(publicly visible in the repo, not published to the docs site).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* docs: document nightly-provenance gate and override_provenance input in release-pipeline.md (gominimal#900)

Co-authored-by: macroscopeapp[bot] <170038800+macroscopeapp[bot]@users.noreply.github.com>

* docs: remove the private docs-repo reference from the promote runbook

The reference-docs promotion dispatch named the docs-site repo and its
GitHub App. That repo is private, so this public repo should not announce
it, and the promote pipeline is being reshaped besides. Describe the
`reference-docs-promoted` dispatch abstractly (it triggers a
docs.minimal.dev rebuild) without naming the target repo.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* fix(release): verify smoke tests actually ran in nightly provenance check (gominimal#911)

Co-authored-by: macroscopeapp[bot] <170038800+macroscopeapp[bot]@users.noreply.github.com>

* docs: remove em-dashes and fix the version-source binary in the release runbook

* fix(scripts): close the no-op-nightly loophole in the provenance gate

smoke-success is if: always() and skip-tolerant, so a no-op nightly run (SHA
already staged, smokes skipped) still concluded success and could vouch for a
version that was never smoked. The gate now also requires the Linux smoke
jobs themselves to have run and passed; smoke-macos alone may be skipped by
the RUN_MACOS_CI kill-switch. Test fixtures move to name/conclusion pairs and
cover the real no-op shape and the kill-switch shape (31 tests). The runbook
text now states the guarantee precisely, drops the unsourced retirement
claim, and documents the channel-endpoint target override.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: macroscopeapp[bot] <170038800+macroscopeapp[bot]@users.noreply.github.com>

fix(minimald): reset terminal + provide message to attached sessions …

…when shutting down

fix(minimald): fix resizing terminal (gominimal#969)

feat(minimal): tab complete session ID/names (gominimal#966)