feat(xim): recipe packaging revision and the install_targets record (2026.9.27.1)

[speak-agent]

Summary

xlings 2026.9.27.1: a recipe's packaging revision (openxlings#620), and a record of what each install request resolved to.

Revision (openxlings#620)

A version entry may state revision = N (libxpkg 0.0.58), counting changes to what a recipe installs under an unchanged upstream version. Until now the store could only answer "is 2.44.3 here", so a fixed recipe never reached a machine that had installed the broken payload.

• Stamp: the payload stamp records the revision it was built from, always written as "revision": N in .xpkg-install.json.
• Verdict: one function, payload_revision_verdict (install_state), decides whether a payload is current.
  • A payload is current if and only if its recorded revision equals the recipe's.
  • A stamp without the field reads as revision 0, so only a recipe that states revision 1 or higher reinstalls.
  • No stamp, or a stamp recording a failed install, gives no verdict.
• Planning: the resolver plans a stale payload as not installed. The installer asks the same verdict again and states the reason, for example reinstalling glibc@2.44.3: recipe revision 1, installed revision 0.
• Replacement: the version is never left without a payload.
  • The old tree is renamed to <data>/stale/ and the new one is installed at the real path.
  • On success the old tree is deleted; on any failure it is renamed back (PayloadReplacement).
• Plan entries: install_plan entries carry the revision as a third element and the reinstall reason as their note.

install_targets (interface protocol 1.1, additive)

• The top-level install reports {request, namespace, name, version, revision, status, payload_dir} per request, in request order, with status installed, already_present or failed.
• It is emitted on every path: fresh installs, "everything already installed" (which previously put nothing on the wire), and failures.
• Nested installs and dry runs do not report.
• install_summary.success now counts only what the run installed, as its comment already stated. This is the one observable change for existing clients.
• Documented in docs/spec/interface-ndjson-v1.md and docs/spec/xpkg-manifest-v1.md.

Version-grammar conformance vectors

tests/data/semver-vectors.tsv lists request, available versions, active version and expected result. tests/unit/test_semver_vectors.cpp drives every vector through the resolver. mcpp vendors the file and runs the vectors without an active version against its own implementation.

Tests

• Unit: test_install_state, test_interface_protocol, test_payload_remove, test_semver_vectors. 55 of 56 pass locally; test_identity fails only because the tests ran as root (uid 0).
• e2e: tests/e2e/install_revision_test.sh (E2E-121).

Dependencies

• libxpkg 0.0.58: mcpp.toml depends on it (feat(model): a version entry's packaging revision (0.0.58) libxpkg#1). It must be published in mcpp-index before CI can resolve it, and mcpp.lock must be regenerated against the published package.
• Recipe: the first recipe that uses the field is glibc 2.44.3 revision 1 (feat(spec, glibc): version-entry revision; glibc 2.44.3 revision 1 reaches its own locale and gconv data xim-pkgindex#1).
• Consumer: mcpp 2026.9.27.1 reads install_targets and the recorded revision.

Refs openxlings#620, openxlings#621.

---

🤖 Generated with Claude Code

https://claude.ai/code/session_01MajuX4J8ewFeWvZJjzRJt5

---

Generated by Claude Code

[speak-agent]

Superseded by openxlings#622.