Artifact Description [0697e7e19a]

Artifact 0697e7e19ac575d0b09f957256a90de524192b03128b15210bd37fec767097a4:

• File src/packaging_test.zig
  • 2026-07-18 20:52:25 — part of check-in [3645c03e2d] on branch release-0.1 — Narrow .paths to docs/rfcs so working docs never ship in a package

    `.paths` named the whole `docs` directory. A Zig package is cut from the working tree, not from what fossil tracks, so the ignore-glob does not govern it: a bare `docs` entry ships whatever sits under docs/ at package time — including the ignore-glob'd docs/plans/*.md working documents, which are internal and must never leave the repository.

    Naming docs/rfcs directly is also what the repo convention already states (0ad7fa92c6: 'docs/ is for the RFCs only'); the manifest now encodes that convention instead of relying on docs/ happening to stay clean. A new pin in src/packaging_test.zig asserts it so the bare-docs form cannot drift back. (user: dmestas, size: 13970) [annotate] [blame] [check-ins using]

  • 2026-07-18 21:11:09 — part of check-in [0c22d3a950] on branch trunk — Merge release-0.1: Narrow .paths to docs/rfcs so working docs never ship in a fetched package

    Second increment of the 0.1.0 release sequence, landed on trunk as it completes rather than accumulating to a big-bang merge at the end.

    The increment: build.zig.zon .paths named the whole docs directory. A Zig package is cut from the working tree, not from what fossil tracks, so the ignore-glob does not govern it -- a bare docs entry ships whatever sits under docs/ at package time, including the ignore-glob'd docs/plans/*.md working documents, which are internal and must never leave the repository. .paths now names docs/rfcs directly, which is also what the repo convention already states (0ad7fa92c6: "docs/ is for the RFCs only"); the manifest encodes that convention instead of relying on docs/ happening to stay clean.

    Evidence: a new pin in src/packaging_test.zig asserts both halves -- that .paths contains "docs/rfcs", and, as negative space, that a bare "docs" entry is absent, so the ship-everything form cannot drift back unnoticed.

    The merged tree was re-verified before this commit: zig fmt --check, zig build, and zig build test all green on the merge result. Green on the branch does not imply green on the merge, since trunk advances with concurrent work.

    No borrowed techniques in this change, so no attribution is owed. (user: dmestas, size: 13970) [annotate] [blame] [check-ins using]