From 1f3cd115342f3847113574d50c79456824ac2a60 Mon Sep 17 00:00:00 2001 From: twilightsaurus <133054450+twilightsaurus@users.noreply.github.com> Date: Fri, 30 Oct 2026 10:51:18 +0200 Subject: [PATCH] docs: record blocked Slice 26 published-artifact acceptance --- docs/roadmap.md | 33 ++++++++++++++++++++++---- docs/status.md | 63 ++++++++++++++++++++++++++++++++++++++++++++++++- 2 files changed, 90 insertions(+), 6 deletions(-) diff --git a/docs/roadmap.md b/docs/roadmap.md index c72f9d3..ef7cf53 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -797,7 +797,8 @@ infrastructure acceptance remains pending. retained policy under one legacy-baseline journal, then uses the existing new-token handoff and commit. Unsafe state is refused; rollback stops the listener before restoring legacy policy. -5. Installation documentation and completion-message corrections (implemented): +5. Installation documentation and completion-message corrections (landed in + [#52](https://github.com/i-mud/imp/pull/52)): preserve the already-truthful retained Direct output (configuration preserved, no public verification and no new token); avoid readiness claims for SSH `--no-start`; distinguish fresh install-only from upgrades preserving existing @@ -809,14 +810,36 @@ decision; public-edge ownership, provisioning, credentials, and rollback remain unchanged. PR4 narrowly extends legacy enable/rollback and gives new Direct installer journals per-invocation ownership; ordinary migrations and credential provisioning are unchanged. -These implementations do not claim live infrastructure acceptance or inclusion -in a particular published artifact. Item 5 passed 12 actual-installer smoke -scenarios, five installer fixture tests and `npm run check`; its smoke used -fixture runtime/systemd/public-edge boundaries, not live infrastructure. The +Implementation and fixture evidence alone do not establish live infrastructure +acceptance. Item 5 passed 12 actual-installer smoke scenarios, five installer +fixture tests and `npm run check`; its smoke used fixture +runtime/systemd/public-edge boundaries, not live infrastructure. The earlier Slice 25 PASS evidence does not accept these later changes. One-level include inspection does not solve arbitrary nested includes, and real-runtime CI remains a separate open follow-up. +**2026-10-30 — published v0.4.6 Phase A: artifact verification PASS; live +acceptance/closure BLOCKED.** [Dated evidence and matrix](status.md#2026-10-30--published-v046-read-only-acceptance-blocked) +record the release identity, checksums (50/50 internal), and guarded frozen +runtime smoke with host Python denied. The operator authorized no VPS/desktop +changes; no isolated hosts were available. The active 0.4.1 VPS and existing TF +session were left untouched; an occupied unrelated VPS was excluded. Local +Windows 0.4.0 is not the separately observed, version-unverified remote Windows +environment. No live changes required restoration. + +Remaining live boundaries are actual TF startup selection/hook-before-login; +published Windows NSIS and native credential cancel/removal/blank-token/ +replacement/restart persistence; Direct fresh/retained installation and +credential preservation; real router/NAT preflight, confirmation and external +reachability; disposable exact-owned inactive schema-1 Direct and schema-2 NAT +missing-`gateway.env` recovery with real systemd/Caddy/TLS, guarded commit/refusal +and rollback; live completion messages for Direct, SSH `--no-start`, +install-only and upgrade; and external public verification including TLS, +authentication and raw-target security probes. Current inventory and unchanged +observed metadata do not prove TLS ownership or complete service-state +preservation. **Slice 26 remains In progress**; nested includes and real-runtime +CI remain open as above. + ## Candidate work Unordered, deliberately without slice numbers, and provisional. Live evidence diff --git a/docs/status.md b/docs/status.md index b430160..2a362d7 100644 --- a/docs/status.md +++ b/docs/status.md @@ -57,7 +57,8 @@ warning; PR3 [#50](https://github.com/i-mud/imp/pull/50) landed NAT preflight classification; PR4 [#51](https://github.com/i-mud/imp/pull/51) landed exact-owned retained-edge recovery. -Item 5 implements completion-message and installation-doc corrections: retained +Item 5 ([#52](https://github.com/i-mud/imp/pull/52)) implements completion-message +and installation-doc corrections: retained Direct already reports preservation, no public verification and no new token; SSH `--no-start` makes no readiness claim; fresh install-only is distinguished from an upgrade that preserves connection configuration. @@ -73,6 +74,66 @@ claims. One-level literal include inspection does not cover arbitrary nested startup includes, and real Caddy/native TinyFugue runtime CI remains open. See the [Slice 26 scope and evidence limits](roadmap.md#slice-26---installation-reliability-and-onboarding). +### 2026-10-30 — published v0.4.6 read-only acceptance: BLOCKED + +**Phase A artifact verification passed; Slice 26 live acceptance and closure +remain BLOCKED.** The operator authorized no VPS or desktop changes, required +the existing TinyFugue session to remain untouched, and had no isolated hosts +available. This is bounded read-only evidence, not a complete environment audit +or a replacement for the historical Slice 25 acceptance above. + +Published release: [v0.4.6](https://github.com/i-mud/imp/releases/tag/v0.4.6). +Signed annotated tag `00f904d15ce0c9c913ab09f1171d5f2f6b687fbc` resolves to +commit `f952f5f89e18681e36fff3b465742a63e5641d17`; GitHub reported its signature +valid. [Release run 41007081793](https://github.com/i-mud/imp/actions/runs/41007081793) +passed semantic-release, tag verification, Linux build/frozen acceptance, +Windows NSIS build and publication. + +| Downloaded asset | SHA256 | +| ------------------------ | ------------------------------------------------------------------ | +| Linux server archive | `c28502bf87ea74e8452d951c192df8a929950a0fb91c57f870b03307a912a313` | +| Published checksum asset | `3c88872679b5b64f2c895bfe9ec5e629119840325fb6656b44463db5c5b38836` | +| Windows NSIS installer | `b20a74bdd26d489b394c6e955a3abac886e46e9f0cb5384a21a71fe6a840627b` | + +The Linux archive matched its published checksum; extracted internal checksums +passed **50/50**, and `VERSION`/`BUILD_INFO` reported **0.4.6**. Under the existing +`scripts/exec-guard.py` Landlock guard (ABI 7), with Python environment variables +unset and `PATH=/nonexistent`, published `relay --help` and +`runtime-check 0.4.6` exited 0. Both system and venv Python execution were denied +with exit 126. Developer Python launched the guard, but the frozen child did not +require host Python. This proves bounded frozen startup/version validation, +not live service operation. Unsupported top-level `--help`/`--version` probes +are not defects. + +**Observed inventory, not accepted targets:** the active VPS still ran 0.4.1 +with a schema-3 Direct edge and an existing TF session. A second VPS had occupied +public ports and unrelated services and was excluded, not treated as disposable. +Local Windows had installed Imp 0.4.0; a separately observed remote Windows host's +Imp version remained unverified. No actual router/NAT target or disposable +schema-1/schema-2 legacy targets were established. + +| Required live coverage | Result / missing boundary | +| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | +| PR #48 — TF startup onboarding | BLOCKED: actual startup selection, hook-before-login and real operator invocation not exercised. | +| PR #49 — saved Direct credentials | BLOCKED: no desktop UI run for cancel/pending edits, confirmed removal, blank-token preservation, replacement or restart persistence. | +| PR #50 — NAT classification | BLOCKED: no authorized real Direct/NAT preflight and installer confirmation path. | +| PR #51 — retained-edge recovery | BLOCKED: no isolated exact-owned inactive legacy edge, guarded commit/refusal or rollback acceptance. | +| PR #52 — installation messages/docs | BLOCKED: no live fresh/retained Direct, SSH `--no-start`, install-only or upgrade flow; fixture results above are not live evidence. | +| Direct VPS | BLOCKED: no authorized v0.4.6 install/reinstall or retained-credential test; current inventory is not acceptance. | +| Router/NAT | BLOCKED: no approved private host/router-forward environment or external reachability test. | +| Schema-1 Direct / schema-2 NAT | BLOCKED: disposable exact-owned inactive fixtures with missing `gateway.env`, real systemd/Caddy/TLS, commit and rollback remain required. | +| Windows published NSIS | BLOCKED: no authorized isolated profile, installation or native UI/persistence run. | +| Public security | BLOCKED: no external verifier, TLS/auth/raw-target probes or public acceptance run. | + +No installs, restarts, credential rotation/replacement, TF startup edits, login +or action were attempted. A final read-only VPS recheck still observed 0.4.1, +the same enabled/active relay/feed/gateway/Caddy PIDs, one TF process, unchanged +hashes for the three observed public-edge files, and unchanged `gateway.env` +mode/size metadata. Credential bytes and certificate storage were not compared; +exact generated-edge/TLS ownership and complete service-state preservation were +not proven. **No live changes were made, so no rollback/restoration was needed.** +All five work-item live results remain BLOCKED; Slice 26 stays **In progress**. + ## Working end to end Imp currently supports TinyFugue and Mudlet as MUD-client adapters. Both feed