Skip to content

ENG-TRAILER-MERGE-ARTIFACTS closed DONE on main without updating docs/STATUS.md or docs/BENCHMARKS.md #420

Description

@localai-bot

Found while merging origin/main into row/KV-EVENTS-W2; filed rather than fixed, because repairing another row's DONE record inside a KV-EVENTS PR would surprise a reviewer and docs/BENCHMARKS.md is under a hard 45,000-char cap.

211ff73arecord(ENG-TRAILER-MERGE-ARTIFACTS): close the row DONE at 157080c8 (#416) — moves the row ACTIVE -> DONE in .agents/engine-matrix.md and touches no public document. AGENTS.md §"Public documents": a lifecycle change owes STATUS, BENCHMARKS and NOW.

The repo's own checker agrees, per commit:

$ python3 scripts/check-doc-checkpoint.py --commit 211ff73a
ERROR: commit 211ff73a: changed .agents/engine-matrix.md: ENG-TRAILER-MERGE-ARTIFACTS
ACTIVE -> DONE but did not update docs/BENCHMARKS.md, docs/STATUS.md.

CI did not catch it because .github/workflows/ci.yml:240 runs the checker over a --base/--head RANGE, not per commit, and the range that landed #416 must have carried a compensating doc edit from another commit. Any branch that merges 211ff73a and then runs --staged or --commit sees the error attributed to itself.

Neither ENG-TRAILER-MERGE-ARTIFACTS nor "trailer" appears anywhere in docs/STATUS.md, so a reader has no way to learn the row shipped.

Two things to fix:

  1. Record the row in docs/STATUS.md (and docs/BENCHMARKS.md as its DONE state requires), paying the BENCHMARKS cap by moving a superseded row into .agents/benchmark-record.md byte-for-byte if needed.
  2. Decide whether the range-only CI invocation is the intended semantics. If per-commit is the contract the checker's message implies, CI should run it per commit; if range is the contract, the message should say so, since it currently reads as a per-commit claim.

Row: ENG-TRAILER-MERGE-ARTIFACTS. Kind: bug.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions