Repository navigation
chore(norms): rename docs/agents to docs/norms - #70
Merged
Merged
Conversation
Move the loop norms directory to docs/norms and update every live reference: AGENTS.md, the moved ops.md, skills/triage/SKILL.md, bump.config.ts and the scripts/loop host strings. CHANGELOG.md and the state/ run history keep the old path on purpose (falsifying them would rewrite the record). Closes #69
Contributor
Author
Coverage
|
Contributor
Author
|
Loop pr-review — approve ✅ Independent check of
Gates re-run from this checkout: No L1/L2/L3 problems under either lens. As a norms-layer proposal this needs your approving review and merge; the loop does not merge its own work. |
This was referenced Sep 21, 2026
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.
Closes #69
loop-task: #69
Why
Issue #69 asks to move the loop norms directory
docs/agents/todocs/norms/. The title states source and target unambiguously; triage (r-20260920-162608-erpg) inventoried the reference set and classified itfeature/ready-for-agent.What
git mv docs/agents docs/norms(five files:domain.md,issue-tracker.md,ops.md,release.md,triage-labels.md) and every live reference updated:AGENTS.mddocs/agents/and the fivedocs/agents/*.mdlinks)docs/norms/ops.mdskills/triage/SKILL.mdbump.config.tsscripts/loop/run.mjsscripts/loop/shared/agent.mjsscripts/loop/shared/route.mjsscripts/loop/shared/state.mjsDiffstat: 12 files changed, 15 insertions(+), 15 deletions(-) — exactly the live occurrences triage found. Relative links inside the moved files (
triage-labels.md,release.md,docs/adr/) need no change.Deliberately not changed
CHANGELOG.md:20mentionsdocs/agentsonly as history of commite3c4cd6; it is changelogen-generated and rewriting it would falsify the record.state/reports/**andstate/tasks/**are run history, not repo content.No source, signer, dependency, test or
.github/workflows/**file is touched, so the signer oracles and tree-shaking are unaffected.Verification
pnpm lint— 0 warnings / 0 errors.pnpm fmt:check— all files formatted.pnpm build— exit 0;pnpm check:types— exit 0.pnpm test:ci— Azure and TOS signature oracles all passed; browser suite 24 files passed, 255 passed / 26 skipped.docs/agentssearch over tracked content after the change — only the historicalCHANGELOG.md:20hit remains.node --checkon the four edited.mjshost files — all OK.Review
Two-lens review (correctness/regression and standards/safety) found no L1/L2 problems. Commit type
chore(norms)per AGENTS.md, so this must not appear inCHANGELOG.md. This is a norms-layer change and therefore a proposal PR: the owner's approving review and merge are the checker; the loop does not merge its own work.