Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
47 commits
Select commit Hold shift + click to select a range
f5fa847
plans(ci): close M003j dispatch input hardening
Oct 9, 2026
57587b3
plans: register producer convergence corrective chain
Oct 23, 2026
e3c6192
fix(core): unify producer file-digest authority
Oct 23, 2026
414f998
plans: accept ADR-0006 and close Build/Qualification M007
Oct 23, 2026
9cf0bf8
fix(ci): converge producer rule authority onto core and manifest
Oct 23, 2026
41b752f
plans: close CI/Release M003l producer rule authority convergence
Oct 23, 2026
7e7cb6a
feat(core): record compatibility floor verification status
Oct 23, 2026
282430b
plans: close Build/Qualification M008 compatibility floor verification
Oct 23, 2026
eb77d19
feat(cli): add local producer operator commands
Oct 23, 2026
8950eb9
docs(cli): document the local producer operator commands
Oct 23, 2026
6a7cb4c
fix(ci): converge consumer-validator execution onto the bounded runner
Oct 23, 2026
97c48bd
plans: close Build/Qualification M009 and CI/Release M003m
Oct 23, 2026
98f26cd
plans: register M009 and M003m closures in the control surface
Oct 23, 2026
93fc17b
fix(cli): rename the misleading operator artifacts flag
Oct 23, 2026
300fa9b
docs(cli): correct the quickstart scratch-repo placement
Oct 23, 2026
50f301a
plans: make the closure records' historical-range citations unambiguous
Oct 23, 2026
4692bd5
refactor(ci): consolidate the producer's duplicated implementations
Oct 23, 2026
e66c7d1
refactor(ci): split the CI crate into a module tree
Oct 23, 2026
fa82486
plans: close CI/Release M003n producer implementation consolidation
Oct 23, 2026
d8d6a5b
docs: reconcile the architecture baseline with the review chain
Oct 23, 2026
e0e1510
fix(bootstrap): restore the adversarial digest fixture coverage
Oct 23, 2026
c17bdbe
fix(core): close the floor contradiction mask and the digest zero-len…
Oct 23, 2026
d2fbd07
fix(cli): correct the local producer operator defects
Oct 23, 2026
b205de6
fix(ci): refuse an over-long generated directory and name the digest …
Oct 23, 2026
86073c6
plans: register the follow-up review corrective chain
Oct 23, 2026
3393269
docs(README): pass the two flags the manifest command now requires
Oct 23, 2026
be01ac7
docs(architecture): re-base every citation onto the corrected produce…
Oct 23, 2026
e5174d1
docs: re-point the ecosystem M003a closure record's pre-split CI anchors
Oct 23, 2026
2768ced
docs: align the remaining indicative-anchor claims with the measured set
Oct 23, 2026
eec3eee
docs(architecture): correct the citation-verification state to measur…
Oct 23, 2026
62b649f
docs: document the operator family and close the F12 stale claims
Oct 23, 2026
e166cf1
docs: re-point closure-record and seam citations into the current tree
Oct 23, 2026
6ff496a
docs(architecture): re-measure the core and contract crate baselines
Oct 23, 2026
5c501d8
docs: correct the measured citation counts after the re-base
Oct 23, 2026
c908996
docs: close the residual citation rot and record the ADR-0006 compati…
Oct 23, 2026
d4d5e43
plans: register Release Manifest M004 for the ADR-0006 0.1.1 publication
Oct 25, 2026
182a0a1
fix(core): terminate an already-exited process group without failing …
Oct 26, 2026
b03e5c4
chore(ci): temporary diagnostic for the macOS validator failure
Oct 26, 2026
16fee25
chore(core): temporary diagnostic for the process-group termination e…
Oct 26, 2026
27cb16c
fix(core): tolerate a group signal macOS refuses for an exited child
Oct 26, 2026
4ce4fb8
plans: close CI M003p, the macOS process-group termination defect
Oct 26, 2026
e231e5e
plans: close Release Manifest M004 — eggpack-manifest 0.1.1 published
Oct 26, 2026
f52f52b
Merge M003j closure and reconcile planning state
Nov 13, 2026
efd8179
ci: serialize portability workspace tests
Nov 13, 2026
77b0417
ci: scope serial workspace test to portability lanes
Nov 13, 2026
ae50c5e
cli: classify bounded package build failures
Nov 13, 2026
283731a
test(cli): shorten Windows Cargo fixture paths
Nov 13, 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
15 changes: 10 additions & 5 deletions .skills/contract-and-manifest-surface/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,11 +39,16 @@ So "it's optional, so it's safe" is false here. A shape change to the published
manifest is a compatibility event, not a convenience. It needs a plan, an ADR if
it establishes a public compatibility contract, and downstream coordination.

`eggpack-manifest 0.1.0` is live on crates.io and consumed by `eggup-eggpack`
downstream. The published `src/lib.rs` is byte-identical to the
consumer-qualified pin the consumer was tested against — that equality is a
deliberate, recorded property, not an accident. The other six workspace crates
are unpublished; do not publish one as a side effect of unrelated work.
`eggpack-manifest 0.1.1` is live on crates.io. `0.1.0` remains published and
resolvable. `0.1.1` carries two narrowings of the published acceptance set —
the ADR-0006 all-zeros digest refusal and the document bound that
`ReleaseManifest::validate` now measures — and both are recorded as
compatibility events in
`plans/closure/release-manifest/004-status.md`. `eggup-eggpack` consumes
`=0.1.0` and is the named affected consumer; it pins an exact version, so it
does not pick up `0.1.1` automatically, and its bump needs a plan registered
in the Eggup repository. The other six workspace crates are unpublished; do
not publish one as a side effect of unrelated work.

## The two documents say different things

Expand Down
9 changes: 5 additions & 4 deletions .skills/planning-and-closure/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,10 +12,11 @@ requires contract-level acceptance evidence. `plans/003-planning-process.md` is

## Before you open anything

1. Read `plans/registry.md` §"Next handoff". As of the last review **no
implementation milestone is `ready`** — the next three lines (Contract M003,
Bootstrap M003, Ecosystem M003 eggsearch) are *research/plan decisions*, not
execution. If your idea is one of them, the deliverable is a plan, not code.
1. Read the current `plans/registry.md` status tables and §"Next handoff".
Milestone status changes over time; use the registry and linked subsystem
roadmap as the authority instead of relying on remembered status snapshots.
If no implementation milestone is `ready`, author or update a plan before
implementing work that has not been handed off.
2. Check the subsystem roadmap (`plans/subsystems/<subsystem>-roadmap.md`). A
plan may already exist under a name you did not guess.
3. Only then write anything.
Expand Down
4 changes: 2 additions & 2 deletions AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ Read the index in `overview.md` and follow one link. Grouped by what they cover:

| Area | Document |
|---|---|
| Vocabulary, authority, phases, ADRs 0001–0005, `dist` (disposition C: prior art only) | [principles-roadmap.md](architecture/principles-roadmap.md) |
| Vocabulary, authority, phases, ADRs 0001–0006, `dist` (disposition C: prior art only) | [principles-roadmap.md](architecture/principles-roadmap.md) |
| Planning process, closure discipline, registry | [planning-and-governance.md](architecture/planning-and-governance.md) |
| Layout authority, schema-v1, conformance validators | [contract.md](architecture/contract.md) |
| Final-bytes evidence, bounds, collision rules, publication status | [manifest.md](architecture/manifest.md) |
Expand All @@ -89,4 +89,4 @@ Read the index in `overview.md` and follow one link. Grouped by what they cover:
## Planning conventions

- Closure discipline: `plans/closure/<subsystem>/NNN-status.md`. Compilation ≠ closure. History never rewritten — correctives are new `NNNa` plans; superseded material goes to `plans/archive/`.
- Current handoff (per `plans/registry.md`): no Eggpack plan is `ready`. Contract M003, Bootstrap M003, and Ecosystem M003a are all closed, so the contract-conformance and bootstrap-installers subsystems have no open work. Ecosystem M003b is **closed** at `plans/closure/ecosystem-adoption/003b-status.md`: the implementation landed in `eggstack/eggsearch`, staging evidence came from run `37531104901` (draft `405157598`, exact 19-asset inventory), provenance attested the staged bytes in run `37561960304`, and the draft was published as eggsearch `v0.4.2` on 2026-10-07. Planning Hygiene M002 is closed at `plans/closure/planning-hygiene/002-status.md` (docs/evidence-only). The next Eggpack line is whatever the registry lists as `ready`; if that table is empty, the next action is plan authoring, not implementation.
- Current handoff (source: `plans/registry.md`): no milestone is **in progress** and none is registered **ready**; the last open obligation of the 2026-10-23 review chain — Release Manifest M004, the ADR-0006 `eggpack-manifest 0.1.1` patch release and the compatibility record ADR-0006 §5.4 requires — is **closed**: `0.1.1` is published to crates.io (checksum `352c3e327159615b763298e911e239f1decc4a2c9e28c28be8ddd28e50515e37`, tagged `eggpack-manifest-v0.1.1`), and both narrowings the package carries — the ADR-0006 digest rule and the `3ef806f` document bound — are recorded as compatibility events. The 2026-10-23 post-implementation review chain is closed (Build/Qualification M007, M008, M009; CI/Release M003l, M003m, M003n; Planning Hygiene M003; Bootstrap M003a), and **ADR-0006 is accepted** (Option A), having gated CI M003l's digest-acceptance work package only. A follow-up review of that chain's own output registered and closed a second corrective chain: Build/Qualification M007a (digest zero-length read refusal), M008a (floor contradiction mask and ELF offset overflow), M009a (local producer operator defects, including an input-destroying staging path), and CI/Release M003o (renderer panic and digest diagnostics). **The chain's first hosted CI run failed on macOS and registered a third corrective, CI/Release M003p**: the shared bounded runner treated a failed process-group signal as fatal, but macOS refuses to signal a group holding the unreaped zombie of an exited child and reports `EPERM` where Linux signals it successfully, so an output-bound violation was reported as a launch failure. M003p decides by observing whether the child has exited rather than by reading the errno, and hosted run `40263176191` is green on all four lanes. Both review chains left one obligation open — ADR-0006 §5.2/§9's `eggpack-manifest 0.1.1` publication and the release-manifest compatibility record — and M004 owns it; the `0.1.1` package carries **two** narrowings of the published acceptance set, the ADR-0006 digest rule and the `3ef806f` document bound, and only the first had been recorded. **Blocked** are Ecosystem M004 (Gregg sibling bundle), Ecosystem M005 (CodeGG runfile bundle), and Ecosystem M006 (Egress archive pair), each on its named adoption evidence and bundle/archive review; the provenance/authenticity line is **planned** pending a dedicated trust ADR, and Python/wheel adapters are **planned** behind broader native adoption. Contract M003, Bootstrap M003, and Ecosystem M003a/M003b are closed, so the contract-conformance and bootstrap-installers subsystems have no open work. The next Eggpack line is whatever the registry lists as `ready`; if that table is empty, the next action is plan authoring, not implementation.
5 changes: 4 additions & 1 deletion Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

128 changes: 101 additions & 27 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,9 +19,10 @@ EGGPACK=./target/debug/eggpack
$EGGPACK --version # eggpack 0.1.0
```

A release is three pure file-in/file-out commands — no network, no token, no
real build. These need six input files: a contract, a pack config, build
bindings, qualification bindings, a draft template, and a GitHub policy.
The `ci` family's rendering path is three pure file-in/file-out commands — no
network, no token, no real build. These need six input files: a contract, a pack
config, build bindings, qualification bindings, a draft template, and a GitHub
policy.
[docs/quickstart.md](docs/quickstart.md) writes all six and runs the whole flow
end to end (~5 minutes, no network); every command and expected output there was
executed verbatim.
Expand Down Expand Up @@ -53,35 +54,108 @@ The rendered workflow is read-only (`contents: read`) and chains

`generate` and `check` are the only user-facing commands in the `ci` family. The nine `ci _*`
runners are the file-in/file-out steps the generated workflow replays inside
CI. A bare `eggpack` prints every subcommand.

There is one other user-facing family, `contract expand`: a bounded, local-only
projection that reads one producer contract and prints one scalar, so a consumer
repository can read a producer fact instead of re-implementing TOML parsing and
template expansion.

CI. A bare `eggpack` prints every subcommand; its usage line leads with the
operator family — `usage: eggpack <check|plan|package|qualify|collect|manifest|ci|contract> [options]`.

There are two other user-facing families.

## The operator family — build a release locally

Six commands drive the producer on a workstation: `check` → `plan` → `package` →
`qualify` → `collect` → `manifest`. Unlike the `ci` rendering path, this family
**performs a real Cargo build** — `package` invokes `cargo +<toolchain>` on
every planned target — but it still performs no network access and needs no
GitHub token. The six commands share one implementation with the `ci _*`
runners, so both surfaces derive one plan from one rule set.

| Command | Class | What it does |
|---|---|---|
| `check` | validation | Resolves the whole planning input set and writes nothing. |
| `plan` | validation | Writes the `ReleasePlan` — the release identity, the selected targets, and their policies. |
| `package` | build | Builds every planned target's candidates under an output root. |
| `qualify` | build | Qualifies the built candidates and writes qualification evidence. |
| `collect` | release aggregation | Aggregates the qualified candidates into a finalized release tree. |
| `manifest` | final-bytes evidence | Derives `release-manifest.json` from the finalized release tree — and checks it against the finalized tree it describes. |

Three optional flags are available on the family: `--qemu-sysroot` (the QEMU
sysroot for an emulated target), `--identity-mode` (a caller-chosen
release-identity mode), and `--consumer-validators` (a checked-in consumer
validator map). The producer policy and both bindings documents may be given as
**TOML or JSON**. `qualify` refuses `--output-dir == --artifacts-dir`, because
staging the qualification artifacts into the directory the candidates were read
from would rewrite the very bytes the qualification is about; and `manifest`
reads every archive member back out of the finalized `.tar.gz` and compares it
against the collected manifest, so a manifest that disagrees with its archive is
refused rather than emitted.
```sh
$EGGPACK contract expand --contract contract.toml --release-id 1.2.6 \
--target linux-x64 --field asset
# eggsact-1.2.6-x86_64-unknown-linux-gnu
# 1. validate the planning inputs — writes nothing
$EGGPACK check --contract contract.toml --pack-config pack-config.toml \
--build-bindings build-bindings.toml --qualification-bindings qualification-bindings.toml \
--selected linux-x64 --release-id 1.2.6 --source-revision "$REV"
# 2. resolve the release identity — writes the plan
$EGGPACK plan --contract contract.toml --pack-config pack-config.toml \
--build-bindings build-bindings.toml --qualification-bindings qualification-bindings.toml \
--selected linux-x64 --release-id 1.2.6 --source-revision "$REV" \
--output out/release-plan.json
# 3. build every planned target — a real Cargo build
$EGGPACK package --release-plan out/release-plan.json \
--build-bindings build-bindings.toml --source-root demo --output-root out/build
# 4. qualify the candidates
$EGGPACK qualify --contract contract.toml --release-plan out/release-plan.json \
--build-bindings build-bindings.toml --qualification-bindings qualification-bindings.toml \
--artifacts-dir out/build --output-dir out/qualification
# 5. aggregate the qualified candidates into a finalized release tree
$EGGPACK collect --contract contract.toml --release-plan out/release-plan.json \
--build-bindings build-bindings.toml --qualification-bindings qualification-bindings.toml \
--artifacts-dir out/qualification --output-root out/release/finalized
# 6. derive the final-bytes evidence — the manifest sits beside the finalized root
$EGGPACK manifest --contract contract.toml --release-plan out/release-plan.json \
--finalized-root out/release/finalized --output out/manifest/release-manifest.json
```
[docs/quickstart.md](docs/quickstart.md) runs this path end to end with the
exact inputs and the quoted output of every step.
## The `contract` family
`contract expand` is a bounded, local-only projection that reads one producer
contract and prints one scalar, so a consumer repository can read a producer
fact instead of re-implementing TOML parsing and template expansion.

It performs no network access, no repository discovery, and no release
selection, and it fails closed on bundle/archive targets for direct-only fields.
See [crates/eggpack-cli/README.md](crates/eggpack-cli/README.md).
```sh
# 1. validate the planning inputs — writes nothing
$EGGPACK check --contract contract.toml --pack-config pack-config.toml \
--build-bindings build-bindings.toml --qualification-bindings qualification-bindings.toml \
--selected linux-x64 --release-id 1.2.6 --source-revision "$REV"

## Verify
# 2. resolve the release identity — writes the plan
$EGGPACK plan --contract contract.toml --pack-config pack-config.toml \
--build-bindings build-bindings.toml --qualification-bindings qualification-bindings.toml \
--selected linux-x64 --release-id 1.2.6 --source-revision "$REV" \
--output out/release-plan.json

```sh
scripts/check-local.sh # fmt, check, clippy, tests, doc, package, MSRV
# 3. build every planned target — a real Cargo build
$EGGPACK package --release-plan out/release-plan.json \
--build-bindings build-bindings.toml --source-root demo --output-root out/build

# 4. qualify the candidates
$EGGPACK qualify --contract contract.toml --release-plan out/release-plan.json \
--build-bindings build-bindings.toml --qualification-bindings qualification-bindings.toml \
--artifacts-dir out/build --output-dir out/qualification

# 5. aggregate the qualified candidates into a finalized release tree
$EGGPACK collect --contract contract.toml --release-plan out/release-plan.json \
--build-bindings build-bindings.toml --qualification-bindings qualification-bindings.toml \
--artifacts-dir out/qualification --output-root out/release/finalized

# 6. derive the final-bytes evidence — the manifest sits beside the finalized root
$EGGPACK manifest --contract contract.toml --release-plan out/release-plan.json \
--build-bindings build-bindings.toml --qualification-bindings qualification-bindings.toml \
--finalized-root out/release/finalized --output out/manifest/release-manifest.json
```

## Docs
[docs/quickstart.md](docs/quickstart.md) runs this path end to end with the
exact inputs and the quoted output of every step.

## The `contract` family

- [docs/quickstart.md](docs/quickstart.md) — the runnable walkthrough, in full
- [docs/release-identity-policy.md](docs/release-identity-policy.md) — opt-in
source-tag and manifest-ID mapping policy
- [docs/](docs/) — user guides and the workspace layout
- [crates/eggpack-cli/README.md](crates/eggpack-cli/README.md) — command reference
- [architecture/overview.md](architecture/overview.md) — pipeline, crate boundaries, invariants
- [AGENTS.md](AGENTS.md) — operating contract, verification, planning conventions
`contract expand` is a bounded, local-only projection that reads one producer
contract and prints one scalar, so a consumer repository can read a producer
fact instead of re-implementing TOML parsing and template expansion.
Loading
Loading