Files
swaitsandClaude Opus 4.7 9232c16f7c
mdBook / build (push) Canceled after 0s
mdBook / deploy (push) Canceled after 0s
feat(versioning): snapshot corpus per spec version
A frozen spec is only meaningful if it's paired with the corpus
that was current at release time — otherwise a v0.1.0 reader
follows "see corpus/payloads/ack/" and lands on a file whose
test vectors may have changed since v0.1.0 was cut.

Three changes:

1. `cut-version` now copies BOTH src/ AND corpus/ into the
   snapshot directory. A release is the pair, not just the text.

2. The corpus URL rewriting in cut-version now retargets
   /tree/main/corpus -> /tree/main/versions/<v>/corpus (and the
   blob variant). This lets the link resolve on GitHub from main
   alone — no git tag required, since the frozen copy is a real
   path under main. Downgrades the "tag is REQUIRED" message from
   last commit back to "optionally tag the commit".

3. The frozen corpus's spec_ref fields get rewritten too: from
   `src/04-payload-ack.md` to `versions/<v>/04-payload-ack.md`,
   so a reader following a test vector lands on the spec text the
   vector was paired with at release time.

versions/v0.1.0/ regenerated from scratch via `just cut-version v0.1.0`
to pick up the corpus snapshot + the new sed patterns. The release
is now self-consistent: v0.1.0 spec links go to v0.1.0 corpus, which
links back to v0.1.0 spec.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-12 10:38:02 -06:00

102 lines
4.1 KiB
Makefile

# meshcore-spec — task runner.
#
# Every recipe runs under `mise exec -- sh -c …`, so mise-pinned tools
# (see mise.toml) are on PATH and we never accidentally use a system
# mdbook of the wrong version. `sh` is intentional — keep recipes
# POSIX-compatible.
#
# Background on `preview` vs the other build recipes:
# `mdbook build` (used by `build` and `serve`) produces a single-
# version site with no versions.json, so the version-picker stays in
# its label-only fallback there. To see the picker as a dropdown
# locally, run `just preview` — it builds the full multi-version site
# AND serves it over HTTP, since browsers block fetch() under file://.
set shell := ["mise", "exec", "--", "sh", "-c"]
# Show the available recipes.
_default:
@just --list
# Install / refresh tools pinned in mise.toml.
setup:
mise install
# Build a single-version site into ./book/ (mdbook output dir).
build:
mdbook build
# Build the full multi-version site into ./_site/ (same logic CI runs).
build-site:
sh scripts/build-site.sh
# Build the multi-version site and serve it at http://localhost:8000/.
preview: build-site
@echo ""
@echo "Serving ./_site/ at http://localhost:8000/"
@echo " http://localhost:8000/latest/ - rolling main"
@echo " http://localhost:8000/v0.1.0/ - frozen v0.1.0"
@echo " Ctrl-C to stop."
@echo ""
cd _site && python3 -m http.server 8000
# Live-preview a single-version build at http://localhost:3000 (auto-reload).
serve:
mdbook serve --open --port 3000
# Remove all build outputs (single- and multi-version).
clean:
rm -rf book _site
# Run the corpus validator.
validate:
python3 tools/validate.py corpus/
# Snapshot ./src/ as ./versions/VERSION/. Usage: just cut-version v0.2.0
cut-version VERSION:
#!/usr/bin/env sh
set -eu
case "{{VERSION}}" in
v[0-9]*.[0-9]*.[0-9]*) ;;
*) echo "Version must look like vX.Y.Z (got '{{VERSION}}')" >&2; exit 1 ;;
esac
if [ -e "versions/{{VERSION}}" ]; then
echo "versions/{{VERSION}} already exists; not overwriting." >&2
exit 1
fi
mkdir -p versions
# Snapshot both the spec text AND its paired test corpus, so the
# release is a self-contained pair. The site infrastructure
# (book.toml, theme, scripts, tools) stays unversioned at the
# repo root and applies to every build.
cp -R src "versions/{{VERSION}}"
cp -R corpus "versions/{{VERSION}}/corpus"
# Freeze the version marker in the snapshot. src/ keeps the literal
# `latest (main)` so the rolling /latest/ build stays accurate.
sed -i 's|`latest (main)`|`{{VERSION}}`|' "versions/{{VERSION}}/00-overview.md"
if ! grep -q '`{{VERSION}}`' "versions/{{VERSION}}/00-overview.md"; then
echo "warning: expected version marker not found in 00-overview.md; the" >&2
echo "snapshot still says 'latest (main)'. Check that src/00-overview.md" >&2
echo "contains the marker line ('**Spec version:** \`latest (main)\`')." >&2
fi
# Repoint corpus URLs in the snapshot's spec text from main/corpus
# to main/versions/<v>/corpus — the frozen copy lives in the repo
# at a stable path on main, so the GitHub links resolve without
# needing a git tag. -maxdepth 1 keeps the substitution off the
# corpus *.json files (they get their own pass below).
find "versions/{{VERSION}}" -maxdepth 1 -name '*.md' -exec sed -i \
-e 's|/tree/main/corpus|/tree/main/versions/{{VERSION}}/corpus|g' \
-e 's|/blob/main/corpus|/blob/main/versions/{{VERSION}}/corpus|g' \
{} +
# Repoint spec_ref inside the frozen corpus to this version's
# frozen spec, so a reader following a test vector lands on the
# spec text the vector was paired with at release time.
find "versions/{{VERSION}}/corpus" -name '*.json' -exec sed -i \
's|"spec_ref": "src/|"spec_ref": "versions/{{VERSION}}/|g' \
{} +
echo "Snapshotted: src/ + corpus/ -> versions/{{VERSION}}/"
echo
echo "Next steps:"
echo " - git add versions/{{VERSION}} && commit (e.g. \"release {{VERSION}}\")"
echo " - optionally tag the commit: git tag {{VERSION}}"