diff --git a/AGENTS.md b/AGENTS.md index c44fa6b1..b7265b97 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -253,7 +253,7 @@ adr queue [--dir docs/adr] [--as-of YYYY-MM-DD] [--format auto|terminal|markdown explicit `terminal`, `markdown`, or `json` (QueueReport v1). Only a TTY ever gets the terminal view — under [ADR-0044](./docs/adr/0044-ratify-a-proposed-record-with-adr-accept-and-present-the-queue-for-terminals.md) - (**proposed**), following ADR-0033 — so piped output is unchanged. + (**accepted**), following ADR-0033 — so piped output is unchanged. Exit codes: `0` = report with no corpus error findings; `1` = report emitted (complete, to stdout) with one or more error-severity corpus findings; `2` = @@ -269,7 +269,7 @@ not change the exit code and do not fail the managed-issue Action. `adr accept --by ` ratifies a `proposed` record, under [ADR-0044](./docs/adr/0044-ratify-a-proposed-record-with-adr-accept-and-present-the-queue-for-terminals.md) -(**proposed**). It is the third writing command, after `new` and `migrate`. +(**accepted**). It is the third writing command, after `new` and `migrate`. - **It splices three fields and nothing else**: `status`, `provenance.ratifiedBy`, and `review.decidedAt`. A `yaml` round trip would @@ -495,7 +495,7 @@ Two boundaries are load-bearing: Both guards are repo-local scripts, not CLI surface: `adr graph --format json` already emits every node's `status` and every `supersedes` edge, and the public CLI is a semver commitment (ADR-0031) whose write surface is deliberately -small: `new`, `migrate`, and `accept` (ADR-0044, **proposed**). A public +small: `new`, `migrate`, and `accept` (ADR-0044, **accepted**). A public Markdown inventory formatter waits for adopter demand. ## Toolchain diff --git a/CHANGELOG.md b/CHANGELOG.md index c4cf928b..1bca1493 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -18,7 +18,7 @@ Until `1.0.0`, minor releases may include breaking changes `review.quorum`, or would not be valid. `--by` is required and never inferred. This is the third writing command, and no agent surface runs it ([ADR-0044](docs/adr/0044-ratify-a-proposed-record-with-adr-accept-and-present-the-queue-for-terminals.md), - proposed). + accepted). - **`adr queue` has a terminal view.** `--format` now defaults to `auto`: a TTY gets a width-aware list with SLA state, days to deadline, approvals, objections, and the next `adr accept` command or the reason acceptance is diff --git a/MANIFEST.md b/MANIFEST.md index 4148ebee..3f1b21a7 100644 --- a/MANIFEST.md +++ b/MANIFEST.md @@ -74,7 +74,7 @@ hand-written. There are 44 records, ids `0001`-`0044`, alongside -`0000-template.md`: 41 accepted, 1 proposed, 2 superseded. +`0000-template.md`: 42 accepted, 2 superseded. | Id | Status | Title | | --- | --- | --- | @@ -121,6 +121,6 @@ There are 44 records, ids `0001`-`0044`, alongside | `0041` | accepted | Regenerate committed artifacts on Dependabot pull requests with default-branch scripts behind a maintainer label | | `0042` | accepted | Count a gate-change acknowledgment only when an admin or maintainer applied it | | `0043` | accepted | Publish schema v0.2.0 with RFC 3339 seconds, retain v0.1.0, and validate every record against the current schema | -| `0044` | proposed | Ratify a proposed record with adr accept and present the queue for terminals | +| `0044` | accepted | Ratify a proposed record with adr accept and present the queue for terminals | diff --git a/docs/adr/0044-ratify-a-proposed-record-with-adr-accept-and-present-the-queue-for-terminals.md b/docs/adr/0044-ratify-a-proposed-record-with-adr-accept-and-present-the-queue-for-terminals.md index 5a6a3f5e..b3f98b5c 100644 --- a/docs/adr/0044-ratify-a-proposed-record-with-adr-accept-and-present-the-queue-for-terminals.md +++ b/docs/adr/0044-ratify-a-proposed-record-with-adr-accept-and-present-the-queue-for-terminals.md @@ -2,7 +2,7 @@ schemaVersion: 0.2.0 id: "0044" title: "Ratify a proposed record with adr accept and present the queue for terminals" -status: proposed +status: accepted date: 2026-09-30 deciders: ["@mbeacom"] tags: [cli, queue, governance, compatibility] @@ -25,9 +25,11 @@ affects: pattern: "packages/cli/src/command-registry.ts" provenance: authoredBy: agent-drafted + ratifiedBy: "@mbeacom" review: tier: async tierReason: Grows the public write surface from two commands to three; a semver commitment under ADR-0031. + decidedAt: 2026-10-01T02:01:16Z reviewBy: 2027-03-31 --- @@ -224,9 +226,9 @@ cannot be reshaped for terminals without breaking them. 4. [x] Enforce in the agent plugin's tests that no component runs `adr accept`. 5. [x] Update `AGENTS.md`, `site/src/content/docs/commands.mdx`, and `CHANGELOG.md`, including every statement that only two commands write. -6. [ ] Ratify this record with `adr accept 0044 --by `. That is +6. [x] Ratify this record with `adr accept 0044 --by `. That is the first real use and the rung-1 functional evidence for the command. -7. [ ] In the pull request that accepts this record, update every public +7. [x] In the pull request that accepts this record, update every public proposed-state qualifier that names it. `AGENTS.md` carries three: the `adr queue` `--format` bullet, the `adr accept` section, and the write-surface sentence. `site/src/content/docs/commands.mdx` carries diff --git a/site/src/content/docs/commands.mdx b/site/src/content/docs/commands.mdx index 283190ad..ee5607df 100644 --- a/site/src/content/docs/commands.mdx +++ b/site/src/content/docs/commands.mdx @@ -437,7 +437,7 @@ for byte, so CI, the managed-issue Action, and agents see no change. Pass Accept a `proposed` record as its named ratifier. This is one of three commands that write, alongside `new` and `migrate` -([ADR-0044](/adr/0044-ratify-a-proposed-record-with-adr-accept-and-present-the-queue-for-terminals/), proposed). +([ADR-0044](/adr/0044-ratify-a-proposed-record-with-adr-accept-and-present-the-queue-for-terminals/), accepted). ```bash adr queue # see what is waiting