Rename docs/agents to docs/norms #69

Activity

1. github-actions commented on Sep 20, 2026

   

   github-actionsBot

   on Sep 20, 2026 – with GitHub Actions

   Contributor

   More actions

   Loop triage — feature / ready-for-agent (confidence: high)

   The request is a mechanical move: git mv docs/agents docs/norms plus every live reference. Inventoried the repo (excluding runtime history in state/ and the generated CHANGELOG.md):

   File	Lines
   AGENTS.md	32, 43, 48, 51, 54, 57, 65
   docs/agents/ops.md	64
   skills/triage/SKILL.md	18
   bump.config.ts	16
   scripts/loop/run.mjs	186
   scripts/loop/shared/agent.mjs	34, 123
   scripts/loop/shared/route.mjs	4
   scripts/loop/shared/state.mjs	8

   docs/agents/ holds five files (domain.md, issue-tracker.md, ops.md, release.md, triage-labels.md) and docs/norms/ does not exist. Relative links inside the moved files (e.g. triage-labels.md, release.md) need no change.

   Three things stay as they are:

   • CHANGELOG.md:20 mentions docs/agents only as history of commit e3c4cd6; it is changelogen-generated and rewriting it would falsify the record.
   • state/reports/** and state/tasks/** are run history, not repo content.
   • The user-facing README.md / README_zh-CN.md never mention docs/agents.

   No .github/workflows/** file references docs/agents (ci.yml, loop.yml are clean), so the host can push the branch; nothing here needs a workflow change. The rename does touch scripts/loop/** prompt/output strings, which docs/agents/ops.md explicitly allows as a loop PR (the owner's review is the checker).

   Per AGENTS.md, this is a norms-layer change, so it lands as a proposal PR the loop opens and a human merges. The feature stage will do the move and the reference updates, committed as chore(norms) so it does not leak into CHANGELOG.md.

   Labelling ready-for-agent.
2. github-actions

   added

   ready-for-agentFully specified, an AFK agent may handle it unattendedFully specified, an AFK agent may handle it unattended

   ready-for-humanRequires a human: implementation, merge of a loop PR, or a release callRequires a human: implementation, merge of a loop PR, or a release call

   and removed

   ready-for-agentFully specified, an AFK agent may handle it unattendedFully specified, an AFK agent may handle it unattended

   on Sep 20, 2026
3. github-actions commented on Sep 20, 2026

   

   github-actionsBot

   on Sep 20, 2026 – with GitHub Actions

   Contributor

   More actions

   Loop feature — PR opened for review ✅

   git mv docs/agents docs/norms (5 files) plus every live reference updated: AGENTS.md (7), docs/norms/ops.md:64, skills/triage/SKILL.md:18, bump.config.ts:16, scripts/loop/run.mjs:186, scripts/loop/shared/agent.mjs:34,123, scripts/loop/shared/route.mjs:4, scripts/loop/shared/state.mjs:8 — 12 files, +15/−15.

   Left untouched on purpose: CHANGELOG.md:20 (changelogen history of commit e3c4cd6) and the state/ run history; rewriting them would falsify the record. Relative links inside the moved files need no change.

   Verification from the runner: pnpm lint 0 warnings/0 errors, pnpm fmt:check clean, pnpm build and pnpm check:types exit 0, Azure + TOS signature oracles pass, browser suite 24 files / 255 passed / 26 skipped. No source, signer, dependency or .github/workflows/** change.

   This is a norms-layer change, so it lands as a proposal PR: the owner's approving review and merge are the checker.
4. Alex1990

   added a commit that references this issue on Sep 21, 2026

   chore(norms): rename docs/agents to docs/norms

   ...

   This issue will close once commit 7909054 is merged into the 'main' branch.

   7909054
5. Alex1990

   closed this as completedin #70on Sep 21, 2026