Install the three agents, the toolbox updater and auto-merge - #29
Merged
Merged
Conversation
Cesium.NET was one of three repositories in a fleet of twelve with no agents installed, and the only one of those three with a live upstream behind it. CesiumC, its own wrapper, has had all three for weeks. The dashboard was saying so and it took a screenshot to notice: the grey v1 badge is not "up to date", it is "no agents that could be behind" -- the metrics collector distinguishes repositories that call the toolbox's reusable workflows from repositories that have agents compiled locally, and this one was only ever the first kind. binding-updater keeps the binding current with the header and fixes the generator when a new construct breaks it. ci-doctor triages failed runs. cpp-wrapper-porter is installed even though this is not a wrapper: its prompt opens by asking whether the repository is its at all, and JoltPhysics.NET carries it on the same terms. toolbox-update.yml comes with them. Without it a repository keeps the commit it was compiled against indefinitely and nothing fails to reveal it -- JoltPhysics.NET has the updater and still drifted to v1.23.0 while the fleet moved to v1.29.0, so going without is strictly worse. auto-merge goes on, because installing something that opens pull requests nobody merges is not automation. The risk is narrower than it looks and the comment in api-gate.yml says why: the updater regenerates C# from a C header rather than writing C, which is precisely what the gate measures, and merging is not publishing -- the eight-leg smoke test still stands between a merge and nuget.org. The authoring scaffolding gh aw regenerates (.vscode, .github/agents, .github/skills, .github/mcp.json, copilot-setup-steps.yml) is deleted rather than committed, and `gh aw compile --strict` passes with no errors or warnings.
Contributor
API gate: additiveEvery symbol that existed still exists, unchanged. Nothing that compiled before stops compiling.
Enum and constant values are part of the measured surface: a renumbering keeps compiling and sends the wrong number to the driver, so it counts as a removal. |
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.
Cesium.NET was one of three repositories in a fleet of twelve with no agents installed — and the only one of those three with a live upstream behind it.
CesiumC, its own wrapper, has had all three for weeks.The dashboard was saying so, and it took a screenshot to notice
The grey
v1badge is not "up to date" — it is "no agents that could be behind". The metrics collector distinguishes repositories that call the toolbox's reusable workflows from repositories that have agents compiled locally, and this one was only ever the first kind.What lands
v1.23.0while the fleet moved tov1.29.0, so going without is strictly worse.auto-merge goes on
Installing something that opens pull requests nobody merges is not automation. The risk is narrower than it looks, and
api-gate.ymlnow says why: the updater regenerates C# from a C header rather than writing C, which is precisely what the gate measures — API delta plus every P/Invoke resolving in all nine shipped libraries. Merging is not publishing: the eight-leg smoke test still stands between a merge and nuget.org.gh aw compile --strictpasses with 0 errors and 0 warnings, and the authoring scaffolding it regenerates is deleted rather than committed.One correction to the onboarding playbook while I was here: it says "create nine
agent:labels first". That is not true today — JoltPhysics.NET has two and CesiumC has none, both with three working agents. They are created when an agent first uses one.