Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
21 commits
Select commit Hold shift + click to select a range
ab90688
fix(corrective): close nine audit milestones across four subsystems
Oct 23, 2026
87cab50
fix(archive): make the M005 member-write guard line-ending portable
Oct 23, 2026
0cb2c53
fix(service,curl): make the hosted-run failures portable and attribut…
Oct 23, 2026
20ac770
docs(closure): record the hosted qualification of the corrective batch
Oct 23, 2026
5ae2301
feat(corrective): close five more audit milestones and repair doc anc…
dbowm91 Oct 24, 2026
b9885fa
fix(service,ci): make the M015 argv guard platform-neutral and defer …
dbowm91 Oct 24, 2026
bf439f5
docs(closure): record the hosted qualification of the second mileston…
dbowm91 Oct 24, 2026
640e97e
fix(audit): make the published contracts and the documentation truthful
Oct 24, 2026
3d91ab1
docs(plans): close the six corrective milestones and repair the registry
Oct 24, 2026
a431aaa
fix(service): re-anchor the public-API surface snapshot
Oct 24, 2026
896b564
docs(closure): record the hosted qualification of the audit-repair batch
Oct 24, 2026
d9428fe
docs(core): correct the M018 closure anchors and state the load requi…
Oct 24, 2026
b75f73b
docs(core): close the M018 hosted-qualification finding in the closur…
Oct 24, 2026
afe6201
plans: add the five 0.2.0 publication plans
Oct 24, 2026
2161f36
release: bump workspace to 0.2.0 and cut the 0.2.0 changelogs
Oct 24, 2026
b612608
plans(core): record the train-order exception for the first crate
Oct 24, 2026
2d6e089
ci: restore the strict packaged-service verification
Oct 24, 2026
fd60b4b
docs: close out the 0.2.0 publication train
Oct 24, 2026
390c224
docs(registry): move the 0.2.0 publication rows to the milestone-stat…
Oct 24, 2026
a811b36
docs(registry): record the ETXTBSY re-observation from the close-out run
Oct 24, 2026
14d39d3
plans(core): author M016 contract-doc packaging
Nov 12, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
62 changes: 62 additions & 0 deletions .github/workflows/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,23 @@ jobs:
- run: cargo fmt --all -- --check
- run: cargo clippy --workspace --all-targets --all-features --locked -- -D warnings
- run: cargo test --workspace --all-targets --all-features --locked
# The isolated single-adapter configurations are the crate's entire
# purpose. Without these steps, "curl_only links no Eggfetch code" is
# never checked by any machine. Each configuration is its own step so a
# failure names itself instead of hiding in a loop.
- run: cargo build -p eggup-transport-footprint --no-default-features --features curl --locked
- run: cargo build -p eggup-transport-footprint --no-default-features --features eggfetch --locked
- run: cargo build -p eggup-transport-footprint --no-default-features --features curl,eggfetch --locked
- run: cargo doc --workspace --no-deps --locked
# The packaged service crate is verified against the REGISTRY, strictly:
# the packaged sources are compiled, not merely packaged. The earlier
# deferral is DISCHARGED. It was needed because the service source line
# uses core's bounded-stdin capability (Core M017) and core's
# unconditional execution deadline (Core M014), neither of which was in
# the published `eggup-core 0.1.3`, so the packaged crate's
# `eggup-core = "^0.2"` requirement had nothing to resolve against.
# `eggup-core 0.2.0` is now on the registry, so the requirement resolves
# and the strict verification passes. See registry finding 16.
- run: cargo package -p eggup-service --locked

msrv:
Expand All @@ -29,6 +45,22 @@ jobs:
- uses: actions/checkout@v4
- uses: dtolnay/rust-toolchain@1.89.0
- run: cargo check --workspace --all-targets --locked
# `cargo check --workspace --all-targets --locked` enables no feature
# (default = []), so it compiled none of the three footprint binaries.
# The MSRV floor must apply to the feature-gated paths too, and the
# dual configuration is where two independent adapter graphs meet.
- run: cargo check -p eggup-transport-footprint --no-default-features --features curl --locked
- run: cargo check -p eggup-transport-footprint --no-default-features --features eggfetch --locked
- run: cargo check -p eggup-transport-footprint --no-default-features --features curl,eggfetch --locked
# The packaged service crate is verified against the REGISTRY, strictly:
# the packaged sources are compiled, not merely packaged. The earlier
# deferral is DISCHARGED. It was needed because the service source line
# uses core's bounded-stdin capability (Core M017) and core's
# unconditional execution deadline (Core M014), neither of which was in
# the published `eggup-core 0.1.3`, so the packaged crate's
# `eggup-core = "^0.2"` requirement had nothing to resolve against.
# `eggup-core 0.2.0` is now on the registry, so the requirement resolves
# and the strict verification passes. See registry finding 16.
- run: cargo package -p eggup-service --locked

service-systemd:
Expand Down Expand Up @@ -59,6 +91,20 @@ jobs:
with:
components: rustfmt, clippy
- run: cargo test --workspace --all-targets --all-features --locked
# macOS is the platform on which the published 3 / 92 / 93 counts were
# captured, so the isolated configurations are built here as well. The
# dual configuration is already built by the lane's --all-features step.
- run: cargo build -p eggup-transport-footprint --no-default-features --features curl --locked
- run: cargo build -p eggup-transport-footprint --no-default-features --features eggfetch --locked
# The packaged service crate is verified against the REGISTRY, strictly:
# the packaged sources are compiled, not merely packaged. The earlier
# deferral is DISCHARGED. It was needed because the service source line
# uses core's bounded-stdin capability (Core M017) and core's
# unconditional execution deadline (Core M014), neither of which was in
# the published `eggup-core 0.1.3`, so the packaged crate's
# `eggup-core = "^0.2"` requirement had nothing to resolve against.
# `eggup-core 0.2.0` is now on the registry, so the requirement resolves
# and the strict verification passes. See registry finding 16.
- run: cargo package -p eggup-service --locked

windows-check:
Expand All @@ -73,6 +119,13 @@ jobs:
- run: cargo test -p eggup-service --lib service_errors_output_and_permission_remediation_stay_utf8_bounded --locked
- run: cargo test -p eggup-service --lib lifecycle_failure_detail_is_utf8_safe_bounded_and_control_free --locked
- run: cargo test -p eggup-service --lib windows_scm::tests --locked
# The real Windows SCM fixture registers a disposable service through the
# crate's public API and drives it against the genuine Service Control
# Manager. It needs a hosted Windows runner with administrator rights,
# and it records a skip reason on stdout when those rights are absent --
# so it runs with --nocapture, and the reason is never swallowed by the
# test harness's output capture.
- run: cargo test -p eggup-service --test windows_scm_live --locked -- --nocapture
# Core self-update and stale-lock fixtures exercise real running-image and
# filesystem-race behaviour, so they run natively here rather than only
# being compiled.
Expand All @@ -81,4 +134,13 @@ jobs:
# --no-fail-fast: this lane is the only Windows test coverage, so a single
# failing target must not hide the state of every other one.
- run: cargo test --workspace --all-targets --locked --no-fail-fast
# The packaged service crate is verified against the REGISTRY, strictly:
# the packaged sources are compiled, not merely packaged. The earlier
# deferral is DISCHARGED. It was needed because the service source line
# uses core's bounded-stdin capability (Core M017) and core's
# unconditional execution deadline (Core M014), neither of which was in
# the published `eggup-core 0.1.3`, so the packaged crate's
# `eggup-core = "^0.2"` requirement had nothing to resolve against.
# `eggup-core 0.2.0` is now on the registry, so the requirement resolves
# and the strict verification passes. See registry finding 16.
- run: cargo package -p eggup-service --locked
28 changes: 16 additions & 12 deletions .opencode/skills/docs-hygiene/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,14 +56,17 @@ to stay correct.

Each has occurred at least once — check for them explicitly:

1. **CI lane understatement.** Windows runs nine `cargo test` steps
(`ci.yml:66-79`) plus packaged service verification. There is also a
privileged Linux `service-systemd` lane. Count commands, not bullets: three
named `eggup-service` diagnostic tests are three steps. The MSRV lane runs a
workspace check and packaged service verification; it does not run tests.
2. **Publication status.** `eggup-service 0.1.2` is published; the corrected
`0.1.3` service candidate is not yet published. Check crates.io rather than
inferring from a `publish = false` key or a plan.
1. **CI lane understatement.** Windows runs ten `cargo test` steps
(`ci.yml:116-136`) plus the packaged-service step, whose registry-resolved
compile is **strict** — the packaged sources are compiled against the
registry copy of `eggup-core 0.2.0`. There is also a privileged Linux
`service-systemd` lane. Count commands, not bullets: three named
`eggup-service` diagnostic tests are three steps. The MSRV lane runs a
workspace check and the packaged-service step; it does not run tests, and
that step's registry-resolved compile is strict too.
2. **Publication status.** All seven publishable crates are published at
`0.2.0` (2026-10-24); `eggup-transport-footprint` is not published at all.
Check crates.io rather than inferring from a `publish = false` key or a plan.
3. **Enum tables lagging the source.** `architecture/core-transaction.md` once
described a whole earlier generation of `eggup-core`'s enums. When a variant
is added, renamed, or removed, update every table that lists variants.
Expand All @@ -83,10 +86,11 @@ Each has occurred at least once — check for them explicitly:
8. **Broken markdown tables.** Copy-pasting a row between tables of different
arity silently drops cells. Check column counts.
9. **Counting steps, not bullets.** A CI lane that runs three separately-named
tests is three steps, not one. `windows-check` is nine `cargo test` steps
(`ci.yml:66-79`): one combined three-crate run, eggpack, three named service
tests, SCM, two Core integration fixtures, and the full workspace run. It
then verifies the packaged service crate. Count the `- run:` lines.
tests is three steps, not one. `windows-check` is ten `cargo test` steps
(`ci.yml:116-136`): one combined three-crate run, eggpack, three named
service tests, SCM, the live SCM fixture, two Core integration fixtures, and
the full workspace run. It then packages the service crate. Count the
`- run:` lines.
10. **A quoted phrase that was never written.** A governance section attributed
a quoted comment to a skill file that did not contain it. When a doc quotes
another doc, `grep` the quoted string — a paraphrase presented as a
Expand Down
25 changes: 17 additions & 8 deletions .opencode/skills/release-workflow/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,9 @@ Do not publish because code changed. Publication requires its own plan under
Precedent: Verified Core M009 (`eggup-core` → `eggup-archive` 0.1.2),
Eggpack Interop M004 (`eggup-acquisition` → `eggup-eggfetch` → `eggup-eggpack`
0.1.2), Acquisition M009 (`eggup-curl` 0.1.2), Acquisition M010
(`eggup-acquisition` 0.1.3, the current open milestone).
(`eggup-acquisition` 0.1.3, published 2026-10-06), and the `0.2.0` lockstep
train (published 2026-10-24 from one source commit `b612608`: all seven
publishable crates, in seam → adapter → leaf order).

## Order matters: publish dependencies first

Expand All @@ -29,12 +31,17 @@ to ship in seam → adapter → leaf order.

## The exact-pin cascade

`eggup-eggpack` pins its Eggup dependencies exactly (`=0.1.2`). Every other
`eggup-eggpack` pins its Eggup dependencies exactly (`=0.2.0`). Every other
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.
- The same fix **cannot** reach `eggup-eggpack 0.1.2` consumers. The adapter
`eggup-service`) is inherited automatically on the next resolve — **within the
same major version only**. A caret requirement does not cross a major
boundary: `^0.1.0` does not accept `0.2.0`, so a consumer that depends on
both the seam and an adapter inherits the seam's source break only after the
adapter's own requirement is widened. Widening a requirement is a manifest
change that belongs to the publication milestone, not to the fix milestone.
- The same fix **cannot** reach `eggup-eggpack 0.2.0` consumers. The adapter
needs a **separate republication** to inherit a seam fix.

So a single seam fix can become a two-publication event. Name that follow-on
Expand All @@ -43,12 +50,14 @@ explicitly in the plan and in the registry, or it will be discovered late.
## Never

- Do not re-publish a version that already exists on crates.io. A fix needs a new
version (`0.1.2` → `0.1.3`).
- Do not move `v0.1.1` / `v0.1.2` tags. Extend release notes instead.
version (`0.1.3` → `0.1.4`, or `0.2.0` → `0.2.1`).
- Do not move `v0.1.1` / `v0.1.2` / `v0.1.3` / `v0.2.0` tags. Extend release
notes instead.
- Do not publish `eggup-transport-footprint` — it is `publish = false`.
- Do not publish `eggup-service` without explicit maintainer authorization for
Service M011. It is published through `0.1.2`; the M010 correction is the
unpublished `0.1.3` candidate.
the next service milestone. It is published through `0.2.0` (Service M017,
published 2026-10-24); unpublished work sits in the crate's `Unreleased`
section and needs a publication milestone of its own.
- Do not add release CI. Manual publication is a recorded decision.

## Qualification before publishing
Expand Down
51 changes: 37 additions & 14 deletions .opencode/skills/verify-workflow/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,13 +18,22 @@ are authoritative; deep dive is
# + cargo test --workspace --all-targets --all-features --locked
# + cargo doc --workspace --no-deps --locked
# + cargo tree --workspace --locked # review step, not a gate
# + ./scripts/check-docs-truth.sh # documentation agrees with itself, the manifests, and the registry
```

`cargo tree` always exits 0 on a resolvable graph. Read its output: the
dependency-boundary rules (core has only `sha2`; acquisition has zero deps;
the two adapters never reference each other) are enforced by **human review
only** — nothing in the script or CI fails when a boundary is crossed.

`scripts/check-docs-truth.sh` is the only gate command that does not invoke
`cargo`. It is read-only and network-free, and it asserts that the version and
status claims in `docs/`, `README.md`, `AGENTS.md`, the root `CHANGELOG.md`,
`architecture/*.md`, and `plans/registry.md` agree with each other and with the
crate manifests and the per-crate changelogs. It is wired into the local gate
only — no CI lane runs it — so a pull request is not checked for documentation
drift until a lane is added.

## Focused runs

- `cargo test -p eggup-core`, `cargo test -p eggup-core <name>`
Expand All @@ -34,11 +43,11 @@ only** — nothing in the script or CI fails when a boundary is crossed.

| Job | Runner | What it adds |
|---|---|---|
| `stable` | ubuntu | fmt + clippy + full `cargo test` + `cargo doc` + packaged service verification; the only lane running clippy, fmt, and doc |
| `msrv` | ubuntu, pinned `1.89.0` | workspace `cargo check` and packaged service verification at the MSRV |
| `stable` | ubuntu | fmt + clippy + full `cargo test` + `cargo doc` + the three isolated `eggup-transport-footprint` builds (`ci.yml:26-28`) + the packaged-service step; the only lane running clippy, fmt, and doc. That step's registry-resolved compile is **strict** |
| `msrv` | ubuntu, pinned `1.89.0` | workspace `cargo check` + the three isolated `eggup-transport-footprint` checks (`ci.yml:52-54`) + the packaged-service step at the MSRV (registry-resolved compile strict) |
| `service-systemd` | ubuntu-latest | registry-only 0.1.2 negative control, current workspace systemd fixtures, and published registry-only 0.1.3 positive quiescence plus ownership controls |
| `macos` | macos-latest | full `cargo test` + packaged service verification; the only macOS evidence |
| `windows-check` | windows-latest | **runs nine test steps**, ending in a full `cargo test --workspace --all-targets`, then package verification — see below |
| `macos` | macos-latest | full `cargo test` + the two isolated `eggup-transport-footprint` builds (`ci.yml:97-98`) + the packaged-service step; the only macOS evidence. That step's registry-resolved compile is **strict** |
| `windows-check` | windows-latest | **runs ten test steps**, ending in a full `cargo test --workspace --all-targets`, then package verification — see below |

`windows-check` is *not* compile-only, and it is no longer a curated subset. It
runs the platform-sensitive steps, then the two Core fixture files, then the
Expand All @@ -51,16 +60,28 @@ whole workspace:
`service_errors_output_and_permission_remediation_stay_utf8_bounded`,
`lifecycle_failure_detail_is_utf8_safe_bounded_and_control_free`)
4. `cargo test -p eggup-service --lib windows_scm::tests --locked`
5. `cargo test -p eggup-core --test current_executable --locked` — replaces a
5. `cargo test -p eggup-service --test windows_scm_live --locked -- --nocapture`
— the live SCM fixture: it registers a disposable service through the
crate's public API and drives it against the genuine Service Control
Manager. It needs a hosted Windows runner with administrator rights and
records a skip reason on stdout when those rights are absent, which is why
it runs with `--nocapture`.
6. `cargo test -p eggup-core --test current_executable --locked` — replaces a
real running Windows image from a child process, both `KeepInstalled` and
`RollBack`. A Windows claim about self-update is **only** evidenced here.
6. `cargo test -p eggup-core --test stale_lock_recovery --locked` — exercises
7. `cargo test -p eggup-core --test stale_lock_recovery --locked` — exercises
the claim/race fixtures natively; `rename` semantics differ per platform, so
compile-only evidence is not sufficient for M011.
7. `cargo test --workspace --all-targets --locked --no-fail-fast`
8. `cargo package -p eggup-service --locked` — verifies package-produced source on Windows

Step 7 exists because the per-crate steps cannot catch a regression in an
8. `cargo test --workspace --all-targets --locked --no-fail-fast`
9. `cargo package -p eggup-service --locked` — packages the service crate on
Windows and **verifies** it. The verification is **strict**: the packaged sources are
compiled against the registry copy of `eggup-core 0.2.0`. The step ran in the
`--no-verify` form while the source line used core capabilities (Core M014, M017) the
published `eggup-core 0.1.3` did not carry; the `0.2.0` publication train put
`eggup-core 0.2.0` on crates.io and the strict form was restored in commit `2d6e089`
(registry finding 16, closed). Do not re-add `--no-verify`.

Step 8 exists because the per-crate steps cannot catch a regression in an
untargeted crate. It passes `--no-fail-fast` deliberately: this lane is the only
Windows test coverage, so one failing target must not hide the state of the rest.
If a new Core milestone adds platform-dependent filesystem or running-image
Expand All @@ -83,10 +104,12 @@ narrowing the step, and keep `--no-fail-fast`.
## Known coverage gaps — check these before claiming evidence

- `cargo tree` runs nowhere in CI; the boundary check is local-only.
- `msrv` and `windows-check` both omit `--all-features`. The three
`eggup-transport-footprint` binaries are behind `required-features`, so **no
MSRV lane and no Windows lane ever compiles them**. Only `stable` and `macos`
build non-default features.
- `msrv` and `windows-check` both omit `--all-features` **on the workspace
check**. The three `eggup-transport-footprint` binaries are behind
`required-features`, so a lane has to name them: `msrv` checks all three
configurations by dedicated steps (`ci.yml:52-54`), and `stable` and `macos`
build them. **No Windows lane ever compiles them** — that asymmetry is an
open, deliberate decision recorded in the transport-footprint closure.
- The `msrv` package check applies the Rust 1.89 floor to `eggup-service` only;
other crates are covered by the workspace `cargo check`.
- clippy and fmt run on Linux only — a `#[cfg(windows)]` or `#[cfg(target_os = "macos")]`
Expand Down
Loading
Loading