red-markers: add the @hapi/lab row (confirm against a real suite first) #17

Open
opened 2026-08-11 14:57:24 +00:00 by jbr870 · 0 comments
Owner

Observed failure

On a @hapi/lab API repo (axana), the TDD-red marker was unresolvable: red-markers.md has no
@hapi/lab row and the project declared no test_conventions.red_marker. The resolution order ran out
of options.

What it needs

One row in _shared/procedures/red-markers.md — the write ↔ promote pair for @hapi/lab — added
after confirming the idiomatic skip/promote pair against a real suite. Guessing the marker is worse
than having no row: a wrong write marker produces a test that is not actually red, and the fix stage
then "promotes" something that was never failing.

Note on scope

Add it to the canonical table only. Per the resolved-debt rule in the repo's CLAUDE.md, do not
re-introduce a per-domain marker mapping.

Source: dogfood retrospective 2026-08-07 (F5), deferred backlog.

## Observed failure On a `@hapi/lab` API repo (axana), the TDD-red marker was **unresolvable**: `red-markers.md` has no `@hapi/lab` row and the project declared no `test_conventions.red_marker`. The resolution order ran out of options. ## What it needs One row in `_shared/procedures/red-markers.md` — the write ↔ promote pair for `@hapi/lab` — added **after confirming the idiomatic skip/promote pair against a real suite**. Guessing the marker is worse than having no row: a wrong `write` marker produces a test that is not actually red, and the fix stage then "promotes" something that was never failing. ## Note on scope Add it to the canonical table only. Per the resolved-debt rule in the repo's CLAUDE.md, do **not** re-introduce a per-domain marker mapping. *Source: dogfood retrospective 2026-08-07 (F5), deferred backlog.*
Sign in to join this conversation.
No description provided.