diff --git a/.opencode/skills/release-workflow/SKILL.md b/.opencode/skills/release-workflow/SKILL.md index 05f7349..119ea55 100644 --- a/.opencode/skills/release-workflow/SKILL.md +++ b/.opencode/skills/release-workflow/SKILL.md @@ -31,8 +31,9 @@ to ship in seam → adapter → leaf order. ## The exact-pin cascade -`eggup-eggpack` pins its Eggup dependencies exactly (`=0.2.0`). Every other -crate uses a caret requirement. Consequence: +The current `eggup-eggpack` workspace source pins its Eggup dependencies +exactly to `=0.2.1`; the published `eggup-eggpack 0.2.0` remains pinned to +`=0.2.0`. Every other workspace crate uses a caret requirement. Consequence: - A fix published to a caret consumer (`eggup-curl`, `eggup-eggfetch`, `eggup-service`) is inherited automatically on the next resolve — **within the diff --git a/AGENTS.md b/AGENTS.md index 539b7e8..6c7495b 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -19,7 +19,7 @@ Full dependency rules and per-crate boundary rationale: - `crates/eggup-curl` — external-curl adapter, no embedded HTTP/TLS stack; depends only on `eggup-acquisition`. Must not know `eggup-eggfetch` exists. Transport composition lives in the seam, never in an adapter. - `crates/eggup-service` — manager-neutral lifecycle; depends only on `eggup-core` (+ `windows-args`, + `windows-service` on Windows). - `crates/eggup-archive` — bounded allowlisted local tar.gz/zip extraction; deps `tar`, `zip`, `flate2`, `fs_at`, `sha2`, dev-dep `eggup-core`. No transport, authenticity, or live-installation policy. -- `crates/eggup-eggpack` — optional leaf adapter for Eggpack ReleaseManifest v1; published (`=0.2.0`), depends on `core` + `archive` + `acquisition` (each pinned `=0.2.0`, local paths) + `eggpack-manifest = "=0.1.1"` from the registry; its exact dependency list is owned by `crates/eggup-eggpack/Cargo.toml`. Only crate allowed to touch producer types. +- `crates/eggup-eggpack` — optional leaf adapter for Eggpack ReleaseManifest v1; latest published version is `0.2.0` (its immutable package pins Eggup dependencies at `=0.2.0`). The workspace source candidate is `0.2.1` and its three local pins are `=0.2.1`; it depends on `core` + `archive` + `acquisition` (local paths) + `eggpack-manifest = "=0.1.1"` from the registry. Its exact dependency list is owned by `crates/eggup-eggpack/Cargo.toml`. Only crate allowed to touch producer types. - `crates/eggup-transport-footprint` — non-published (`publish = false`) footprint fixtures: `curl_only` / `eggfetch_only` / `dual` binaries behind `required-features`, with a source-level linkage-discipline guard in `tests/cross_link_guard.rs`. The isolated single-adapter configurations are built by `stable` and `macos` and checked at the MSRV floor by `msrv`; `windows-check` builds none of them. New crates must join `Cargo.toml` members, inherit the 5 shared keys (`version`, `edition`, `rust-version`, `license`, `repository`), and set `[lints] workspace = true`. The 7 library crates also carry `#![forbid(unsafe_code)]` and `#![deny(missing_docs)]`; `eggup-transport-footprint` is the sole exception (binary-only, no `lib.rs`, and no `README.md`/`CHANGELOG.md` — see §3.4 of the governance deep dive). @@ -35,7 +35,8 @@ gaps are in [`architecture/tooling-governance.md`](architecture/tooling-governan # + cargo clippy --workspace --all-targets --all-features --locked -- -D warnings # + cargo test --workspace --all-targets --all-features --locked # + cargo doc --workspace --no-deps --locked -# + cargo tree --workspace --locked # review step, not a gate +# + cargo tree --workspace --locked # executed for resolution; review boundary output manually +# + ./scripts/check-docs-truth.sh # source versions, published versions, and docs truth ``` `cargo tree` always exits 0 on a resolvable graph. Read it: the dependency-boundary rules are enforced by **human review only**. diff --git a/CHANGELOG.md b/CHANGELOG.md index 31ceacc..69a8f1f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -403,10 +403,12 @@ claims are made by any of these crates. ## Unreleased -Nothing in this section has been published. The current published baselines -are `0.2.0` for all seven published crates; `eggup-transport-footprint` is -`publish = false` and has no registry version. This dependency refresh does -not authorize publication or consumer migration. +Nothing in this section has been published. The latest published version is +`0.2.0` for all seven publishable crates; `eggup-transport-footprint` is +`publish = false` and has no registry version. This section includes M007 +dependency maintenance and M016 preparation of an `eggup-core 0.2.1` package +candidate. Neither records explicit upload authorization or a publication, and +no consumer migration has occurred. - `eggup-archive`: update the ZIP dependency from `6.0.0` to `9.6.1`, keeping explicit bounded extraction behavior and the public API unchanged. This @@ -417,6 +419,13 @@ not authorize publication or consumer migration. `eggup-eggpack 0.2.0` package. - Refresh compatible lockfile dependencies, including the patched Rustls, `rustls-webpki`, and `webpki-roots` versions. +- `eggup-core` M016: prepare the `0.2.1` package to include the three existing + authoritative contract documents. This is package-content-only; the Core + `0.2.0` registry artifact remains unchanged, and the candidate is not yet published. +- `eggup-eggpack`: align the three local exact pins to workspace source version + `=0.2.1`. The published `eggup-eggpack 0.2.0` archive and its `=0.2.0` pins + are unchanged; the `0.2.1` source candidate is not yet published, and no + Eggpack publication is authorized. ## 0.1.1 diff --git a/Cargo.lock b/Cargo.lock index d60f2b0..ad90e19 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -231,11 +231,11 @@ dependencies = [ [[package]] name = "eggup-acquisition" -version = "0.2.0" +version = "0.2.1" [[package]] name = "eggup-archive" -version = "0.2.0" +version = "0.2.1" dependencies = [ "eggup-core", "flate2", @@ -247,7 +247,7 @@ dependencies = [ [[package]] name = "eggup-core" -version = "0.2.0" +version = "0.2.1" dependencies = [ "self-replace", "sha2", @@ -255,14 +255,14 @@ dependencies = [ [[package]] name = "eggup-curl" -version = "0.2.0" +version = "0.2.1" dependencies = [ "eggup-acquisition", ] [[package]] name = "eggup-eggfetch" -version = "0.2.0" +version = "0.2.1" dependencies = [ "eggfetch-core", "eggup-acquisition", @@ -273,7 +273,7 @@ dependencies = [ [[package]] name = "eggup-eggpack" -version = "0.2.0" +version = "0.2.1" dependencies = [ "eggpack-manifest", "eggup-acquisition", @@ -289,7 +289,7 @@ dependencies = [ [[package]] name = "eggup-service" -version = "0.2.0" +version = "0.2.1" dependencies = [ "eggup-core", "windows-args", @@ -298,7 +298,7 @@ dependencies = [ [[package]] name = "eggup-transport-footprint" -version = "0.2.0" +version = "0.2.1" dependencies = [ "eggup-acquisition", "eggup-curl", diff --git a/Cargo.toml b/Cargo.toml index 79d8235..7208e32 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -12,7 +12,7 @@ members = [ ] [workspace.package] -version = "0.2.0" +version = "0.2.1" edition = "2021" rust-version = "1.89" license = "MIT" diff --git a/architecture/acquisition.md b/architecture/acquisition.md index 9288ea8..44f4de9 100644 --- a/architecture/acquisition.md +++ b/architecture/acquisition.md @@ -46,11 +46,13 @@ Crates that depend on it: |---|---|---| | `eggup-eggfetch` | `0.2` (caret) + path | native HTTP adapter; implements `AcquisitionTransport` | | `eggup-curl` | `0.2` (caret) + path | external-process adapter; implements `AcquisitionTransport` | -| `eggup-eggpack` | `=0.2.0` exact pin + path | `use eggup_acquisition::{AcquisitionRequest, FetchLimits}` only (`eggup-eggpack/src/lib.rs:6`) — binds requests, never transports | +| `eggup-eggpack` | workspace source `=0.2.1` exact pin + path; published `0.2.0` retains `=0.2.0` | `use eggup_acquisition::{AcquisitionRequest, FetchLimits}` only (`eggup-eggpack/src/lib.rs:6`) — binds requests, never transports | | `eggup-transport-footprint` | `0.2` (caret) + path | `curl_only.rs` / `eggfetch_only.rs` use `AcquisitionRequest` + `FetchLimits`; `dual.rs` uses `ComposedTransport` + `CompositionPolicy` | The caret/exact-pin split is deliberate: adapters inherit a seam fix on the next -resolve, `eggup-eggpack` does not +resolve; the published `eggup-eggpack 0.2.0` exact pin does not. The workspace +source candidate has moved its local pin to `=0.2.1`, but that does not update +the immutable published package. ([acquisition-transport-roadmap.md](../plans/subsystems/acquisition-transport-roadmap.md#m010--eggup-acquisition-013-publication), M010). The `0.1.0` caret became `0.2` in the `0.2.0` publication train (Acquisition Transport M017): the seam's `0.2.0` is source-breaking @@ -589,8 +591,9 @@ caller set a `User-Agent`; that is the claim, and it is what M014 delivers. It is explicitly **not** placement parity: the two controls live in different types and are deliberately not aligned. `eggup-eggfetch`'s control lives in `EggfetchConfig`, whose `user_agent` is a public field of a public, -non-`#[non_exhaustive]` struct in a crate published at `0.2.0`; moving it -would be a source break for published consumers. `eggup-curl`'s control lives +non-`#[non_exhaustive]` struct in the `eggup-eggfetch 0.2.0` registry release; +moving it would be a source break for published consumers. `eggup-curl`'s +control lives on `CurlTransport` because `CurlConfig`'s fields are public and **not** `#[non_exhaustive]` (`curl/src/lib.rs:58-76`), so adding a field there would be source-breaking for every external struct-literal construction. Each diff --git a/architecture/eggfetch-adapter.md b/architecture/eggfetch-adapter.md index 41d64cf..78408bd 100644 --- a/architecture/eggfetch-adapter.md +++ b/architecture/eggfetch-adapter.md @@ -466,8 +466,8 @@ here as well as in [acquisition.md](acquisition.md) §11.1. makes. The finding is closed at the capability level. - **Parity is capability parity, not placement parity.** This adapter's control lives in `EggfetchConfig`, whose `user_agent` is a public field of a public, - non-`#[non_exhaustive]` struct in a crate published at `0.2.0`; moving it - would be a source break for published consumers, so it stays where it is. + non-`#[non_exhaustive]` struct in the `eggup-eggfetch 0.2.0` registry release; + moving it would be a source break for published consumers, so it stays where it is. The curl adapter's control lives on `CurlTransport` because `CurlConfig`'s fields are public and **not** `#[non_exhaustive]`, so adding a field there would be source-breaking for every external struct-literal construction. diff --git a/architecture/eggpack-adapter.md b/architecture/eggpack-adapter.md index 84acae2..acba409 100644 --- a/architecture/eggpack-adapter.md +++ b/architecture/eggpack-adapter.md @@ -70,15 +70,15 @@ Runtime dependencies ([`Cargo.toml`](../crates/eggup-eggpack/Cargo.toml)): | Dependency | Constraint | Source | |---|---|---| -| `eggup-core` | `=0.2.0` | local path `../eggup-core` | -| `eggup-archive` | `=0.2.0` | local path `../eggup-archive` | -| `eggup-acquisition` | `=0.2.0` | local path `../eggup-acquisition` | +| `eggup-core` | `=0.2.1` | local path `../eggup-core` | +| `eggup-archive` | `=0.2.1` | local path `../eggup-archive` | +| `eggup-acquisition` | `=0.2.1` | local path `../eggup-acquisition` | | `eggpack-manifest` | `=0.1.1` | crates.io registry | -The three Eggup edges are exact-pinned so the published crate cannot silently -resolve a different published seam; the producer edge is registry-only so the -published crate has no VCS source requirement. Both facts are asserted as -tests, not just comments — see +The workspace-source candidate pins its three Eggup edges to `=0.2.1`; the +published `eggup-eggpack 0.2.0` artifact remains unchanged and pins `=0.2.0`. +The producer edge is registry-only so the published crate has no VCS source +requirement. Both facts are asserted as tests, not just comments — see [Testing approach](#testing-approach). The adapter has **no direct `sha2` runtime dependency**. The archive digest is @@ -255,9 +255,10 @@ as the enforcement point: ([`tests/interoperability.rs:972`](../crates/eggup-eggpack/tests/interoperability.rs)) asserts the manifest contains `eggpack-manifest = "=0.1.1"` and that it contains no `git =`, `rev =`, `branch =`, or `tag =` edge; asserts all three - Eggup edges stay `=0.2.0` — derived from the adapter's own - `env!("CARGO_PKG_VERSION")` rather than a hardcoded literal, so the invariant - is "pinned to *our* version" and survives the next workspace bump; and asserts + Eggup edges match the adapter's own `env!("CARGO_PKG_VERSION")` rather than a + hardcoded literal, so the invariant is "pinned to *our* version" and survives + future workspace bumps (currently `=0.2.1` in this unpublished source + candidate); and asserts `eggpack-core`, `eggpack-contract`, and `eggpack-bootstrap` appear nowhere. - `adapter_source_claims_no_producer_or_service_authority` ([`tests/interoperability.rs:1023`](../crates/eggup-eggpack/tests/interoperability.rs)) diff --git a/architecture/overview.md b/architecture/overview.md index 0f5f91f..d9b7b42 100644 --- a/architecture/overview.md +++ b/architecture/overview.md @@ -43,9 +43,12 @@ manager, and producer concerns. ## Dependency graph Derived from the `crates/*/Cargo.toml` manifests. Arrows point from dependent to -dependency (compile-time direction). All 8 crates carry the workspace version -`0.2.0`; all seven library crates are published at `0.2.0` on crates.io. -The 0.2.0 line is one lockstep train published from a single source commit, +dependency (compile-time direction). All 8 crates carry workspace version +`0.2.1`. + +The seven published library crates still have latest registry version `0.2.0`; +this branch prepares Core M016 only, and no `0.2.1` package is published. The +`0.2.0` line is one lockstep train published from a single source commit, because `eggup-acquisition`'s next release is source-breaking and the workspace shares one version; per-crate checksums, package dependency graphs, and the registry-only fixture results are recorded in the five publication @@ -76,7 +79,7 @@ In plain dependency order, deepest first: 4. **`eggup-curl`** → `eggup-acquisition` only. External-process adapter, no HTTP/TLS stack. 5. **`eggup-service`** → `eggup-core` + `windows-args` (+ `windows-service` on Windows). Lifecycle adapters. 6. **`eggup-archive`** → `tar`, `zip`, `flate2`, `fs_at`, `sha2` (dev-dep `eggup-core`). Bounded local extraction. -7. **`eggup-eggpack`** → `eggup-core` + `eggup-archive` + `eggup-acquisition` (`=0.2.0`) + `eggpack-manifest =0.1.1`. Leaf producer adapter. +7. **`eggup-eggpack`** → `eggup-core` + `eggup-archive` + `eggup-acquisition` (`=0.2.1` in the workspace source candidate) + `eggpack-manifest =0.1.1`. Leaf producer adapter. 8. **`eggup-transport-footprint`** → `eggup-acquisition` + optional `eggup-curl` / `eggup-eggfetch`. **Non-published** footprint fixtures. Two consequences worth knowing before reviewing anything: @@ -100,21 +103,20 @@ binary-only with no `lib.rs`, so it relies on the workspace lint table for `unsafe_code` and has no `missing_docs` enforcement ([tooling-governance.md](tooling-governance.md) §3.4). -*Figures are a snapshot of the working tree at the time this table was -corrected. `eggup-core` and `eggup-curl` were being edited concurrently at -that moment, so their line counts need re-derivation once those edits land.* +LOC figures reflect the current checked-in Rust source; test counts are the +number of `#[test]` functions under each crate's `src/` and `tests/` trees. | Module (crate) | Role | LOC / tests | Key capabilities | Deep dive | |---|---|---|---|---| -| `eggup-core` | Policy-neutral local mechanics | 7181 / 110 | `InstallPlan` → `Prepared` → `Verified` → `Validated` → `Receipt`; SHA-256 integrity, bounded candidate execution, caller-proven `Absent \| Owned \| Foreign \| Unknown`, `MutationLock` + opt-in `StaleLockVerifier` recovery, locked ownership + staged-digest revalidation, commit/rollback, `commit_with_post_commit`, `InstallPlan::for_current_executable` self-update | [core-transaction.md](core-transaction.md) | -| `eggup-acquisition` | Transport-neutral seam, fixtures, composition | 2229 / 50 | `AcquisitionRequest`, `FetchLimits` + `effective()` = `min(request, adapter)`, `CancelFlag`, `Success \| NotFound` vs hard failure (`InvalidInput`/`Transport`/`Timeout`/`TooLarge`/`Cancelled`/`Io`/`Unavailable`), `AcquisitionTransport`, `FixtureTransport`, `ComposedTransport` + `CompositionPolicy`, exclusive 0600 temp + no-clobber promotion, URL redaction | [acquisition.md](acquisition.md) | -| `eggup-eggfetch` | Native HTTP adapter | 1229 / 31 | `EggfetchConfig::strict()` single policy point (timeout ceilings, redirect bound, explicit `ProxyDecision`, HTTP/1 + Rustls), status classification, streaming artifacts, sync-over-async bridge, category-only redacted errors | [eggfetch-adapter.md](eggfetch-adapter.md) | -| `eggup-curl` | External curl adapter | 2532 / 38 | `CurlConfig::strict()` single policy point (explicit executable, opt-in PATH discovery, connect/total ceilings, redirect/protocol/proxy explicit, `--disable` against curlrc), direct-process execution with kill/reap, same-request HTTP status capture, private temp + no-clobber promotion | [curl-adapter.md](curl-adapter.md) | -| `eggup-service` | Manager-neutral lifecycle | 11700 / 174 | `ServiceSpec` / `Ownership` / `LifecycleSnapshot`, `ServiceManager` + `TestDoubleManager`, `SystemExecutor` (allowlisted paths, cleared env, bounded I/O), `atomic_write_definition`, systemd / launchd / cron / Windows SCM adapters, `commit_with_lifecycle`, `UpdateRuntimeDisposition` + `plan_unix`/`plan_windows` + `DirectRuntimeControl` + `commit_with_disposition` | [service-lifecycle.md](service-lifecycle.md) | +| `eggup-core` | Policy-neutral local mechanics | 7180 / 110 | `InstallPlan` → `Prepared` → `Verified` → `Validated` → `Receipt`; SHA-256 integrity, bounded candidate execution, caller-proven `Absent \| Owned \| Foreign \| Unknown`, `MutationLock` + opt-in `StaleLockVerifier` recovery, locked ownership + staged-digest revalidation, commit/rollback, `commit_with_post_commit`, `InstallPlan::for_current_executable` self-update | [core-transaction.md](core-transaction.md) | +| `eggup-acquisition` | Transport-neutral seam, fixtures, composition | 2229 / 49 | `AcquisitionRequest`, `FetchLimits` + `effective()` = `min(request, adapter)`, `CancelFlag`, `Success \| NotFound` vs hard failure (`InvalidInput`/`Transport`/`Timeout`/`TooLarge`/`Cancelled`/`Io`/`Unavailable`), `AcquisitionTransport`, `FixtureTransport`, `ComposedTransport` + `CompositionPolicy`, exclusive 0600 temp + no-clobber promotion, URL redaction | [acquisition.md](acquisition.md) | +| `eggup-eggfetch` | Native HTTP adapter | 1229 / 30 | `EggfetchConfig::strict()` single policy point (timeout ceilings, redirect bound, explicit `ProxyDecision`, HTTP/1 + Rustls), status classification, streaming artifacts, sync-over-async bridge, category-only redacted errors | [eggfetch-adapter.md](eggfetch-adapter.md) | +| `eggup-curl` | External curl adapter | 2634 / 38 | `CurlConfig::strict()` single policy point (explicit executable, opt-in PATH discovery, connect/total ceilings, redirect/protocol/proxy explicit, `--disable` against curlrc), direct-process execution with kill/reap, same-request HTTP status capture, private temp + no-clobber promotion | [curl-adapter.md](curl-adapter.md) | +| `eggup-service` | Manager-neutral lifecycle | 11706 / 182 | `ServiceSpec` / `Ownership` / `LifecycleSnapshot`, `ServiceManager` + `TestDoubleManager`, `SystemExecutor` (allowlisted paths, cleared env, bounded I/O), `atomic_write_definition`, systemd / launchd / cron / Windows SCM adapters, `commit_with_lifecycle`, `UpdateRuntimeDisposition` + `plan_unix`/`plan_windows` + `DirectRuntimeControl` + `commit_with_disposition` | [service-lifecycle.md](service-lifecycle.md) | | `eggup-archive` | Bounded local archive extraction | 3717 / 59 | Explicit tar.gz/zip member allowlists, finite compressed/decompressed budgets, regular-file-only extraction, private root, no-clobber files, streamed SHA-256/size evidence, `ExtractedArchive` → `PersistedExtraction` → `BoundExtraction` handoff, internal `DirectoryGuard` cleanup | [archive-extraction.md](archive-extraction.md) | | `eggup-eggpack` | Optional Eggpack ReleaseManifest v1 adapter (leaf) | 855 / 71 | `project` / `project_json`, `bind_requests` (tightened byte caps), `default_destinations`, `materialize_artifact_set[_with_destinations]`, direct/bundle installable vs archive extraction-required, `core_plan_for_archive*`, `bind_archive_members`, `install_ids` | [eggpack-adapter.md](eggpack-adapter.md) | | `eggup-transport-footprint` | Non-published footprint fixtures | 45 / 2 | Three `required-features` binaries — `curl_only`, `eggfetch_only`, `dual` — that pin which transport stacks a consumer links; measures the cost of the transport choice | [transport-footprint.md](transport-footprint.md) | -| tooling + governance | Workspace, verification, planning | — | `scripts/check-local.sh` (fmt/clippy/test/doc/tree), CI (stable, MSRV 1.89, macOS, Windows), workspace lints, `plans/` ADRs + subsystem roadmaps + closure records + registry, and the agent-facing surface (`AGENTS.md` + `.opencode/skills/`) | [tooling-governance.md](tooling-governance.md) | +| tooling + governance | Workspace, verification, planning | — | `scripts/check-local.sh` (fmt/clippy/test/doc/tree + docs truth), CI (stable, MSRV 1.89, Linux systemd, macOS, Windows), workspace lints, `plans/` ADRs + subsystem roadmaps + closure records + registry, and the agent-facing surface (`AGENTS.md` + `.opencode/skills/`) | [tooling-governance.md](tooling-governance.md) | ### Source layout inside the larger crates @@ -259,12 +261,12 @@ Contract-level detail that belongs to no single crate: - [ADRs](../plans/adrs/README.md) — accepted decisions, superseded not rewritten - [closure records](../plans/closure/README.md) — requirement → evidence matrices -Publication state: `eggup-core`, `eggup-archive`, `eggup-acquisition`, -`eggup-curl`, `eggup-eggfetch`, `eggup-eggpack`, and `eggup-service` are -published at `0.2.0`. The 0.2.0 line is one lockstep train from a single -source commit; checksums and registry-only qualification are in the five -publication closure records under `plans/closure/`. The `v0.1.1`, `v0.1.2`, -and `v0.1.3` tags were not moved. +Registry snapshot: the latest published version for each of the seven library +crates (`eggup-core`, `eggup-archive`, `eggup-acquisition`, `eggup-curl`, +`eggup-eggfetch`, `eggup-eggpack`, and `eggup-service`) remains `0.2.0`. The +`0.2.0` line is one lockstep train from a single source commit; checksums and +registry-only qualification are in the five publication closure records under +`plans/closure/`. The `v0.1.1`, `v0.1.2`, and `v0.1.3` tags were not moved. `eggup-transport-footprint` is `publish = false` by design and has no registry version. CI never publishes; releases are manual — see [tooling-governance.md](tooling-governance.md) §8. diff --git a/architecture/service-lifecycle.md b/architecture/service-lifecycle.md index 3c05755..1f361a7 100644 --- a/architecture/service-lifecycle.md +++ b/architecture/service-lifecycle.md @@ -62,7 +62,7 @@ absolute paths. ## Position in the workspace ```text -eggup-core (sha2 only) +eggup-core (sha2; self-replace on Windows) ^ | eggup-service -> windows-args (=0.2.0) @@ -75,18 +75,18 @@ eggup-service -> windows-args (=0.2.0) **Windows-target dependency**, so the Linux/macOS build never links it. - `windows-args` is cross-platform and is used for the SCM command-line parser, so the ownership tests in `windows_scm.rs` run on every host. -- **The crate is current with the workspace.** It is on crates.io at - `0.1.0`, `0.1.1`, `0.1.2`, `0.1.3`, and `0.2.0`; the `0.1.2` service publication came - from `7fb84bc`, after the shared `v0.1.2` tag, which remains the core/archive - source tag. Service M011 published the `0.1.3` owned failed-systemd - quiescence correction from source `feb6ae5`; its exact checksum and registry - qualification are in the M011 closure. Service M017 published `0.2.0` from - the train's shared source commit `b612608` — the first publication that - carries the stdin-verdict fix the published `0.1.3` lacks; its checksum and - registry qualification are in the M017 closure record. - `eggup-core`, `eggup-archive`, `eggup-acquisition`, `eggup-eggfetch`, - `eggup-eggpack`, and `eggup-curl` are also published at `0.2.0`. - `eggup-transport-footprint` is `publish = false` +- **The crate's registry history.** `eggup-service` is available on crates.io at + `0.1.0`, `0.1.1`, `0.1.2`, `0.1.3`, and `0.2.0`. The `0.1.2` service + publication came from `7fb84bc`, after the shared `v0.1.2` tag, which remains + the core/archive source tag. Service M011 published the `0.1.3` owned + failed-systemd quiescence correction from source `feb6ae5`; its exact checksum + and registry qualification are in the M011 closure. Service M017 published + `0.2.0` from the train's shared source commit `b612608` — the first publication + that carries the stdin-verdict fix the published `0.1.3` lacks; its checksum + and registry qualification are in the M017 closure record. + + The latest registry version for each of the other six published library crates + remains `0.2.0`; `eggup-transport-footprint` is `publish = false` ([registry.md](../plans/registry.md)). - Dependency order position: 5th deepest in [overview.md's dependency graph](overview.md#dependency-graph). It is a leaf diff --git a/architecture/tooling-governance.md b/architecture/tooling-governance.md index b378013..08ff5b9 100644 --- a/architecture/tooling-governance.md +++ b/architecture/tooling-governance.md @@ -55,7 +55,7 @@ dependency of one crate silently activate in another. `[workspace.package]` (`Cargo.toml:14-19`) declares exactly five keys: ```toml -version = "0.2.0" +version = "0.2.1" edition = "2021" rust-version = "1.89" license = "MIT" @@ -95,7 +95,7 @@ review-critical. | Crate | Dependencies | Boundary rule | |---|---|---| -| `eggup-core` | `sha2 = "0.10"` | Sole dep. No transport, no service manager, no Eggpack | +| `eggup-core` | `sha2 = "0.10"`; Windows-only `self-replace = "1.5"` | Non-Windows graph remains `sha2` only; no transport, service manager, or Eggpack | | `eggup-acquisition` | *(none)* | Zero-dependency seam | | `eggup-eggfetch` | `eggup-acquisition`, `eggfetch-core`, `tokio`, `futures-util` | Must not know `eggup-curl` exists | | `eggup-curl` | `eggup-acquisition` | Must not know `eggup-eggfetch` exists; no embedded HTTP/TLS stack | @@ -114,16 +114,18 @@ silently break them: (`crates/eggup-archive/Cargo.toml`). Core does not depend on archive; the arrow is one-way, and the test fixtures are what need the transaction types. -**Exact-pin asymmetry.** `eggup-eggpack` pins its in-workspace deps with exact -requirements (`=0.2.0`) and takes `eggpack-manifest` as `=0.1.1` from the -registry. Every other crate uses a caret requirement — and every one of them -now carries the literal `"0.2"`, which matches the workspace version -`0.2.0` (`eggup-eggfetch` → `eggup-acquisition`, `eggup-curl` → -`eggup-acquisition`, `eggup-service` → `eggup-core`, and all three in -`eggup-transport-footprint`). These resolve correctly through the path -dependencies, so the build is not broken. The pin style still differs by crate -for no stated reason, which means a version bump has to be reasoned about -per-crate rather than applied uniformly. +**Exact-pin asymmetry.** In the current workspace source candidate, +`eggup-eggpack` pins its in-workspace deps with exact requirements +(`=0.2.1`) and takes `eggpack-manifest` as `=0.1.1` from the registry. The +immutable published `eggup-eggpack 0.2.0` still pins those Eggup edges at +`=0.2.0`. Every other current workspace crate uses a caret requirement, +`"0.2"`, which resolves against the local path packages at source version +`0.2.1` (`eggup-eggfetch`/`eggup-curl` → `eggup-acquisition`, +`eggup-service` → `eggup-core`, and the footprint fixtures). This local +alignment does not make the other six crates `0.2.1` registry releases; only +Core is in M016's publication scope. The distinct exact-pin behavior is +intentional for the adapter; +review downstream version coupling per release plan. **The `0.2.0` widening was load-bearing, not cosmetic.** The seam's `0.2.0` is source-breaking (`AcquisitionError::Io(String)` became @@ -249,7 +251,7 @@ and with `plans/registry.md`: | Assertion | What it checks | |---|---| | 1 | No checked surface (`docs/`, `README.md`, `AGENTS.md`, `architecture/*.md`) states a version literal outside the known set — the registry history unioned with the version the manifests declare. A literal the same clause explicitly disclaims ("not a `0.1.4`") is not a claim | -| 2 | No checked surface states the current version as a version other than the one the manifests declare — a "workspace version" paragraph must not name another version, "published at `X`" must name the current version (except in `docs/crates.md`, which records each crate's published history), and an exact pin `=X` may survive only where it states the eggpack exact-pin policy. The clause is anchored to the manifest version, so the next train needs no edit of it | +| 2 | Workspace-source version claims must match the manifest. Published-version claims are validated per crate against that crate's released changelog headings and `publish` flag, so a single-crate release preparation may legitimately have source `0.2.1` while the registry still has `0.2.0`. Exact pins are allowed where they describe the Eggpack pin policy | | 3 | No `docs/` file and no `architecture/*.md` deep dive states a normative rule without linking the contract that owns it. The owning deep dive is exempt: it is the owner, not a leak | | 4 | The root `CHANGELOG.md` `Unreleased` section does not contradict the published section. The published set is derived from the crate changelogs' version headings rather than a literal, so the clause keeps policing the next train without another edit | | 5 | No milestone carries two statuses in `plans/registry.md` — three-cell tables included, not only the four-cell ones — and the registry names its authoritative table | @@ -448,17 +450,18 @@ Entry point `plans/README.md`. Normative process document: |---|---|---| | Canonical long-term documents | 4 | `plans/000`–`003` | | Accepted ADRs | 5 | `plans/adrs/ADR-0001`…`0005` | -| Subsystem roadmaps | 7 | `plans/subsystems/*-roadmap.md` | -| Implementation plans | 62 | `plans/implementation//NNN-*.md` | -| Closure records | 61 | `plans/closure//NNN-status.md` | -| Closure directories | 8 | 7 subsystems plus `planning-closure-hygiene-corrective` | +| Subsystem roadmaps | 8 | `plans/subsystems/*-roadmap.md` | +| Implementation plans | 101 | `plans/implementation//NNN-*.md` (README excluded) | +| Closure records | 99 | `plans/closure//NNN-status.md` | +| Closure directories | 9 | 8 subsystems plus `planning-closure-hygiene-corrective` | The subsystem set is: `verified-update-core`, `acquisition-transport`, `archive-extraction`, `service-lifecycle`, `distribution-bootstrap`, -`consumer-adoption`, `eggpack-manifest-interoperability`. The eighth closure -directory, `planning-closure-hygiene-corrective`, is a docs-only workstream that -holds plans `001`–`012` and has no subsystem roadmap — it exists to reconcile -the registry and closure records against reality. +`consumer-adoption`, `eggpack-manifest-interoperability`, and +`transport-footprint`. The ninth closure directory, +`planning-closure-hygiene-corrective`, is a docs-only workstream that holds +plans `001`–`015` and has no subsystem roadmap — it exists to reconcile the +registry and closure records against reality. ### 6.2 Normative documents and their mutability @@ -655,24 +658,26 @@ Releases are manual, and this is recorded as a deliberate design decision in the registry: the M009 core/archive publication row states "manual only, no release CI added." -| Crate | Workspace version | On crates.io | Note | -|---|---|---|---| -| `eggup-core` | 0.2.0 | 0.1.0, 0.1.1, 0.1.2, 0.1.3, **0.2.0** | Sole dep `sha2`; transaction mechanics | -| `eggup-archive` | 0.2.0 | 0.1.2, 0.1.3, **0.2.0** | Bounded extraction | -| `eggup-acquisition` | 0.2.0 | 0.1.0, 0.1.1, 0.1.2, 0.1.3, **0.2.0** | Zero-dependency seam | -| `eggup-eggfetch` | 0.2.0 | 0.1.0, 0.1.1, 0.1.2, 0.1.3, **0.2.0** | Native HTTP adapter | -| `eggup-curl` | 0.2.0 | 0.1.2, **0.2.0** | External-curl adapter | -| `eggup-eggpack` | 0.2.0 | 0.1.2, 0.1.3, **0.2.0** | Only crate touching producer types; pins `=0.2.0` | -| `eggup-service` | 0.2.0 | 0.1.0, 0.1.1, 0.1.2, 0.1.3, **0.2.0** | Carries the stdin-verdict fix the published `0.1.3` lacks | -| `eggup-transport-footprint` | 0.2.0 | none (`publish = false`) | Binary-only fixture crate, non-publishable by design | - -All 8 crates share workspace version `0.2.0`; all seven library crates are on -crates.io at `0.2.0`. The 0.2.0 line is one lockstep train, published in -dependency order — the seam, then the adapters, then the leaf — because a -crate is published only after every in-workspace dependency it names is on the -registry. `eggup-curl` skipped `0.1.3` entirely: its next release after -`0.1.2` is `0.2.0`, because the seam's source break forced the whole -version-lockstep workspace forward. +| Crate | Workspace source version | Latest published | Published versions | Note | +|---|---|---|---|---| +| `eggup-core` | 0.2.1 | 0.2.0 | 0.1.0, 0.1.1, 0.1.2, 0.1.3, **0.2.0** | Non-Windows runtime graph is `sha2`; Windows also uses `self-replace`; M016 prepares contract-doc packaging | +| `eggup-archive` | 0.2.1 | 0.2.0 | 0.1.2, 0.1.3, **0.2.0** | Bounded extraction; current dependency refresh remains unpublished | +| `eggup-acquisition` | 0.2.1 | 0.2.0 | 0.1.0, 0.1.1, 0.1.2, 0.1.3, **0.2.0** | Zero-dependency seam | +| `eggup-eggfetch` | 0.2.1 | 0.2.0 | 0.1.0, 0.1.1, 0.1.2, 0.1.3, **0.2.0** | Native HTTP adapter | +| `eggup-curl` | 0.2.1 | 0.2.0 | 0.1.2, **0.2.0** | External-curl adapter | +| `eggup-eggpack` | 0.2.1 | 0.2.0 | 0.1.2, 0.1.3, **0.2.0** | Only crate touching producer types; source candidate pins `=0.2.1`; published `0.2.0` retains `=0.2.0` | +| `eggup-service` | 0.2.1 | 0.2.0 | 0.1.0, 0.1.1, 0.1.2, 0.1.3, **0.2.0** | Carries the stdin-verdict fix the published `0.1.3` lacks | +| `eggup-transport-footprint` | 0.2.1 | — | none (`publish = false`) | Binary-only fixture crate, non-publishable by design | + +All 8 crates share workspace source version `0.2.1`; crates.io still reports +`0.2.0` as the latest published version for all seven publishable crates. The +`0.2.1` source is an unpublished preparation candidate, not a registry release. +The `0.2.0` line is one historical lockstep train, published in dependency +order — the seam, then the adapters, then the leaf — because a crate is +published only after every in-workspace dependency it names is on the registry. +`eggup-curl` skipped `0.1.3` entirely: its next release after `0.1.2` is +`0.2.0`, because the seam's source break forced the whole version-lockstep +workspace forward. **The `0.1.x` line stays on crates.io.** No published version is withdrawn and no tag is moved; `v0.1.1`, `v0.1.2`, and `v0.1.3` remain where they are, @@ -702,11 +707,14 @@ Ordered by how expensive a miss is. `eggup-eggfetch` and `eggup-curl`? 4. **ADR-0004 classification** — is this work that belongs to Eggup, or producer work that belongs to Eggpack? `distribution-bootstrap` stays archived. -5. **Run `./scripts/check-local.sh`** and treat all 5 lines as gates, including - reading the `cargo tree` output rather than skimming past it (§4.2). +5. **Run `./scripts/check-local.sh`** and require every command to pass. The + script executes five Cargo commands plus the network-free documentation + check; `cargo tree` resolves the graph, but boundary compliance still needs + human review of its output (§4.2). 6. **Feature-gated change?** If the change lives behind a feature flag, check - which CI lane actually compiles it. Non-default features are built only by - `stable` and `macos` (§5.3) — not by `msrv`, not on Windows. + which CI lane actually compiles it. `stable` and `macos` build the three + footprint configurations; `msrv` checks all three at Rust 1.89; no Windows + lane builds them (§5.3). 7. **Platform-sensitive change?** Do not infer Windows or macOS behavior from a local Linux run. Confirm the relevant lane ran, and if the change is outside the curated Windows subset, treat Windows evidence as `not run` and say so. @@ -723,8 +731,9 @@ Ordered by how expensive a miss is. 11. **Registry updated** — status transitions, blockers, and next dependency transitions only; no plan detail duplicated. Roadmap status table reconciled. 12. **If publishing** — confirm it is a tracked publication milestone, that - `cargo package`/dry-run was qualified, that downstream exact pins - (`eggup-eggpack` → `=0.2.0`) are accounted for, and that CI still does not + `cargo package`/dry-run was qualified, that the downstream exact pins in the + current source and published adapter are accounted for (workspace `=0.2.1`; + published `eggup-eggpack 0.2.0` still uses `=0.2.0`), and that CI still does not publish. See the `release-workflow` skill. 13. **Did the prose move with the code?** If the change touched an enum, a variant, a CI lane, a dependency edge, a command, or a publication status, @@ -749,8 +758,9 @@ Ordered by how expensive a miss is. - [`../docs/`](../docs/README.md) — user-facing adoption guidance (quickstart, crate choice, releases). Non-normative; points at the contracts rather than restating them (§7.4). -- [core-transaction.md](core-transaction.md) — the crate whose sole `sha2` - dependency makes the boundary in §2.4 checkable. +- [core-transaction.md](core-transaction.md) — the crate whose non-Windows + dependency graph contains only `sha2` and whose Windows graph also includes + `self-replace`; the target-specific boundary is in §2.4. - [acquisition.md](acquisition.md) — the zero-dependency seam both adapters and the footprint fixtures depend on. - [eggfetch-adapter.md](eggfetch-adapter.md), [curl-adapter.md](curl-adapter.md) @@ -762,7 +772,8 @@ Ordered by how expensive a miss is. - [transport-footprint.md](transport-footprint.md) — the feature-gated binaries that `msrv` and `windows-check` do not build (§5.3). - [eggpack-adapter.md](eggpack-adapter.md) — the only crate allowed to depend - on `eggpack-manifest` and to pin `=0.2.0` exactly. + on `eggpack-manifest`; current workspace pins are `=0.2.1`, while the + published `0.2.0` artifact retains its `=0.2.0` pins. - [ADR-0005](../plans/adrs/ADR-0005-local-archive-extraction-safety-contract.md) — the archive safety contract; the ADR to read before touching `eggup-archive` boundaries. @@ -828,14 +839,11 @@ Corrected in the doc-hygiene pass recorded in the workspace history: | The same pass reconciled all seven roadmap **status tables** correctly but missed the milestone **bodies** and header `Status:` lines: acquisition M010 and core M012 read `Status: ready.`, archive M004 read `Status: blocked on Acquisition M010`, Eggpack M005 read `Status: blocked on Acquisition M010, Core M013, and Archive M004` | Each body entry reconciled to its closure record, and the acquisition/core headers — which still advertised M010/M011 and M012/M013 as open — rewritten. The asymmetry was real and within single files: M011 and M013 bodies were updated by the closing commit while M010 and M012 in the *same* files were missed. A drift class was added for reconciling a summary table while leaving its prose behind | | `consumer-adoption-roadmap.md` held Gregg M004 and EggPool M007 as `blocked` in both prose and status-table rows, gated on "Core M012 + M013; Acquisition M010" | All four gates closed 2026-10-06. Both rows now read `authorable`, with the published `eggup-core 0.1.3` / `eggup-acquisition 0.1.3` named as the satisfied evidence. They stay *intentionally unwritten* — no plan file exists, which is a separate fact from being blocked | -### Open — code-level, needs a milestone, not a doc edit +### Open — tracked residuals and ongoing corrections | Location | Drift | Why it is not fixed here | |---|---|---| -| `crates/eggup-transport-footprint/Cargo.toml:16,24,29` | **Closed 2026-10-24.** The pins were `"0.1.0"` for `eggup-acquisition`, `eggup-curl`, and `eggup-eggfetch` while `[workspace.package] version` was `0.1.3` | Resolved by the `0.2.0` publication train: all three are now `"0.2"`, matching the workspace `0.2.0`. The seam's `0.2.0` is source-breaking, so the caret had to widen or a consumer's lockfile could resolve a seam the adapters cannot compile against | -| `plans/implementation/**` | 14 of 62 plans ship fewer than 16 sections and 17 omit a `Repository baseline:` line; `Primary class:` is frequently outside the template enum (only 2 of 62 use a single template value verbatim) | Historical records. The template is `plans/implementation/README.md`; conforming old plans is not worth rewriting evidence. New plans should follow the template exactly | -| `crates/eggup-service/Cargo.toml:24` and the footprint manifest | **Closed 2026-10-24.** Both required peers at caret `0.1.0` while the workspace was at `0.1.3`, so they did **not** participate in the exact-pin cascade that §8 describes for `eggup-eggpack` | The service manifest now requires `eggup-core = "0.2"`. That widening was load-bearing, not cosmetic: leaving it at `^0.1.0` would let a consumer's lockfile resolve `eggup-core 0.1.3`, which lacks `stdin_data` and cannot compile `eggup-service 0.2.0`. The footprint manifest's three requirements moved to `"0.2"` for the same reason. The exact-pin style that §8 describes for `eggup-eggpack` is unchanged and still applies to it alone | -| `architecture/transport-footprint.md` §"Testing approach" and the CI matrix in §5 | **Closed 2026-10-24.** No CI job built the isolated single-adapter configurations (`--no-default-features --features curl`, `--features eggfetch`): every lane that built the bins built only the dual configuration, so the claim "links no Eggfetch code" was never verified by CI. The crate also had no `plans/subsystems/` roadmap | Both halves are now done. The `stable` lane builds all three isolated configurations (`ci.yml:26-28`), the `msrv` lane checks all three at the 1.89 floor (`ci.yml:52-54`), and the `macos` lane builds the `curl` and `eggfetch` configurations (`ci.yml:97-98`), so "links no Eggfetch code" is machine-checked on every lane that carries it. `plans/subsystems/transport-footprint-roadmap.md` exists and owns the crate. Registry finding 12 was closed by **Transport Footprint M001** (`plans/closure/transport-footprint/001-status.md`), and this row had simply not been reconciled to that closure | -| `crates/eggup-core/Cargo.toml:15-19` (`exclude = ["docs/", …]`) | `crates/eggup-core/docs/{domain,verification,transaction}.md` — the crate's authoritative contract docs — are excluded from the published package, so a consumer on crates.io or docs.rs never receives the contract it is bound to | Removing `"docs/"` from `exclude` is a manifest change with no consumer effect until `eggup-core` is republished — **and that republication has now happened**: the published `eggup-core 0.2.0` ships *with* the exclusion, so the consumer impact is live for the current published line, not hypothetical. Owned by **Verified Update Core M016 — `eggup-core` contract-doc packaging** (`plans/subsystems/verified-update-core-roadmap.md`): it must remove `"docs/"` from `exclude`, qualify `cargo package -p eggup-core --list`, and authorize the republication that delivers the docs. Recorded as open finding 14 and named as the follow-on of planning C013 at `plans/closure/planning-closure-hygiene-corrective/013-status.md` | +| `plans/implementation/**` | Some older plans predate or do not fully match the current 16-section template | Historical records. The template is `plans/implementation/README.md`; conforming old plans is not worth rewriting evidence. New plans should follow the template exactly | +| `crates/eggup-core/Cargo.toml` package selection | `crates/eggup-core/docs/{domain,verification,transaction}.md` are the authoritative contract docs. The active `0.2.1` source candidate no longer excludes `docs/`, but package-list and artifact proofs are still pending; the immutable published `eggup-core 0.2.0` package still lacks them | Owned by **Verified Update Core M016** (`plans/implementation/verified-update-core/016-eggup-core-contract-doc-packaging.md`). Finding 14 remains open until a published artifact and registry readback prove the documents are present. Explicit maintainer upload authorization is still required. | | `plans/closure/eggpack-manifest-interoperability/004a-status.md` | Still asserts `git log 39ff626..HEAD -- crates/` **is empty**; it now returns 4 commits | Deliberate. The record is an immutable 2026-10-01 snapshot, and rewriting it would edit historical evidence. The `registry.md` line that made the same claim *as a live status statement* is corrected; the closure record is not | | `plans/archive/` | Holds only its own `README.md`; no superseded material has ever been moved there, though `plans/README.md` describes it as retained-for-traceability | A policy directory with no content is not wrong. Pruning it would remove a documented mechanism; populating it is a separate authoring decision | diff --git a/architecture/transport-footprint.md b/architecture/transport-footprint.md index 82ccdc9..2a0b15b 100644 --- a/architecture/transport-footprint.md +++ b/architecture/transport-footprint.md @@ -52,13 +52,13 @@ separately exposed — the crate's *only* public feature surface is `curl`, | Crate | Manifest requirement | Resolved version | Note | |---|---|---|---| -| `eggup-acquisition` | `"0.2"` (path) | `0.2.0` | The seam, and the only unconditional dependency | -| `eggup-curl` | `"0.2"` (path, optional) | `0.2.0` | External-process adapter | -| `eggup-eggfetch` | `"0.2"` (path, optional) | `0.2.0` | Native in-process HTTP/TLS adapter | +| `eggup-acquisition` | `"0.2"` (path) | `0.2.1` | The seam, and the only unconditional dependency | +| `eggup-curl` | `"0.2"` (path, optional) | `0.2.1` | External-process adapter | +| `eggup-eggfetch` | `"0.2"` (path, optional) | `0.2.1` | Native in-process HTTP/TLS adapter | The requirement literals above are the ones in [`crates/eggup-transport-footprint/Cargo.toml`](../crates/eggup-transport-footprint/Cargo.toml); -the resolved versions are the current workspace version (`0.2.0`). The manifest +the resolved versions are the current workspace source version (`0.2.1`). The manifest is authoritative and is not changed by this document. It inherits the 5 shared workspace keys (`version`, `edition`, `rust-version`, @@ -97,10 +97,12 @@ until it lands in a consumer's dependency graph and binary size. These binaries are the fixture that makes the cost visible. Measured on this workspace at commit `ae9b47a` (macOS, `debug` profile, exact -commands in [Verification](#verification)). The workspace version has since -advanced to `0.2.0`; the counts below are the dated capture and are -not re-derived — the commands in [Verification](#verification) reproduce them at -the current baseline. +commands in [Verification](#verification)). The current workspace source +candidate is `0.2.1`; the counts and version labels below remain the dated +capture and are not re-derived. The commands in [Verification](#verification) +reproduce the build configurations at the current baseline, but may not produce +the same counts or binary sizes; the displayed dependency-tree labels describe +the captured `0.2.0` graph. | Configuration | Unique crates in the resolved tree | `curl_only` / `eggfetch_only` / `dual` binary size | |---|---|---| diff --git a/crates/eggup-archive/README.md b/crates/eggup-archive/README.md index f7b4365..495737f 100644 --- a/crates/eggup-archive/README.md +++ b/crates/eggup-archive/README.md @@ -74,8 +74,8 @@ the foreign replacement stays untouched. Member handles are single-owner and move-only: never clone a bound handle and assume an independent cursor. Supported order is stage, then close/consume handles, then handle-authorized cleanup. A failed bound stage copy never reopens the recorded path as -fallback. Egress M006 and Eggpack M002 stay blocked until M001d closes with -hosted qualification. +fallback. Egress M006 and Eggpack M002 are closed: M001d delivered the handle-backed +source handoff, with hosted qualification recorded in their closure records. This crate performs no network access, authenticity policy, external process invocation, live installation mutation, metadata restoration, or service diff --git a/crates/eggup-core/CHANGELOG.md b/crates/eggup-core/CHANGELOG.md index b006260..5892d3d 100644 --- a/crates/eggup-core/CHANGELOG.md +++ b/crates/eggup-core/CHANGELOG.md @@ -424,8 +424,15 @@ changelogs for changes that cross the boundary. ## Unreleased -Nothing in this section has been published. `0.2.0` is the published baseline on -crates.io, and no publication milestone authorizes these entries. +Nothing in this section has been published. `0.2.0` is the latest published +baseline on crates.io. M016 prepares package content for target version +`0.2.1`; no explicit upload authorization or publication is recorded. + +- **Package-content preparation (M016; target `0.2.1`, unpublished).** Include + the existing `docs/domain.md`, `docs/verification.md`, and `docs/transaction.md` + in the package. The Rust API, runtime behavior, and dependency graph do not + change, and no consumer migration is required. The immutable Core `0.2.0` + archive still lacks these files. ## 0.1.3 — 2026-10-06 diff --git a/crates/eggup-core/Cargo.toml b/crates/eggup-core/Cargo.toml index fd89658..0cafb33 100644 --- a/crates/eggup-core/Cargo.toml +++ b/crates/eggup-core/Cargo.toml @@ -13,7 +13,6 @@ authors = ["David Bowman"] keywords = ["update", "installer", "integrity", "rollback", "deployment"] categories = ["os", "filesystem"] exclude = [ - "docs/", "tests/", "benches/", ] diff --git a/crates/eggup-eggpack/CHANGELOG.md b/crates/eggup-eggpack/CHANGELOG.md index 9a85010..e835398 100644 --- a/crates/eggup-eggpack/CHANGELOG.md +++ b/crates/eggup-eggpack/CHANGELOG.md @@ -52,12 +52,16 @@ evidence only. ## Unreleased -Unpublished dependency maintenance only; package version remains `0.2.0`. -No publication or consumer migration is authorized by this milestone. +Unpublished dependency maintenance and workspace pin alignment only. The +latest published `eggup-eggpack` remains `0.2.0`; local source uses workspace +version `0.2.1`. No Eggpack publication or consumer migration is authorized. - Advance the exact registry pin for `eggpack-manifest` from `=0.1.0` to `=0.1.1`, and update the test ZIP dependency from `6.0` to `9.6.1`. The adapter API and projected behavior remain unchanged. +- Align the three local exact Eggup dependency pins to `=0.2.1` for the + workspace source version. The published `eggup-eggpack 0.2.0` package keeps + its original `=0.2.0` pins and is not republished by Core M016. ## 0.1.3 — 2026-10-06 diff --git a/crates/eggup-eggpack/Cargo.toml b/crates/eggup-eggpack/Cargo.toml index 54e3ec3..91f5ec4 100644 --- a/crates/eggup-eggpack/Cargo.toml +++ b/crates/eggup-eggpack/Cargo.toml @@ -17,9 +17,9 @@ categories = ["development-tools"] workspace = true [dependencies] -eggup-core = { version = "=0.2.0", path = "../eggup-core" } -eggup-archive = { version = "=0.2.0", path = "../eggup-archive" } -eggup-acquisition = { version = "=0.2.0", path = "../eggup-acquisition" } +eggup-core = { version = "=0.2.1", path = "../eggup-core" } +eggup-archive = { version = "=0.2.1", path = "../eggup-archive" } +eggup-acquisition = { version = "=0.2.1", path = "../eggup-acquisition" } eggpack-manifest = "=0.1.1" [dev-dependencies] diff --git a/docs/releases.md b/docs/releases.md index ea4c06a..d6bb7dc 100644 --- a/docs/releases.md +++ b/docs/releases.md @@ -1,9 +1,11 @@ # Versions and upgrades -This page is a snapshot checked against crates.io on 2026-11-14. The latest -published version is **0.2.0** for each of the seven library crates. Check -crates.io again when choosing a version, since registry state can change -independently of this repository. +This page was checked against crates.io on 2026-11-18. The latest published +version is **0.2.0** for each of the seven library crates. The workspace source +version is being prepared at `0.2.1`, but that candidate has not been published; +all seven registry packages remain at `0.2.0`. Check crates.io again when +choosing a version, since registry state can change independently of this +repository. | Crate | Latest published version | |---|---| @@ -22,11 +24,12 @@ remain available. Because Eggup is pre-1.0, a `0.1` requirement does not accept ## Exact-pin behavior The workspace crates generally use caret requirements for their Eggup -dependencies. `eggup-eggpack` pins its Eggup dependencies exactly to `0.2.0`, -so a later fix to `eggup-core`, -`eggup-archive`, or `eggup-acquisition` will not reach an already published -`eggup-eggpack` until that adapter is republished. Check the resolved dependency -graph if you depend on `eggup-eggpack`. +dependencies. The published `eggup-eggpack 0.2.0` pins its Eggup dependencies exactly to +`0.2.0`, so a later fix to `eggup-core`, `eggup-archive`, or +`eggup-acquisition` will not reach that published adapter until it is +republished. The local workspace pins are being aligned to `=0.2.1` for the +unpublished source candidate; this does not change the registry package. Check +the resolved dependency graph if you depend on `eggup-eggpack`. ## Earlier-version limitations diff --git a/plans/implementation/verified-update-core/016-eggup-core-contract-doc-packaging.md b/plans/implementation/verified-update-core/016-eggup-core-contract-doc-packaging.md index bd72dfb..ea91015 100644 --- a/plans/implementation/verified-update-core/016-eggup-core-contract-doc-packaging.md +++ b/plans/implementation/verified-update-core/016-eggup-core-contract-doc-packaging.md @@ -1,8 +1,8 @@ # Verified Update Core Milestone 016 — eggup-core contract-doc packaging -Status: ready for handoff +Status: active -Repository baseline: `a811b3634a48c4c045b467cee70d8d9ccc4144c4` +Repository baseline: `94f2545ea12fa88ab7fb5e135ba587d0fa6f584c` Source roadmap: - `plans/subsystems/verified-update-core-roadmap.md` @@ -45,27 +45,33 @@ that does not authorize their publication. - Core M019 and the workspace version-lockstep work are closed. The core has no in-workspace runtime dependency, so its package can be published on its own before any other crate at the new workspace version. -- At this plan's baseline, `cargo search eggup-core --limit 1` reports `0.2.0`. - The implementation must repeat the registry preflight. `0.2.1` is the - planned next patch only if that version remains unused. -- The milestone is ready for implementation handoff. A separate, recorded - maintainer authorization is still required before the irreversible - `cargo publish` step; authoring this plan does not grant that authorization. +- Point-in-time preflight on 2026-11-18: crates.io reports `eggup-core 0.2.0` + as latest and `0.2.1` unused; none of the listed Core versions is yanked. + GitHub has no `v0.2.1` tag or Release. Repeat these checks immediately before + any upload; the target remains provisional until then. +- Implementation is active in the `0.2.1` source candidate. A separate, + recorded maintainer authorization is still required before the irreversible + `cargo publish` step; this preparation does not grant that authorization. ## 3. Current implementation evidence -- `crates/eggup-core/Cargo.toml` declares - `exclude = ["docs/", "tests/", "benches/"]`. The exclusion is the direct - reason the contract documents are absent from the package. +- The active candidate's `crates/eggup-core/Cargo.toml` now excludes only + `tests/` and `benches/`; `docs/` is no longer excluded. A local + `cargo package --list --locked --allow-dirty` selected all three contract + files and no `tests/` or `benches/` paths. `cargo package`, strict service + package verification against registry Core `0.2.0`, and the Core publish + dry-run also passed locally; repeat these checks from the final clean commit + before any upload. No publication was attempted. - `crates/eggup-core/docs/` contains the three normative contract documents named in §1. They are already authoritative; this milestone does not edit their content. - `plans/closure/verified-update-core/019-status.md` records the published `eggup-core 0.2.0` package inventory and names M016 as the open follow-on. -- The root `[workspace.package].version` is `0.2.0`, inherited by every crate. - `crates/eggup-eggpack/Cargo.toml` exact-pins its three in-workspace - dependencies at `=0.2.0`; those local pins must stay aligned if the shared - source version advances. +- The root `[workspace.package].version` is now `0.2.1`, inherited by every + crate. `crates/eggup-eggpack/Cargo.toml` exact-pins its three in-workspace + dependencies at `=0.2.1` to match local path packages; published + `eggup-eggpack 0.2.0` remains immutable and keeps its `=0.2.0` pins. The + current workspace registry dependency remains `eggpack-manifest = "=0.1.1"`. - `eggup-core`'s runtime dependency surface is `sha2` plus the Windows-only `self-replace` dependency. Packaging documentation must not add a dependency or change either target's graph. @@ -97,6 +103,10 @@ that does not authorize their publication. - Advance `[workspace.package].version` from `0.2.0` to `0.2.1` and refresh `Cargo.lock` without unrelated dependency updates. +- Update `scripts/check-docs-truth.sh` so it validates workspace-source version + claims against the workspace manifest and published-version claims against the + subject crate's own changelog, allowing the documented source/registry split + before a single-crate publication. Keep the gate network-free. - Remove only `"docs/"` from `eggup-core`'s `exclude` list. Keep `tests/` and `benches/` excluded. - Retarget the three local exact `eggup-eggpack` path pins to `=0.2.1` so the @@ -135,13 +145,18 @@ that does not authorize their publication. retaining `"tests/"` and `"benches/"`. 3. In `crates/eggup-eggpack/Cargo.toml`, change the three local exact Eggup requirements from `=0.2.0` to `=0.2.1` so their path packages match the - shared workspace version. Keep `eggpack-manifest = "=0.1.0"` unchanged. - This is a source-workspace alignment only; the published `eggup-eggpack - 0.2.0` package is immutable and is not rebuilt or uploaded here. + shared workspace version. Keep the current `eggpack-manifest = "=0.1.1"` + registry pin unchanged. This is a source-workspace alignment only; the + published `eggup-eggpack 0.2.0` package is immutable and is not rebuilt or + uploaded here. 4. Refresh only the affected workspace package entries in `Cargo.lock`. Review the complete lockfile diff and stop if unrelated registry dependency versions change. -5. Do not change any file under `crates/eggup-core/src/**` or any file under +5. Revise `scripts/check-docs-truth.sh` only as needed to stop equating the + workspace source version with every crate's latest registry version; retain + per-crate changelog and manifest checks. Update its owning explanation in + `architecture/tooling-governance.md` and `.opencode/skills/verify-workflow`. +6. Do not change any file under `crates/eggup-core/src/**` or any file under `crates/eggup-core/docs/**`. ## 7. Ordered work packages @@ -160,15 +175,19 @@ that does not authorize their publication. appear, with tests and benches still absent. 4. **W4 — Release notes and current claims.** Add the Core M016 note to the core changelog and root changelog. Record the unpublished `eggup-eggpack` - local pin alignment in its `Unreleased` section without claiming that - `eggup-eggpack 0.2.0` has changed. Update current published/source-version - claims in `docs/crates.md`, `docs/releases.md`, `architecture/overview.md`, - `architecture/tooling-governance.md`, and `README.md` where applicable. - Keep dependency examples at `0.2.0` if they remain intentionally pinned and - working; do not edit compiled examples merely to make their version string - look newest. Remove the resolved M016 row from the live drift table only - after the `0.2.1` package is verified. Update the registry and Core roadmap - after qualification and closure, not before evidence exists. + local pin alignment in its `Unreleased` section without claiming that the + published `eggup-eggpack 0.2.0` changed. Until the registry upload occurs, + consumer-facing release docs must show all seven published crates at `0.2.0` + and explicitly identify workspace `0.2.1` as an unpublished source candidate. + Update `docs/crates.md`, `docs/releases.md`, `architecture/overview.md`, + `architecture/tooling-governance.md`, and `README.md` where applicable. Keep + the README/quickstart dependency example at `0.2.0` while that remains the + latest published package; do not alter compiled examples just to change the + version literal. Keep the Core M016 drift open until the published archive + proves the fix. Update the registry and Core roadmap to `active` during this + implementation; do not record closure or publication evidence before it exists. + Update `AGENTS.md` and the release/verification skills where current manifest + pins or gate semantics changed. 5. **W5 — Local qualification.** Run `./scripts/check-local.sh`, inspect `cargo tree --workspace --locked`, and review the lockfile and package manifest diffs. Require no runtime source or dependency-edge changes. @@ -250,8 +269,11 @@ crates.io upload, which is irreversible once accepted. ## 10. Required tests No production-code tests are added because the change does not alter Rust -source. The existing workspace gate remains required. The packaging behavior -is covered by artifact and consumer evidence: +source. The existing workspace gate remains required. The documentation-truth gate +must allow the workspace source version to differ from each crate's latest +published version, while checking each published-version claim against that +crate's changelog and manifest. The packaging behavior is covered by artifact +and consumer evidence: - The local package file list contains `docs/domain.md`, `docs/verification.md`, and `docs/transaction.md`, and no `tests/` or @@ -273,6 +295,7 @@ ordered local gate; inspect its `cargo tree` output as a human review step. ```sh ./scripts/check-local.sh +./scripts/check-docs-truth.sh cargo tree --workspace --locked cargo package -p eggup-core --list --locked cargo package -p eggup-core --locked @@ -322,26 +345,32 @@ package or registry command substitutes for a hosted platform lane. unchanged and M016 does not publish it. - Root `CHANGELOG.md`: aggregate the Core 0.2.1 package-content change without replacing the per-crate release notes. -- `docs/crates.md` and `docs/releases.md`: distinguish workspace source - version `0.2.1` from registry state (Core `0.2.1`; the other published - crates remain at `0.2.0` until their own releases). Explain that Core 0.2.0 - remains immutable and does not contain the three files. +- `docs/crates.md` and `docs/releases.md`: before publication, state that the + seven registry releases remain at `0.2.0` while the workspace source is a + `0.2.1` candidate. Do not claim Core `0.2.1` is published. Explain that the + immutable Core `0.2.0` package lacks the three files. After a later authorized + upload, update only Core's latest published version to `0.2.1`; other crates + remain at `0.2.0` unless separately released. - `architecture/overview.md` and `architecture/tooling-governance.md` §8: - update current workspace/published-version claims, add the Core 0.2.1 - publication, and preserve the historical 0.2.0 train record. Remove the - live Core M016 drift row only after the published archive proves the fix; - retain any necessary note that older immutable package versions lack the - files. + distinguish workspace-source version `0.2.1` from the seven crates still + published at `0.2.0`; preserve the historical 0.2.0 train record. Keep the + live Core M016 drift row open until the published archive proves the fix. +- `scripts/check-docs-truth.sh`: do not infer registry publication from the + workspace manifest version. Verify published-version claims per crate using + its changelog headings and `publish` setting; keep source-version claims + tied to the workspace manifest. Update the governance §4.1 description and + the verification skill to match. - `README.md`: update only any current workspace-version claim. Keep an intentionally pinned, compiling dependency example at `0.2.0` if it remains a valid example; do not silently change a snippet that must match a checked-in example. - `plans/registry.md` and - `plans/subsystems/verified-update-core-roadmap.md`: during this authoring - change, list M016 as ready for handoff with this plan. At closure, replace - that status with the closure evidence and record the publication result. -- `AGENTS.md` and `.opencode/skills/`: no change is required unless this work - changes a rule they index; M016 introduces no new rule. + `plans/subsystems/verified-update-core-roadmap.md`: mark M016 active while + implementation is underway. At closure, replace that status with closure + evidence and record only the actual publication result. +- `AGENTS.md` and `.opencode/skills/`: update indexed current facts when the + workspace exact pins and documentation-truth semantics change; do not add a + new policy rule there. ## 13. Acceptance criteria diff --git a/plans/registry.md b/plans/registry.md index 0d66919..9cb00be 100644 --- a/plans/registry.md +++ b/plans/registry.md @@ -558,7 +558,7 @@ against the registry. Finding 17 was registered by Acquisition M016. | Subsystem | Status | Next milestone | |---|---|---| -| Verified update core | M001-M015 and M017-M019 closed; M019 published `eggup-core 0.2.0` 2026-10-24 from `b612608`, hosted run `40079833945` green on all five lanes | M016 contract-doc packaging is ready for handoff; plan targets `eggup-core 0.2.1` after registry preflight | +| Verified update core | M001-M015 and M017-M019 closed; M019 published `eggup-core 0.2.0` 2026-10-24 from `b612608`, hosted run `40079833945` green on all five lanes | M016 contract-doc packaging is active in the `0.2.1` source candidate; the local gate and package checks pass; explicit maintainer upload authorization and registry readback remain required before any release | | Acquisition transport | M001-M018 closed; M012 conditionally closed; M017 published `eggup-acquisition`, `eggup-curl`, and `eggup-eggfetch` 0.2.0 (2026-10-24) from `b612608`, run `40079833945` green | M018 replaced the shell-backed curl fake after two Stable attempts in run `44024401775` failed with `ETXTBSY`; run `44155438351` is green on all five lanes. Finding 1 remains open because the Core shell fixture and general host-level spawn/resource failures remain outside M018 | | Transport footprint | M001 closed 2026-10-23 and hosted-qualified in run `40062299630`; the subsystem roadmap was created 2026-10-23, which was the prerequisite its first milestone required | no further transport-footprint milestone is registered | | Service lifecycle | M001–M017 closed; M012/M013/M014/M015 hosted-qualified; M017 published `eggup-service 0.2.0` 2026-10-24 from `b612608`, run `40079833945` green | no further service-lifecycle milestone is registered. The `SystemExecutor` consolidation that M012 deferred is closed by M015, and finding 16's strict packaged-service step was restored in `2d6e089` | @@ -576,7 +576,7 @@ milestone appears in exactly one table in this registry. | Subsystem | Milestone | Status | Plan | Dependencies | |---|---|---|---|---| -| Verified update core | M016 eggup-core contract-doc packaging | ready for handoff | `plans/implementation/verified-update-core/016-eggup-core-contract-doc-packaging.md` | Core M019 closed; target `0.2.1` subject to registry preflight; explicit maintainer upload authorization remains a publication gate | +| Verified update core | M016 eggup-core contract-doc packaging | active | `plans/implementation/verified-update-core/016-eggup-core-contract-doc-packaging.md` | Core M019 closed; local gate and package qualification passed for the `0.2.1` source candidate; explicit maintainer authorization and registry readback remain publication gates | | Verified update core | M020 staging privacy and credential redaction corrective | ready for handoff | `plans/implementation/verified-update-core/020-staging-privacy-and-credential-redaction-corrective.md` | Closes finding 18 (**low**): creation-mode privacy for the stage root, stage intermediates, backup root and both lock-record sites, plus manual `Debug` redaction in `eggup-acquisition`, `eggup-curl`, and `eggup-eggfetch`. No new dependency, no public API change, no version or publication change; three audit residuals accepted with reasons in plan §5 | | Verified update core | M019 eggup-core 0.2.0 publication | closed 2026-10-24 | `plans/implementation/verified-update-core/019-eggup-core-0.2.0-publication.md`; `plans/closure/verified-update-core/019-status.md` | published `eggup-core 0.2.0` (`2c86a0eb…eb23b8`) from `b612608`; hosted run `40079833945` green on all five lanes; the train-order exception in plan §9.1 is the only deviation; registry-only fixture green | | Archive extraction | M006 eggup-archive 0.2.0 publication | closed 2026-10-24 | `plans/implementation/archive-extraction/006-eggup-archive-0.2.0-publication.md`; `plans/closure/archive-extraction/006-status.md` | published `eggup-archive 0.2.0` (`ce35edd5…ff57ad`) from `b612608`; run `40079833945` green; registry-only fixture green; the packaged manifest carries no `eggup-core` edge | diff --git a/plans/subsystems/README.md b/plans/subsystems/README.md index 46a8438..a288390 100644 --- a/plans/subsystems/README.md +++ b/plans/subsystems/README.md @@ -36,5 +36,6 @@ Roadmaps MUST preserve completed history and MUST link active milestones to impl - `distribution-bootstrap-roadmap.md` (archived/transferred) - `consumer-adoption-roadmap.md` - `eggpack-manifest-interoperability-roadmap.md` +- `transport-footprint-roadmap.md` Do not create new subsystems merely to split files. Create one when ownership, dependencies, or closure criteria are meaningfully distinct. diff --git a/plans/subsystems/consumer-adoption-roadmap.md b/plans/subsystems/consumer-adoption-roadmap.md index cfba7d9..413e185 100644 --- a/plans/subsystems/consumer-adoption-roadmap.md +++ b/plans/subsystems/consumer-adoption-roadmap.md @@ -103,8 +103,7 @@ core M005 corrective + M006 qualification + transport M002 | v M004 Gregg - [BLOCKED on Core M012/M013 + Acquisition M010; - plan intentionally unwritten] + [AUTHORABLE; implementation plan intentionally unwritten] qualified core M006 + acquisition M004 | @@ -115,7 +114,7 @@ qualified core M006 + acquisition M004 M006 Egress was unblocked by Archive Extraction M001d closure (`plans/closure/archive-extraction/001d-status.md`, hosted run `36335233644`) and its adoption plan is registered at `plans/implementation/consumer-adoption/006-egress-archive-pair-adoption.md`. Verified Core M009 closed the publication gate on 2026-09-28 (`eggup-core 0.1.2` + `eggup-archive 0.1.2` registry-visible; `plans/closure/verified-update-core/009-status.md`), and Egress Delivery M003 landed the adoption on 2026-09-29 with hosted Linux/macOS/Windows updater evidence — M006 is closed (see `plans/closure/consumer-adoption/006-status.md` M003-landed addendum). No git/path dependency entered Egress's publishable release state. -M007 EggPool selective adoption remains evidence-driven. Core M010/M011 are closed; its standalone-Rust branch becomes authorable only after Core M012 preserves the 0.1.x boundary and M013 publishes the versioned Core. uv/pipx/pip provenance and package-manager rollback remain EggPool-owned. +M007 EggPool selective adoption is authorable: its versioned prerequisites are published (`eggup-acquisition 0.1.3` and `eggup-core 0.1.3`), and Core M012/M013 are closed. The adoption plan remains intentionally unwritten; uv/pipx/pip provenance and package-manager rollback remain EggPool-owned. ``` ## 7. Milestones diff --git a/plans/subsystems/verified-update-core-roadmap.md b/plans/subsystems/verified-update-core-roadmap.md index ec5e16c..20c7538 100644 --- a/plans/subsystems/verified-update-core-roadmap.md +++ b/plans/subsystems/verified-update-core-roadmap.md @@ -1,6 +1,6 @@ # Verified Update Core Roadmap -Status: active; M001-M015 and M017-M019 closed; M013 `eggup-core 0.1.3` published 2026-10-06 from `bd43683`; M014/M015/M017/M018 correctives hosted-qualified; M019 published `eggup-core 0.2.0` 2026-10-24 from `b612608` (hosted run `40079833945` green on all five lanes); M016 contract-doc packaging and M020 staging-privacy/credential-redaction corrective are ready for handoff +Status: active; M001-M015 and M017-M019 closed; M013 `eggup-core 0.1.3` published 2026-10-06 from `bd43683`; M014/M015/M017/M018 correctives hosted-qualified; M019 published `eggup-core 0.2.0` 2026-10-24 from `b612608` (hosted run `40079833945` green on all five lanes); M016 contract-doc packaging is active in the `0.2.1` source candidate; M020 staging-privacy/credential-redaction corrective remains ready for handoff Long-term references: @@ -503,5 +503,5 @@ publication/tag is reopened. | M017 | closed; hosted-qualified (run `40062299630`) | `plans/implementation/verified-update-core/017-bounded-stdin-execution-corrective.md` | `plans/closure/verified-update-core/017-status.md` | Supplies the bounded-stdin capability that Service M015 needs. `CommandSpec::stdin_data` attaches a payload and `MAX_STDIN_BYTES` (1 MiB, inclusive) bounds it; an oversize payload is rejected with `Error::InvalidInput` **before any child is spawned**; the payload is written on a dedicated thread and a write failure — including the broken pipe from a child that exits without reading — kills and reaps the child and returns a typed `Error::Io`. The deadline stays unconditional and bounds the writer exactly as it bounds the readers. The three `Error::Io` operation strings (`spawning bounded candidate`, `polling bounded candidate`, `writing bounded stdin`) are documented as a stable classification surface so a downstream adapter can re-classify a core failure. `Error` keeps exactly the seven published variants and no new dependency was added. Unpublished; `eggup-core` stays published at `0.1.3` **Published since:** the `0.2.0` train carries this fix — published 2026-10-24 from `b612608`; the published `0.1.x` line still carries the pre-fix state, and registry versions are immutable. | | M018 | closed; hosted-qualified (run `40079833945`) | `plans/implementation/verified-update-core/018-bounded-stdin-outcome-priority-corrective.md` | `plans/closure/verified-update-core/018-status.md` | The deadline has priority over the bounded stdin writer's verdict, and the verdict is classified by the instant the writer observed the write rather than by the runner's poll phase. A write failure observed before the deadline is an `Err`; one observed at or after it is the deadline outcome (`Ok`, `timed_out` set), so an undelivered payload is never reported as a success. The kill-and-pipe wording and the `FailureCategory` producer count were corrected, and the M015 closure record's U1 is closed on the evidence of commit `ab90688`. `Error` keeps exactly the seven published variants and no new dependency was added. Unpublished; `eggup-core` stays published at `0.1.3` **Published since:** the `0.2.0` train carries this fix — published 2026-10-24 from `b612608`; the published `0.1.x` line still carries the pre-fix state, and registry versions are immutable. | | M019 | closed; hosted-qualified (run `40079833945`) | `plans/implementation/verified-update-core/019-eggup-core-0.2.0-publication.md` | `plans/closure/verified-update-core/019-status.md` | Published `eggup-core 0.2.0` (`2c86a0eb…eb23b8`) from `b612608`, the publication source commit, with `v0.2.0` and release `0.2.0` created. The registry-only fixture resolves `eggup-core 0.2.0` from crates.io and exercises `MAX_STDIN_BYTES`, `CommandSpec::stdin_data`, the seven `Error` variants, and the absence of `FailureCategory::RetainedEvidence`. The version is `0.2.0` rather than `0.1.4` because the workspace is version-lockstep and the seam's next release is source-breaking. Plan §9.1 records the train-order exception: the packaged-service step resolves `eggup-core` against crates.io, so it could not be green before the first upload of the train; the four lanes were re-run on the same commit afterwards and passed unchanged | -| M016 | ready for handoff | `plans/implementation/verified-update-core/016-eggup-core-contract-doc-packaging.md` | — | Core M019's republication prerequisite is closed. The plan targets `eggup-core 0.2.1`, subject to registry preflight; explicit maintainer authorization remains required before upload | +| M016 | active | `plans/implementation/verified-update-core/016-eggup-core-contract-doc-packaging.md` | — | Local gate and package qualification passed for the `0.2.1` source candidate. Explicit maintainer authorization and registry readback remain required before upload and closure | | M020 | ready for handoff | `plans/implementation/verified-update-core/020-staging-privacy-and-credential-redaction-corrective.md` | — | Closes registry finding 18 (**low**) at baseline `2516d9e`: creation-mode privacy for the stage root, stage intermediates, backup root and both lock-record sites, plus manual `Debug` redaction in `eggup-acquisition`, `eggup-curl`, and `eggup-eggfetch`. No new dependency, no public API change, no publication. Three audit items are accepted residuals with reasons in plan §5; the acquisition boundary is named as an affected roadmap, not a second primary | diff --git a/scripts/check-docs-truth.sh b/scripts/check-docs-truth.sh index 47eb537..5147b48 100755 --- a/scripts/check-docs-truth.sh +++ b/scripts/check-docs-truth.sh @@ -7,7 +7,7 @@ # writes, never fetches, and never needs elevated privileges. # # Usage: -# ./scripts/check-docs-truth.sh # assertions 1-5 and 8 +# ./scripts/check-docs-truth.sh # assertions 1-5, 8, and 9 # ./scripts/check-docs-truth.sh --baseline # also assertion 7, scoped to # # Assertion 6 (the transport-footprint dependency counts) is a `cargo tree` @@ -250,19 +250,16 @@ for path in ALL_SURFACES: offset += len(line) + 1 # ---------------------------------------------------------------- assertion 2 -# The published-state claims in the checked surfaces must name the current -# workspace version. +# Workspace-source version claims are anchored to the workspace manifest. +# Published-version claims are checked per crate against its own released +# changelog headings in assertion 8b; a single-crate release preparation may +# legitimately make source and registry versions differ. # - a "workspace version" paragraph must not name any other version -# - "published at `X`" must name the current version, except in docs/crates.md, -# which is the one surface that records each crate's published history and -# may name an older version as a crate's first publication -# - "=X" (an exact pin) may survive only where it states the eggpack +# - "=X" exact pins may survive only where they state the eggpack # exact-pin policy # -# Re-based from the `0.1.2` literal when the `0.2.0` train landed, and made -# version-agnostic against WORKSPACE_VERSION so the next train needs no further -# edit of this clause. The shape of the rule is unchanged; only the version it -# is anchored to moved. +# The assertion is manifest-anchored, so future workspace version changes need +# no edit of this clause. CURRENT = WORKSPACE_VERSION if not CURRENT: @@ -279,22 +276,6 @@ for path in DOC_FILES + ["README.md", "AGENTS.md"]: fail("2", "%s: a 'workspace version' paragraph names %s, not the current %s" % (path, literal, CURRENT)) -published_hits = [] -for path in DOC_FILES: - for number, line in enumerate(lines(path), 1): - for match in re.finditer(r"published at `(0\.\d+\.\d+)`", line): - published_hits.append((path, number, line, match.group(1))) -for path, number, line, literal in published_hits: - if literal == CURRENT: - continue - if path != "docs/crates.md": - fail("2", "%s:%d: 'published at `%s`' names a version other than the current %s, " - "and only docs/crates.md may record an older published version" - % (path, number, literal, CURRENT)) - if literal not in KNOWN_VERSIONS: - fail("2", "%s:%d: 'published at `%s`' names a version outside the known set %s" - % (path, number, literal, sorted(KNOWN_VERSIONS))) - for path in DOC_FILES + ["README.md", "AGENTS.md", "architecture/overview.md", "architecture/tooling-governance.md"]: text = read(path)