Repository navigation
Conversation
…gine registry check Rule files state their own paths and tags in front matter and lose the rule-unit markers. Documentation CI no longer checks them against the engine registry, which the engine retires; the guidance check validates the front matter and the 16 KiB file limit instead.
A human vouches for every commit, and the protected API synchronization is the only automated committer. The source examples use a neutral author placeholder, and engine links point to master.
…the engine sync The API synchronization registered Inno.Build.ProductProfiles.Integration.Tests in the project catalog, but no project guide owned it, so complete release validation failed with a missing authoritative entry. Add its guide and list it in the testing project index.
Add the Synchronize draft workflow. After a push to main it moves draft to main with an ordinary fast-forward push, so no commit is created and no force is used. When draft already contains main it does nothing; when draft has newer commits it leaves the merge to the next API synchronization. Document the behavior in the instructions, delivery rules and README, and cover the workflow boundary with a test.
Project guides follow the API page policy: synchronization registers a Synced guide for a new project that no project page owns and deletes the Synced guide of a removed project, while unregistered hand-authored pages stay untouched. The engine tooling change ships separately in the engine repository.
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.
Problem
.agents/rulebook/coverage.json(scripts/check-rule-authority.ps1). The engine retires that registry, and a documentation rule edit needed a matching engine registry commit.documentation.mdcarriedrule-unitmarkers and anchors that existed only for that registry.sourceexample, and linked a retired engine branch.Final behavior
pathsandtagsin front matter, in the format the engine rulebook defines. Engine tasks select them with the engine rule script and an explicit-DocsRoot; this repository remains their sole text authority.scripts/check-rule-authority.ps1and its workflow step are removed. Documentation CI no longer runs engine rule tooling.scripts/check-guidance.mjschecks that every rule file has one-linepathsortagslists and stays within 16 KiB.sourceexamples use<author name>; engine links point tomaster.Rule text is otherwise unchanged.
This pull request also carries the two automated API synchronization commits already on
draft.Verification
Run on Linux with Node 24.21.0 and PowerShell 7.5.4:
node scripts/check-guidance.mjspassed for 88 operational Markdown documents, and rejected a rule file without front matter.npm test: 190 passed.-DocsRootby tag and by path.Not run
Related
InnoEngine replaces its rule registry with plain Markdown rule files in the matching pull request.
Added after opening
fix(docs): add the project guide forInno.Build.ProductProfiles.Integration.Tests. The API synchronization registered the project without a guide, which failed complete release validation with "1 actual projects lack an authoritative entry".feat(ci): add theSynchronize draftworkflow. After each push to main it fast-forwardsdrafttomainwithout creating a commit; it never forces and never touches another branch.docs(rules): describe automatic project guide creation and removal (the tooling change is in refactor(rules): make agent rules plain Markdown with front-matter routing InnoEngine#89).