cc1ad064d7
The current manifest stamped package.json's version into itself (9 lines), so every RC/stable version bump made the committed artifact stale on every open branch: lint failed until authors committed content-free regeneration diffs, which also dragged the resources/skills-filtered update-roundtrip matrix onto unrelated PRs. Cutting a release tag whose skills tree changed had the same effect through release-mapping.json. - current-manifest.json is now schema 2 and content-only; the generator no longer reads package.json. Registry and mapping stay schema 1 so the append-only released-history guard keeps its schema gate. - The running build's version enters at the IPC boundary (skills:freshnessInventory passes app.getVersion()) and threads through the inventory to placement observation; current-revision placements are labeled with it while historical revisions keep resolving through the release mapping. The artifact loader and its cache stay content-only. - verify tolerates a committed release mapping that is a byte-exact prefix of the derived one when every missing trailing row's revisions equal the current manifest (a just-cut tag over unchanged-since bytes); such rows are provably redundant until the next real regeneration adds them. Artifacts now change only when skills/ content changes. |
||
|---|---|---|
| .. | ||
| computer-e2e.yml | ||
| daemon-relocation-spike.yml | ||
| e2e.yml | ||
| golden-e2e-experiment.yml | ||
| homebrew-bump.yml | ||
| issue-os-labeler.yaml | ||
| linux-wayland-gpu-sandbox.yml | ||
| mobile-android-release.yml | ||
| mobile-ios-release.yml | ||
| mobile.yml | ||
| pr.yml | ||
| pullfrog.yml | ||
| readme-downloads-badge.yml | ||
| release-cut.yml | ||
| release-mac-build.yml | ||
| skill-update-roundtrip.yml | ||
| terminal-perf.yml | ||
| track-community-prs.yaml | ||
| win-update-e2e.yml | ||
| win-update-survival-e2e.yml | ||
| windows-signing-rehearsal.yml | ||