red-markers: add the @hapi/lab row (confirm against a real suite first) #17
Labels
No labels
component:adapters
component:lifecycle
component:qa
component:setup
component:shared
component:worktrees
phase/accepted
phase/backlog
phase/deployed
phase/developing
phase/integrating
phase/planning
phase/qa
phase/requirements
phase/uat
priority:critical
priority:critical
priority:high
priority:high
priority:low
priority:low
priority:medium
priority:medium
type:bug
type:chore
type:docs
type:feature
type:infra
type:tech-debt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jbr870/devwork-skills#17
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Observed failure
On a
@hapi/labAPI repo (axana), the TDD-red marker was unresolvable:red-markers.mdhas no@hapi/labrow and the project declared notest_conventions.red_marker. The resolution order ran outof options.
What it needs
One row in
_shared/procedures/red-markers.md— the write ↔ promote pair for@hapi/lab— addedafter confirming the idiomatic skip/promote pair against a real suite. Guessing the marker is worse
than having no row: a wrong
writemarker produces a test that is not actually red, and the fix stagethen "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.