Skip to content

Say where the parity artifacts belong - #51

Open
anakanemison wants to merge 1 commit into
mschaller/u15-version-stampfrom
mschaller/u16-parity-artifacts-location
Open

anakanemison wants to merge 1 commit into
mschaller/u15-version-stampfrom
mschaller/u16-parity-artifacts-location

Conversation

@anakanemison

@anakanemison anakanemison commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

SKILL.md said only that the models, aquery.json and diff.json live "in or beside" the repository. It now says: at the repository root beside any2bazel.json, gitignored with a comment naming the command that regenerates them, and not in a temp directory, so a migration is auditable without committing large JSON.

In any2bazel-lab, one migration left its artifacts in a session temp directory, so nothing showed it had converged. In later graphicsgems and lensfun runs, they were at the root, gitignored, with the command.

Stacked on #50 (tracking issue: #35). pytest tests/: 186 passed (132 on main). Lab proposal: P6.

🤖 Generated with Claude Code

The procedure listed the parity artifacts to produce (the two models,
aquery.json, diff.json) but said only that they live "in or beside" the
target repo, so where they ended up was up to the agent.

Measured in any2bazel-lab: one migration wrote its diff and
both models to a session-scoped temp directory, so nothing in the
repository showed that it had converged; another kept them at the repo
root, gitignored them, and recorded how to regenerate them, unprompted.

The preamble now says: at the target repo root beside any2bazel.json,
gitignored with a comment naming the regeneration command, not in a temp
directory. That makes a migration auditable by default without committing
large generated JSON.

In the lab's later graphicsgems and lensfun runs with this change, the
artifacts were at the root, gitignored, with the regeneration command.

Lab-Proposal: P6

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant