@amsterdamdatalabs/adl-agent-control-linux-x64 0.1.30 → 0.1.33

package/packages/repo-controls/assets/promote.ts

@@ -1,52 +1,8 @@
-// Managed by adl-repo-controls — do not edit.
-// Regenerate with: adl-repo-controls install --repo .
-//
-// Vendored into `.workflows/` byte-for-byte so CI depends on nothing: no
-// adl-repo-controls on PATH, no MCP client, no package install. A pipeline
-// agent is a cold environment, and a promotion that needs a global npm binary
-// fails there for reasons that have nothing to do with the promotion.
-//
-// Byte-identical in every repository, deliberately. Refs come from the
-// environment, never baked in — otherwise each consumer's copy would hash
-// differently and one published hash could not verify any of them.
+// Managed by adl-repo-controls, do not edit; regenerate with: adl-repo-controls install --repo . (README "Managed workflow scripts").
 
-/**
- * Promote one branch to another through an Azure DevOps pull request.
- *
- * Standard, not repo-local: every repository in this estate is on Azure DevOps,
- * and promoting a branch to its trunk is find-or-reuse a PR, then set
- * auto-complete. Ported from enact-m5's `workflows/scripts/release/
- * promote-main.ts`, where the mechanism was already injectable — fetch,
- * collection, project, repository and token were all parameters — and only
- * three module-scoped literals made it that repository's:
- *
- *     SOURCE_REF = 'refs/heads/integration'
- *     TARGET_REF = 'refs/heads/main'
- *     title      = 'release: promote integration to main'
- *
- * The refs are declared as `[controls.release].source` / `.target`. The title is
- * DERIVED from them rather than being a third key: a title that can disagree
- * with the refs it describes is a bug waiting for someone to change one and
- * forget the other, and the derived form satisfies this package's own
- * commit-msg grammar for any pair.
- *
- * The target branch's gate is Tarun's approval alone (Tarun, 2026-09-30): the
- * promotion PR gets NO build validation and CD runs after the merge into the
- * target. The pre-flight proves the minimum-reviewer policy (>=1 approver,
- * resetOnSourcePush=true) and does not require a build policy.
- *
- * There is no default pair. Defaulting to integration -> main would put one
- * repository's branch names back into the package by the back door.
- */
+/** Promote one branch to another through an Azure DevOps pull request; see README "Managed workflow scripts". */
 
-/**
- * Azure DevOps' `GitPullRequestCompletionOptions.mergeStrategy`, by name.
- * The REST API's wire values are the camelCase strings below (confirmed
- * against a live PR: sending the numeric `GitPullRequestMergeStrategy` enum
- * ordinal here is silently accepted by the type system but is not what the
- * API expects — PR 1477, 2026-09-27, armed auto-complete with `rebase`
- * although "no-fast-forward" was intended). `squash` is the standard.
- */
+/** Azure DevOps' `mergeStrategy` by name; see README "Managed workflow scripts". */
 export const MERGE_STRATEGIES = {
   squash: 'squash',
   rebase: 'rebase',
@@ -68,12 +24,7 @@ export interface PromotionRequest {
   /** Declared branch names, WITHOUT the `refs/heads/` prefix. */
   source?: string
   target?: string
-  /**
-   * Azure's `GitPullRequestMergeStrategy`. Defaults to the standard the MCP
-   * server defines -- its PR tool admits `enum: ['Squash']` and nothing else.
-   * A repository wanting something else declares it, so the deviation is
-   * visible instead of welded into this file.
-   */
+  /** Azure's `GitPullRequestMergeStrategy`; see README "Managed workflow scripts". */
   mergeStrategy?: MergeStrategy
 }
 
@@ -192,26 +143,7 @@ export interface PromotionPolicyReceipts {
   build: PolicyConfiguration | null
 }
 
-/**
- * The one policy contract used by both promotion and doctor. A configuration
- * only counts when it is enabled, blocking, and scoped exactly to the target
- * branch; a project-wide or path-filtered lookalike cannot guard a promotion.
- *
- * The target's gate is the minimum-reviewer policy ONLY (Tarun, 2026-09-30):
- * the integration -> main promotion PR gets no build validation, Tarun's
- * approval is the only gate, and CD runs after the merge into main. Promotion
- * therefore never requires a build policy. `build` is still reported so a
- * caller can show one that happens to be present, but nothing here demands it.
- *
- * No named-reviewer policy is checked here, deliberately (Tarun,
- * 2026-09-27): the two-branch standard's `main` gate is "exactly one human
- * reviewer, author's vote excluded" via the minimum-reviewer policy below —
- * never a specific named individual. A required-reviewer-by-identity policy
- * on `main` was PR 1477's second live bug: it named the person who pushed to
- * `integration` as a mandatory approver, which both self-approves (that
- * person is usually the change's author) and contradicts "agent-reviewer is
- * optional, never required".
- */
+/** The one policy contract used by promotion and doctor (see README "Managed workflow scripts"). */
 export function promotionPolicyReceipts(
   policies: readonly PolicyConfiguration[],
   { repositoryId, targetRef }: PromotionPolicyRequirement,
@@ -326,11 +258,7 @@ export async function ensurePromotionPullRequest({
     status = 'created'
   }
 
-  // No reviewer is named here, deliberately (Tarun, 2026-09-27): naming one —
-  // typically the person who pushed to `integration` — is a self-approval
-  // risk and contradicts "agent-reviewer is optional, never required". The
-  // gate is the target branch's own minimum-reviewer policy (verified above),
-  // which excludes the author's own vote.
+  // No reviewer is named: see README "Managed workflow scripts".
   await azureRequest(fetchImpl, `${repositoryUrl}/pullrequests/${pullRequest.pullRequestId}?api-version=7.1`, authToken, {
     method: 'PATCH',
     body: JSON.stringify({
@@ -347,13 +275,7 @@ export async function ensurePromotionPullRequest({
 }
 
 
-/**
- * Standalone entry point. Reads the refs from the ENVIRONMENT, not from config:
- * this file is vendored into `.workflows/` byte-for-byte, so its content must
- * be identical in every repository or a single published hash cannot verify
- * any of them. The pipeline supplies the repository-specific values through
- * environment variables while the managed implementation stays identical.
- */
+/** Standalone entry point; refs come from the environment (see README "Managed workflow scripts"). */
 export async function main(env: Record<string, string | undefined> = process.env): Promise<void> {
   const result = await ensurePromotionPullRequest({
     collectionUri: env.AZURE_DEVOPS_COLLECTION_URI,

package/packages/repo-controls/assets/reconcile-guard.sh

@@ -1,20 +1,7 @@
 #!/usr/bin/env bash
 set -euo pipefail
 
-# Stage 1 of the CI pipeline for pull requests into `integration` (stage 2
-# runs the tests). It forces the PR author, usually an agent, to reconcile with
-# integration before anything merges:
-#
-#   the PR source branch contains integration's tip
-#
-# That is the only check. The version bump is not a PR concern any more: the
-# integration-merge pipeline bumps after the merge (Tarun, 2026-10-01).
-#
-# Read-only: this script only fetches and reads. It never pushes, and the only
-# refs it writes are the two remote-tracking refs it fetches.
-
-# CI never carries an agent identity. Never set one here, and never inherit
-# one from the caller.
+# Stage 1 PR guard; see README "Managed workflow scripts".
 unset ADL_AGENT_ID_AGENT
 
 die() {

package/packages/repo-controls/assets/scaffold/docs/AGENTS.md

@@ -0,0 +1,25 @@
+# docs/ — what belongs here
+
+Reference documentation for this repository: how it works and why it is shaped
+the way it is.
+
+## Layout
+
+- Standing reference pages live directly under this directory, one topic per
+  page.
+- Sub-directories group related pages (for example `decisions/` for
+  architecture decision records, `research/` for dated investigations). Add one
+  only when it has pages to hold.
+- `notes.md` is the repository's task ledger: one line when an agent starts a
+  task and one when it finishes.
+
+## Conventions
+
+- Every page carries YAML frontmatter with at least `type`, `title`,
+  `description`, `status` and `last_update` (ISO-8601 UTC,
+  `YYYY-MM-DDTHH:MM:SSZ`).
+- `notes.md` is append-only: newest line at the bottom, earlier lines are never
+  rewritten. Format `YYYY-MM-DD HH:MM <surface> <note>`, at most 100
+  characters per line.
+- A page that is catalogued in an index stays listed there; add the entry in
+  the same change that adds or renames the page.

package/packages/repo-controls/assets/scaffold/docs/CLAUDE.md

@@ -0,0 +1 @@
+@AGENTS.md

package/packages/repo-controls/assets/scaffold/docs/decisions/index.md

@@ -0,0 +1,17 @@
+---
+last_update: '2026-10-08T00:00:00Z'
+title: Architecture decision records
+description: The index of this repository's architecture decision records, one adr-<slug>.md page per decision.
+type: Reference
+status: stable
+sources: the repository's documentation conventions (decision records)
+---
+
+# Architecture decision records
+
+One page per decision, named `adr-<slug>.md`. Each carries an inline
+`**Status:**` line (OPEN, DECIDED or STABLE) and the backlinks that state owes.
+
+## Decisions
+
+None yet. List each new record here in the same change that adds it.

package/packages/repo-controls/assets/scaffold/docs/notes.md

@@ -0,0 +1,20 @@
+---
+last_update: '2026-10-08T00:00:00Z'
+title: Agent notes ledger
+description: One append-only ledger per repository for every agent, one line when you start a task and one when you finish it.
+type: Operations
+status: stable
+sources: the repository's agent rules (task ledger convention)
+---
+
+# Agent notes ledger
+
+A short, append-only log so anyone landing in the repository can see at a glance
+what every agent is doing. Every line is at most 100 characters, format
+`YYYY-MM-DD HH:MM <surface> <note>` (for example
+`2026-10-08 13:30 claude start: add retry to the uploader`). Agents append one
+line when they start a task and one when they finish it. The ledger is never
+edited or sorted; earlier lines are never rewritten, only appended to, newest
+at the bottom.
+
+## Lines

package/packages/repo-controls/assets/scaffold/plans/AGENTS.md

@@ -0,0 +1,28 @@
+# plans/ — what belongs here
+
+Work items: Features, and the PBIs/Bugs that hang under them. The work-item
+board is the only place status lives; the files here describe the work.
+
+## Layout
+
+- `plans/features/az<id>-<slug>/spec.md` — one Feature, one file, for its whole
+  life. Frontmatter: `type: feature`, `title`, `status` (the board state),
+  `epic:` (the parent Epic's board URL), `work_item:` (this Feature's own board
+  URL), `last_update`. The Feature's own `## Items` table is the one place it
+  may list its children.
+- `plans/features/az<id>-<slug>/items/az<item-id>-<slug>.md` — one PBI or Bug.
+  Frontmatter: `type: pbi` or `type: bug`, `title`, `status`, `feature:` (the
+  parent Feature's slug), `work_item:`, `last_update`.
+- `plans/GAPS-AND-FINDINGS.md` — a register of gaps found while planning or
+  building something else. A row is deleted, not marked done, once its linked
+  item closes.
+- `plans/LEDGER.md` — the plan-event ledger, a Markdown table, newest entry
+  first.
+
+## Conventions
+
+- The board is the only place status lives. A file's `status:` mirrors the
+  board state.
+- An item is allocated on the board first; the file is named `az<id>-<slug>`
+  only once that id exists. Files never move between directories.
+- `epic:` and `feature:` are authored by hand, never tool-generated.

package/packages/repo-controls/assets/scaffold/plans/CLAUDE.md

@@ -0,0 +1 @@
+@AGENTS.md

package/packages/repo-controls/assets/scaffold/plans/GAPS-AND-FINDINGS.md

@@ -0,0 +1,12 @@
+# Gaps and findings
+
+Anything found while planning or building that is not the work in hand. Each row
+becomes an item file with `item_type: bug`, parented under the same Feature as
+the plan it was found from, so the fix stays attached to the effort that
+surfaced it.
+
+Each row states how it was verified, because a finding nobody can re-check is a
+rumour. A row is deleted, not marked done, once it stops being a gap.
+
+| Found | Finding | From plan | Item file | Work item |
+| --- | --- | --- | --- | --- |

package/packages/repo-controls/assets/scaffold/plans/LEDGER.md

@@ -0,0 +1,8 @@
+# Ledger
+
+Plan events, newest first. Each row has a kebab-case unique `Id`, an ISO `Date`,
+an `Area`, a short `Event`, and `Refs` (repository-relative paths that exist).
+
+| Date | Id | Area | Event | Refs |
+| --- | --- | --- | --- | --- |
+| 2026-10-08 | plans-tree-bootstrapped | plans | Plans tree scaffolded by adl repo controls install | — |

package/packages/repo-controls/assets/scaffold/root/AGENTS.md

@@ -0,0 +1,22 @@
+# Agent entry point
+
+This is the first file a human or agent should read on arriving at this
+repository. Edit it to describe what this repository is; the sections below
+describe the layout the adl repo controls enforce.
+
+## Layout
+
+| Path | What lives there |
+| --- | --- |
+| `docs/` | reference documentation, see `docs/AGENTS.md` |
+| `plans/` | Features and the PBIs/Bugs under them, see `plans/AGENTS.md` |
+| `workflows/` | CI pipelines and build/release scripts, see `workflows/AGENTS.md` |
+| `.workflows/` | managed hook stubs and lock, rebuilt by `adl repo controls install`; never hand-edit |
+
+## Rules
+
+- This repository is graded by `adl-compliance` on every commit; the enabled
+  gates are `[controls.compliance].enabled` in `adl-config.toml`. A failing
+  gate is fixed, not skipped.
+- `INVARIANTS.md` lists what this repository must never regress.
+- Work-item status lives on the board, never in a file.

package/packages/repo-controls/assets/scaffold/root/CLAUDE.md

@@ -0,0 +1 @@
+@AGENTS.md

package/packages/repo-controls/assets/scaffold/workflows/AGENTS.md

@@ -0,0 +1,16 @@
+# workflows/ — what belongs here
+
+The CI tree: pipeline definitions and the scripts they run.
+
+## Layout
+
+- `workflows/pipelines/` — pipeline definitions and their shared templates.
+- `workflows/scripts/` — the scripts the pipelines invoke, grouped in
+  sub-directories by purpose (for example `build/`, `release/`).
+
+## Conventions
+
+- A script here is invoked by a pipeline, never by a git hook.
+- Keep each scripts directory small; split by purpose before it grows past a
+  screenful of files.
+- A pipeline and the scripts it references must resolve: move them together.

package/packages/repo-controls/assets/scaffold/workflows/CLAUDE.md

@@ -0,0 +1 @@
+@AGENTS.md

package/packages/repo-controls/assets/version-bump.sh

@@ -1,26 +1,8 @@
 #!/usr/bin/env bash
 set -euo pipefail
 
-# STAGE 1 of the promote pipeline (push to `integration`): the integration-merge
-# build owns package version allocation (Tarun, 2026-10-01 -- a PR's
-# build-validation policy ignores `[skip ci]`, so a bump pushed from PR CI
-# re-queued itself; a push to a branch honours it). After a merge lands on
-# `integration` this sets the manifest to that commit's version + patch 1:
-#
-#   version-bump.sh --file package.json --integration --push
-#
-# The Azure Pipelines build checks out the detached commit that triggered the
-# run with persisted credentials, so `git push` authenticates as the project
-# build service (which needs Contribute + "Bypass policies when pushing" on
-# `integration`). The bump commit is created on that checkout, carries
-# `[skip ci]` so the push does not trigger this pipeline again, and is pushed
-# with a plain fast-forward -- never forced. If integration moved since the
-# checkout the push is rejected and the script fails loud; the newer merge's
-# own run bumps. No npm query, no PR.
-
-# CI never carries an agent identity: the push below authenticates as the
-# project build service through the checkout's persisted System.AccessToken.
-# Never set an agent identity here, and never inherit one from the caller.
+# Rationale: packages/repo-controls/README.md, "Managed workflow scripts", version-bump.sh.
+
 unset ADL_AGENT_ID_AGENT
 
 die() {
@@ -82,13 +64,6 @@ node -e '
   fs.writeFileSync(file, `${JSON.stringify(manifest, null, 2)}\n`)
 ' "$version_file" "$next_version"
 
-# `[controls.release].pre_bump` (adl-config.toml, repo root): ordered,
-# repository-relative scripts a multi-language repo runs before the bump
-# commit — e.g. agent-identities updates a Go version constant nothing about
-# package.json can reach. No file, or no `pre_bump` key: no scripts, and
-# everything below this comment is a no-op, so the resulting commit is
-# byte-identical to the behaviour before this feature existed (see
-# packages/repo-controls/tests/version-bump-integration-pre-bump.test.ts).
 config_path="$repo_root/adl-config.toml"
 pre_bump_list=''
 if [[ -f "$config_path" ]]; then
@@ -129,31 +104,17 @@ if [[ -n "$pre_bump_list" ]]; then
 fi
 
 if [[ ${#pre_bump_scripts[@]} -gt 0 ]]; then
-  # Validated before any of them run, so a bad declaration fails clearly
-  # instead of leaving the repo half-way through a partial run.
   for script in "${pre_bump_scripts[@]}"; do
     [[ -f "$repo_root/$script" ]] || die "pre_bump script not found: $script"
   done
 
-  # Every var whose name ends _TOKEN/_PAT/_SECRET/_PASSWORD, plus the two
-  # Azure DevOps credentials by their exact names (SYSTEM_ACCESSTOKEN does
-  # not end in "_TOKEN"), is stripped from each script's environment. A
-  # pre_bump script is repo-authored, unreviewed by this package, and has no
-  # business ever seeing the pipeline's push/PR credentials.
   unset_flags=(-u SYSTEM_ACCESSTOKEN -u AZURE_DEVOPS_EXT_PAT -u AZURE_DEVOPS_TOKEN -u AZURE_DEVOPS_PAT)
   while IFS= read -r var_name; do
-    unset_flags+=(-u "$var_name")
-  done < <(compgen -v | grep -Ei '_(TOKEN|PAT|SECRET|PASSWORD)$' || true)
-
-  # A pre_bump script that edits `.git` directly (hooks, config, refs) would
-  # never show up in `git status` — `.git` sits outside the working tree that
-  # diffs against — so this is a separate, explicit check. There is no
-  # equivalent check for a script writing to an absolute path OUTSIDE the
-  # repository entirely: a plain shell script has no sandbox to enforce
-  # that, so this refuses `.git` tampering only, honestly, rather than
-  # claiming a guarantee this script cannot keep. Changes INSIDE the repo
-  # tree are never "outside the repo" by construction: every add below is
-  # scoped to `$repo_root`, so nothing beyond it can ever be staged.
+    if [[ "$var_name" =~ _([Tt][Oo][Kk][Ee][Nn]|[Pp][Aa][Tt]|[Ss][Ee][Cc][Rr][Ee][Tt]|[Pp][Aa][Ss][Ss][Ww][Oo][Rr][Dd])$ ]]; then
+      unset_flags+=(-u "$var_name")
+    fi
+  done < <(compgen -v)
+
   git_marker="$(mktemp)"
   for script in "${pre_bump_scripts[@]}"; do
     if ! ( cd "$repo_root" && env "${unset_flags[@]}" \
@@ -172,8 +133,6 @@ fi
 
 git -C "$repo_root" add -A
 git diff --cached --quiet && die "version bump produced no staged change (expected at least $version_file)"
-# `[skip ci]` (Azure DevOps: a push whose commits contain it does not trigger CI
-# pipelines) keeps this push from re-running the promote pipeline that made it.
 git commit -m "chore: bump version $current_version to $next_version [skip ci]"
 if ! git push origin "HEAD:refs/heads/integration"; then
   die "push to integration rejected: integration moved since checkout, so this bump is stale; the next merge's run bumps"

package/packages/repo-controls/package/adl-compliance/AGENTS.md

@@ -98,15 +98,15 @@ the rest, so ast-grep's next release does not fail a gate.
 
 ## The consumer's layout arrives
 
-A row names a logical tree; `policy/trees.toml` says where it currently lives.
+A row names a logical tree; the consumer's `[controls.compliance.trees]` says where it lives (`policy/config.toml` ships no defaults).
 
 ```yaml
 scope:
-  - <rust>/crates/**/src/*.rs        # backend/crates/**/src/*.rs
-  - <compliance>/policy/inputs/rust-policy.json
+  - <docs>/guides/**/*.md            # documentation/guides/**/*.md
+  - <plans>/features/**/spec.md
 ```
 
-253 of the registry's 325 scope entries are placeholders, and named-input
+Most of the registry's scope entries are placeholders, and named-input
 defaults and `grants:` paths resolve through the same table — so no consumer path
 is written in this package's rows, and moving a tree is one line. `<name>`, not
 `{name}`: braces are already glob alternation and eleven rows use it. An unknown
@@ -125,8 +125,8 @@ never enter a set and no row needs to exclude `node_modules/`.
 ## Running
 
 ```bash
-uv run adl-compliance rust.acp-boundary
-uv run adl-compliance RST-001 --files changed.list
+uv run adl-compliance layout.references
+uv run adl-compliance DOC-001 --files changed.list
 uv run adl-compliance                      # every row
 ```
 
@@ -150,7 +150,7 @@ it. `tests/core/` is the one exception, for the spine (`Check`, `scope`,
 
 ## Status
 
-Every row of the registry is implemented — 28 of 28, counted by importing
+Every row of the registry is implemented — 29 of 29, counted by importing
 `adl_compliance.checks` and measuring `len(CHECKS)` (`checks/__init__.py`'s
 explicit registry tuple), not by re-reading this paragraph. The shell
 `compliance_new/` tree this package ported from is gone, not frozen: a row
@@ -160,3 +160,21 @@ never a silent pass, and today no row reaches that.
 [`docs/operations/adl-compliance-invariants.md`](../../../../docs/operations/adl-compliance-invariants.md)
 records what is not true yet, including two rows that do not
 trigger on their own named inputs and one whose register does not exist.
+
+## Rationale moved out of code comments (Bug 602)
+
+- A check that subscripts an input dropped because its tree is declared `""`
+  (`[controls.compliance.trees] <tree> = ""`) is could-not-run, never clean: a
+  clean verdict would read as a pass for a gate that graded nothing (Bug 597).
+  Checks that can honestly narrow (LAY-006/008/013, DOC-002) guard the read.
+  Any other `KeyError` is a plain crash, reported as that row's could-not-run so
+  it cannot erase the other rows' verdicts.
+- A widening input (a register of grants) whose tree is unknown is "no register",
+  never an error: its absence can only grade stricter (PBI 599).
+- Central root trees are only adl's own or language-neutral ones (`compliance`,
+  `workflows`, `bin`, `packages`, `scripts`, `src`, `tests`); any other layout is
+  declared under `[controls.compliance.root] dirs` (PBI 601).
+- `.workflows/` is deliberately not in the root-Markdown guide list: it is
+  machine-managed, written wholesale by `adl-repo-controls install`.
+- `markdown_trees` root names come from `[controls.compliance.root] files` and
+  match exactly; a glob is refused by `declared_root_files`.

package/packages/repo-controls/package/adl-compliance/src/adl_compliance/checks/__init__.py

@@ -36,16 +36,16 @@ from .layout.root_closed_set import RootClosedSet
 from .layout.root_markdown_allowlist import RootMarkdownAllowlist
 from .layout.scripts_size_depth import ScriptsSizeDepth
 from .lfs.integrity import Integrity
-from .pipeline.phase_disjoint import PhaseDisjoint
-from .repository.banned_commands import BannedCommands
 from .repository.ignored_paths import IgnoredPaths
+from .repository.legacy_search import LegacySearch
 from .repository.license_declared import LicenseDeclared
 from .repository.lockfile_integrity import LockfileIntegrity
+from .repository.no_multiline_comments import NoMultilineComments
+from .repository.vcs_in_scripts import VcsInScripts
 
 CHECKS: tuple[type[Check], ...] = (
     AdrLifecycle,
     AgentsLayout,
-    BannedCommands,
     CiPaths,
     DirectoryRatchet,
     DocsClosedSet,
@@ -59,18 +59,20 @@ CHECKS: tuple[type[Check], ...] = (
     Indexes,
     Integrity,
     LicenseDeclared,
+    LegacySearch,
     LockfileIntegrity,
     MarkdownAst,
     MarkdownTrees,
+    NoMultilineComments,
     OkfProfile,
     OpenWorkCap,
-    PhaseDisjoint,
     Placement,
     PlansLayout,
     References,
     RootClosedSet,
     RootMarkdownAllowlist,
     ScriptsSizeDepth,
+    VcsInScripts,
 )
 
 _BY_ID: dict[str, type[Check]] = {check.id: check for check in CHECKS}

package/packages/repo-controls/package/adl-compliance/src/adl_compliance/checks/docs/adr_lifecycle/check.py

@@ -7,7 +7,7 @@ owes a different set of backlinks.
               docs/architecture/decisions/ entirely would pass in silence.
   graded      the ADRs, which are the given set.
 
-BACKLINK TARGETS ARE RESOLVED, NOT GRADED. `.specs/`, `.plans/` and
+BACKLINK TARGETS ARE RESOLVED, NOT GRADED. `.plans/` and
 `docs/architecture/` references are read from disk even though the row's scope
 excludes them. That is not a second discovery pass: the set says which ADRs are
 graded, and whether an ADR's own link resolves is a property OF that ADR.

package/packages/repo-controls/package/adl-compliance/src/adl_compliance/checks/docs/adr_lifecycle/test_check.py

@@ -54,7 +54,7 @@ def test_a_linked_plan_is_no_longer_graded_on_the_directory_it_sits_in() -> None
     So whether a linked plan is active is no longer answerable from disk, and this
     gate does not try. What remains is the backlink itself, asserted below. The rule
     survived the tree's deletion by eighteen months of nobody writing a DECIDED ADR —
-    DOC-001 was armed and green on enact-m5 the whole time."""
+    DOC-001 was armed and green on a managed repository the whole time."""
     verdict = verdict_for("DOC-001", CORPORA / "adr-lifecycle-inactive-plan")
     assert "requires a linked active plan" not in verdict.render()
 

package/packages/repo-controls/package/adl-compliance/src/adl_compliance/checks/docs/english_only/check.py

@@ -35,12 +35,10 @@ One finding per (path, line, kind), not per matched character or codepoint —
 the matched value (a two-character Han word on one line is one finding, not
 two).
 
-The row's `engine.scope` (`policy/gate-registry.yaml`, `DOC-002`) excludes
-four specific frontend fixture files — SCOPE, decided by the row, not by this
-check. `scan_excluded`'s three rules below are a different thing: SUBJECT-MATTER
+The row's `engine.scope` (`policy/gate-registry.yaml`, `DOC-002`) decides
+SCOPE, not this check. `scan_excluded`'s rules below are a different thing: SUBJECT-MATTER
 exclusions this gate owns, because they say what kind of content Han text is
-allowed to be (hidden paths, the one named i18n directory, any locale-named
-data directory), not where in the tree it lives.
+allowed to be (hidden paths, any locale-named data directory), not where in the tree it lives.
 """
 
 from __future__ import annotations
@@ -124,19 +122,6 @@ class DocsEnglishOnly(Check):
     and `.../i18n/locales/<locale>/...` — where non-English text is the point,
     not a defect. Mirrors check.sh's `scan_excluded` rule 3."""
 
-    inputs: ClassVar[dict[str, str]] = {"frontend_src": "<frontend>"}
-    """FIXED 2026-09-16 (K-42 sweep, LOUD form, approved): `I18N_OWNER` was a
-    hardcoded `frontend/mobile/src/i18n` literal, matched against the given
-    set with `==`/`startswith` inside `_excluded` -- a rule 2 EXEMPTION, not a
-    filter over what gets scanned. A repository whose frontend root is not the
-    packaged default had its real i18n directory fail this match, so its
-    genuinely-translated strings were no longer exempt -- every one of them
-    became a false "raw Han text" finding. LOUD, not silent: the wrong path
-    does not go quiet, it makes real translated content look like a defect.
-    `mobile/src/i18n` stays literal below the resolved root: the settled
-    platform path, not a resolvable one, the same call TS-001's `MOBILE_SRC`
-    fix already made."""
-
     FIX_BY_KIND: ClassVar[dict[str, str]] = {
         "Han Unicode escape": "replace the \\u/\\U escape with the equivalent English text",
         "raw Han text": "translate this Han-script text into English",
@@ -172,15 +157,14 @@ class DocsEnglishOnly(Check):
         # it still exists on disk — check.sh's ALL_RELPATHS is filled before
         # its own `[ -f "$rel" ]` guard, because a Han PATH is the finding
         # there, distinct from Han CONTENT, which a deleted file no longer has.
-        i18n_owner = self._i18n_owner(ctx)
         for relative in files:
-            if self._excluded(relative, i18n_owner):
+            if self._excluded(relative):
                 continue
             if self.HAN_PATTERN.search(relative):
                 yield self._finding(relative, "Han filename")
 
         for relative in files.existing(ctx.root):
-            if self._excluded(relative, i18n_owner):
+            if self._excluded(relative):
                 continue
             suffix = self._path_suffix(relative).lower()
             if suffix in self.OFFICE_SUFFIXES:
@@ -190,30 +174,11 @@ class DocsEnglishOnly(Check):
 
     # ------------------------------------------------------ subject-matter scope
 
-    def _i18n_owner(self, ctx: Context) -> str | None:
-        # Decision for a tree declared absent (`frontend = ""`, which drops
-        # `frontend_src` from the resolved inputs): this input only contributes
-        # the i18n OWNER exemption, an extra path that excuses translated strings
-        # beneath it. A repository with no frontend tree has no such directory, so
-        # there is no exemption to grant -- Han text anywhere is graded by the rule
-        # as written, and the generic locale-directory exemption below still
-        # applies. This read `ctx.inputs['frontend_src']` unguarded -- a `KeyError`
-        # traceback (exit 1), not a verdict, on any file.
-        frontend_src = ctx.inputs.get("frontend_src")
-        if frontend_src is None:
-            return None
-        return f"{ctx.relative(frontend_src)}/mobile/src/i18n"
-
-    def _excluded(self, relative: str, i18n_owner: str | None) -> bool:
+    def _excluded(self, relative: str) -> bool:
         # 1. Hidden paths, by decision. Every component is tested.
         if any(part.startswith(".") for part in relative.split("/")):
             return True
-        # 2. The one named i18n owner exemption (absent when the frontend tree is).
-        if i18n_owner is not None and (
-            relative == i18n_owner or relative.startswith(i18n_owner + "/")
-        ):
-            return True
-        # 3. Any locale-named data directory, anywhere.
+        # 2. Any locale-named data directory, anywhere.
         if self.LOCALE_DIR.search(relative):
             return True
         return False

package/packages/repo-controls/package/adl-compliance/src/adl_compliance/checks/docs/english_only/fixtures/excluded/web/i18n/locales/zh-CN/strings.ts

@@ -0,0 +1 @@
+export const strings = { greeting: "你好" };