Files

T

timothyandClaude Opus 5.5 41d604f0ae fix(935): script-tests jq tripwire accepts exactly {1.6, 1.7} until server-management#1080 pins the fleet

jq-preflight.sh --expect takes a comma-separated set (validated whole, exact
major.minor membership); pr-checks.yml passes 1.6,1.7. Both small runners float
on runner-images:ubuntu-latest, so the fleet's jq is a function of pull history
(1.7 measured on PR #933 job 12347 and PR #934 job 12360, 2026-10-29).

New record ci.jq-accepted-version-set supersedes ci.jq-version-contract
(archived); docs/ci-cd.md, the script header and runner-ships-1.6 comments now
state the dated invariant. review-verdict.yml stays floor-only.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: f9ce6bc6-5b36-491a-8d72-89c1f70dd3e1

2026-10-29 21:38:38 +01:00

api

fix(578): the LIKE prefilter under-matched every accented artist; make the superset provable

2026-07-27 03:10:35 +02:00

fix(935): script-tests jq tripwire accepts exactly {1.6, 1.7} until server-management#1080 pins the fleet

2026-10-29 21:38:38 +01:00

docs

feat(610): split the decision corpus into one YAML-frontmatter file per record

2026-07-25 19:45:09 +02:00

scan

feat(610): split the decision corpus into one YAML-frontmatter file per record

2026-07-25 19:45:09 +02:00

spa

feat(651): media-library pickers resolve by search instead of a bounded window

2026-07-27 04:25:14 +02:00

testing

docs(563): supersede the scripted-golden deferral with the in-process coverage rule

2026-09-05 09:25:11 +02:00

api.md

feat(610): split the decision corpus into one YAML-frontmatter file per record

2026-07-25 19:45:09 +02:00

README.md

feat(521): reconcile #390/#406 + #411 + append-only supersession; seed exemplars [decisions-edit]

2026-07-21 03:00:15 +02:00

release-ci-governance.md

feat(610): split the decision corpus into one YAML-frontmatter file per record

2026-07-25 19:45:09 +02:00

scan.md

feat(610): split the decision corpus into one YAML-frontmatter file per record

2026-07-25 19:45:09 +02:00

spa.md

feat(610): split the decision corpus into one YAML-frontmatter file per record

2026-07-25 19:45:09 +02:00

startup.md

feat(610): split the decision corpus into one YAML-frontmatter file per record

2026-07-25 19:45:09 +02:00

README.md

Archive — superseded / retired decision records

This directory holds decision records whose status is superseded or retired. They are kept verbatim (rationale prose untouched — see docs/decisions.md header and scripts/decisions_lib.py) for history: why we changed our mind is the point, never silently rewritten.

They are out of the active startup path: scripts/decisions_lib.py active_files() / all_active_records() do not glob this directory, docs/decisions/README.md (the active catalog) never lists a record from here, and an agent doing task-router discovery should not need to read this directory to find the current rule — follow a record's superseded-by key to the active successor instead.

The lifecycle validator (scripts/decisions_validate.py) still enforces invariants here:

a superseded/retired record MUST live under this directory, never in an active file;
an active record MUST NOT live under this directory;
supersedes/superseded-by keys must resolve reciprocally to a record in the active set OR here;
a record moved here must not have its rationale prose changed in the same commit (unless the commit message carries the [decisions-edit] token, reserved for genuine rationale edits).

One file per topic cluster (e.g. ci.md, release-ci-governance.md), mirroring the active docs/decisions/*.md topic-file split. See docs/decisions/migration-map.md for the legacy heading → key → status → location mapping produced during the #521 lifecycle migration.