docs(governance): trim AGENTS.md narrative prose to the sober standard #NOT YET READY - #1583
Draft
djdomi wants to merge 40 commits into
Draft
docs(governance): trim AGENTS.md narrative prose to the sober standard #NOT YET READY#1583djdomi wants to merge 40 commits into
djdomi wants to merge 40 commits into
Conversation
chore(governance): open worktree for #1578 AGENTS.md sober-prose trim
CLD-1786823828 Refs #1578
CLD-1786823993 Refs #1578
CLD-1786824049 Refs #1578
CLD-1786824080 Refs #1578
CLD-1786824107 Refs #1578
CLD-1786824137 Refs #1578
CLD-1786824226 Refs #1578
CLD-1786824249 Refs #1578
CLD-1786824304 Refs #1578
CLD-1786824337 Refs #1578
CLD-1786824365 Refs #1578
CLD-1786824426 Refs #1578
CLD-1786824454 Refs #1578
CLD-1786824581 Refs #1578
CLD-1786824608 Refs #1578
CLD-1786824638 Refs #1578
CLD-1786824671 Refs #1578
CLD-1786824714 Refs #1578
CLD-1786824735 Refs #1578
CLD-1786824765 Refs #1578
CLD-1786824803 Refs #1578
CLD-1786824826 Refs #1578
CLD-1786824848 Refs #1578
CLD-1786824881 Refs #1578
…o current state CLD-1786824937 Refs #1578
…nother file type CLD-1786825436 Refs #1578
CLD-1786825522 Refs #1578
CLD-1786825552 Refs #1578
CLD-1786827335 Refs #1578
CLD-1786827787 Retire AG-GH-8 (Rule-Ref: AG-WF-016 stub) and split its three distinct concerns into focused rules: AG-GH-23 (what metadata is required), AG-GH-24 (where it comes from), AG-GH-25 (when it must be set and how it's enforced). Drops the redundant Known Gaps mechanism paragraph in favor of the Rule Enforcement Matrix rows plus scripts/check-pr-tracking- metadata.sh's own comments, which already document the fork-PR and secret-failure-mode nuance in full. Refs #1578
…024/025 CLD-1786827800 Refs #1578
CLD-1786827814 Refs #1578
…ocal Windows Docker CLD-1786828241 AG-VAL-016 already made the build-tools container the only valid verification path but did not say where that container must run. Makes explicit that a Windows authoring host (even with Docker Desktop installed and apparently working) is not a substitute for SSH against a real Linux self-hosted runner host -- grounded in AG-IPV6-001's already- documented Docker-Desktop-on-Windows divergence. Refs #1578
… instead of duplicating it CLD-1786828283 Refs #1578
…ot a coordinator
CLD-1786859037
A coordinating agent could previously grant its own new-file ACK on the
maintainer's behalf ('maintainer/coordinator ACK'). Closes that loophole:
only the maintainer's explicit ACK lifts the new-file DISACK now.
Refs #1578
…ile ACK regardless of circumstance CLD-1786859140 Refs #1578
…ainer-only ACK CLD-1786859163 Refs #1578
djdomi
added a commit
that referenced
this pull request
Aug 19, 2026
PR #1583 (not yet merged) is trimming AGENTS.md's narrative-heavy rule prose repo-wide; writing new prose in that same narrative style would just be more work for that trim later. Compresses the incident retelling to a two-sentence pointer at issues #815/#1095, matching the target pattern -- normative content stays in the Rule Enforcement Matrix row. CLD-1787166227 From: Issue #1599
djdomi
changed the base branch from
current_dev
to
fix/1598-build-tools-cve-sweep
August 20, 2026 04:47
5 tasks
djdomi
force-pushed
the
fix/1598-build-tools-cve-sweep
branch
from
August 20, 2026 09:33
d17781e to
fed0be7
Compare
djdomi
force-pushed
the
fix/1598-build-tools-cve-sweep
branch
4 times, most recently
from
August 20, 2026 15:39
494aabc to
d92d507
Compare
66 tasks
djdomi
commented
Aug 22, 2026
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
djdomi
added a commit
that referenced
this pull request
Aug 22, 2026
… 3 lines / <=80 chars What: trims the What/Why/From comment blocks this PR itself introduced (the one full-detail copy per step type, on detect-changes' occurrence of each of the three new steps -- all other 30 sites already carry no comment) from 5-6 lines down to exactly 3 lines each, all <=80 chars, with no loss of the What/Why/From substance itself. Why: maintainer feedback relayed via the coordinator during this PR's own review cycle, citing build-push.yml as a named example of comment blocks growing without a length ceiling, contributing to the file's own AG-CI-021 size guard margin being fragile. Scoped to only this PR's own new comment blocks, not the rest of the file's pre-existing comments -- a much larger sweep was proposed separately and is intentionally NOT part of this commit pending direct confirmation, since the specific 3-line/80-char ceiling cited is not yet present in AG-CODE-012 on origin/current_dev as of this commit (current text: 5-line ceiling, Why: 1-3 lines) and the PR proposing that tightening (#1583) is itself still a draft explicitly marked not-yet-ready. Verified: scripts/untracked/check-workflow-line-limit.sh still passes (8759/8999 lines, 510777/512000 bytes); bash -n still passes on all 219 run: blocks; the 31/31/31 structural placement check still passes; a targeted awk scan confirms none of this PR's own three comment blocks exceed 80 characters (the only >80-char "# What/Why/From:" lines remaining in the file are pre-existing, not touched by this commit). From: Issue #1095 | PR #1645
This was referenced Aug 22, 2026
djdomi
added a commit
that referenced
this pull request
Aug 22, 2026
… 3 lines / <=80 chars What: trims the What/Why/From comment blocks this PR itself introduced (the one full-detail copy per step type, on detect-changes' occurrence of each of the three new steps -- all other 30 sites already carry no comment) from 5-6 lines down to exactly 3 lines each, all <=80 chars, with no loss of the What/Why/From substance itself. Why: maintainer feedback relayed via the coordinator during this PR's own review cycle, citing build-push.yml as a named example of comment blocks growing without a length ceiling, contributing to the file's own AG-CI-021 size guard margin being fragile. Scoped to only this PR's own new comment blocks, not the rest of the file's pre-existing comments -- a much larger sweep was proposed separately and is intentionally NOT part of this commit pending direct confirmation, since the specific 3-line/80-char ceiling cited is not yet present in AG-CODE-012 on origin/current_dev as of this commit (current text: 5-line ceiling, Why: 1-3 lines) and the PR proposing that tightening (#1583) is itself still a draft explicitly marked not-yet-ready. Verified: scripts/untracked/check-workflow-line-limit.sh still passes (8759/8999 lines, 510777/512000 bytes); bash -n still passes on all 219 run: blocks; the 31/31/31 structural placement check still passes; a targeted awk scan confirms none of this PR's own three comment blocks exceed 80 characters (the only >80-char "# What/Why/From:" lines remaining in the file are pre-existing, not touched by this commit). From: Issue #1095 | PR #1645
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.
CLD-1786825000
Summary
Trims
AGENTS.md's own narrative-heavy rule prose to the "sober" standard already applied to code comments (AG-CODE-012), and separately adoptsAG-VAL-033and closes a realAG-REL-001gap found along the way.Linked Issues
Refs #1578. This is a governance-doc change (
Rule-Ref: AG-CI-020's own trailing paragraph): stays open withRefs, neverCloses, until confirmed live onmaster.What This Actually Changes
Before: many rules (especially in
Agent Workflow,Required Validation,Coding Patterns) carried a 100-300+ word inline incident retelling after their normative text -- the actualmust/must not/scope/exception was buried inside the story of how the rule was discovered. After: the normative text is unchanged in substance; each incident retelling is compressed to a one-sentenceBad Example:citation pointing at the real PR/issue where the full detail still lives. Nothing normative was narrowed -- everymust/must not, scope, exception, rule ID, andRule-Ref:cross-reference survives; several bare mid-sentence references were upgraded to the requiredRule-Ref:form as a side effect.What This PR Fixes / Adds
Agent Workflow,Required Validation(CI/VAL families),Issue And PR Tracking, and theKnown Gapsnotes.AG-VAL-033as binding (removes "proposed, not yet adopted" from the rule text and its Rule Enforcement Matrix row) -- explicit maintainer ACK, recorded on issue release-validation-plan Part B: needs re-validation & extension entirely for upcoming release (as a living document) #1391.AG-REL-001to cover a language hidden inside a file declared as another type (e.g. Python committed inline inside a.sh/bash-shebang script) -- two confirmed real instances (scripts/check-pr-tracking-metadata.sh,scripts/dhcp-kea-lease-flow-simulation.sh), finding recorded on issue ci: rework of the entire CI infrastructure (rebuild/scan/promote pipeline, workflow consolidation, runner stabilization) #1095; the two scripts themselves are not rewritten here (separate scoped decision).What Changed In Code
AGENTS.mdonly -- 30 commits, one per rule/decision (explicit maintainer request for this refactor specifically, so every intermediate state stays independently revertable). No other file touched.Why This Matters For Users / Operators
No runtime/operator-visible change. This is the project's own AI-agent governance document -- easier for a human or an agent to actually read and follow when the regulatory text isn't buried in a paragraph of incident narrative.
Scope Boundaries
Does not touch
AG-WF-026,AG-WF-033,AG-KD-003, orAG-GH-018-- reviewed and found to be either purely normative (no separable incident tail) or dense technical specification (byte thresholds, CVE/version tables) where trimming would cost real content, not prose. Does not rewrite the two scripts found under the newAG-REL-001clause (tracked on issue #1095 instead).Risk / Rollback / Follow-up
No behavioral risk -- documentation-only. Rollback: revert any single commit (or the whole branch) independently; each rule's trim is its own commit. Follow-up: maintainer review/reconciliation of all 30 commits against the original text (in progress); the two Python-in-bash scripts flagged under
AG-REL-001remain unfixed pending a separate scoping decision.Local Scope Evidence
Validation
No CI-relevant file touched; standard governance-content checks (
file-headers,check-governance-guards.sh) apply automatically viabuild-push.ymlon this PR.Type of change
Changelog
Internal governance-document cleanup; no user-facing/operational change.