Repository navigation
Keep "stop" only for build-time generation with no Bazel mapping (for discussion) - #55
Open
anakanemison wants to merge 1 commit into
Open
anakanemison wants to merge 1 commit into
anakanemison wants to merge 1 commit into
Conversation
anakanemison
force-pushed
the
mschaller/d3-narrow-the-stop
branch
from
October 26, 2026 13:30
01efb91 to
2219f4a
Compare
armandomontanez
approved these changes
Oct 30, 2026
…ion) The scope list tells the agent to stop at any build-time custom command or generated code. In non-interactive runs the stop is not honored, and where the codegen maps directly onto Bazel the agents migrated it correctly, so the instruction bought nothing; where it does not map, it is the right call and deserves a sharper description. Observed in any2bazel-lab: every skill-guided pono migration (five runs) went through the stop and migrated its bison/flex genrules and stamped version.h, with parser and lexer outputs identical to the reference in all of them; the unguided run did the same, but silently downgraded bison below the declared minimum. The one honored stop (YugabyteDB) was right: the blocker was a PostgreSQL fork built by autotools outside the CMake model and linked into the servers, and the unguided migration that went ahead produced servers that abort at startup for that reason. The scope list now keeps "stop" only for build-time generation with no clear Bazel mapping, described as a sub-build the CMake model does not show whose outputs the binaries link, in SKILL.md and in docs/REFERENCE-cmake.md's scope traps. Without an answer, that is still a stop (the non-interactive fallback earlier in this series says so). A short paragraph under "Create initial BUILD.bazel files" says codegen that maps to a genrule over a host tool or to a ruleset is the agent's to migrate, with the project's declared generator version; the byte comparison of its outputs is the one the convergence-boundary list already requires. The frontmatter description still says "no codegen/custom commands"; it is trigger text, so it is unchanged. In the lab's later runs with this change, two YugabyteDB agents stopped at the PostgreSQL sub-build, the case the narrowed text describes. A pono agent migrated bison and flex with the declared minimum versions enforced, and a Kodi agent continued past FFmpeg's link wrapper, having mapped FFmpeg. This is a proposal for discussion: moving from a blanket stop to guidance is a scope decision for the maintainers, and the evidence is a few runs. Lab-Proposal: P9 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
anakanemison
force-pushed
the
mschaller/d3-narrow-the-stop
branch
from
November 2, 2026 17:51
2219f4a to
0f7d021
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The scope list says to stop at any build-time codegen. The stop is now kept only for generation with no clear Bazel mapping: a sub-build the CMake model does not show, whose outputs the binaries link. Codegen that maps onto a genrule or a ruleset is the agent's to migrate, with the project's declared generator version.
In any2bazel-lab, every guided pono migration went through the stop and migrated its bison and flex rules correctly, and the one honored stop, at YugabyteDB's PostgreSQL sub-build, was right. In later runs, two YugabyteDB agents stopped there, and a pono agent migrated bison and flex with the declared minimum versions. For discussion: moving from a blanket stop to guidance is a scope decision.
Stacked on #54 (tracking issue: #35).
pytest tests/: 186 passed (132 onmain). Lab proposal: P9.🤖 Generated with Claude Code