skills/boshu2__agentops
1
0
Fork 0
mirror of https://github.com/boshu2/agentops.git synced 2026-09-14 15:08:13 +08:00
Code Issues Packages Projects Releases Wiki Activity

fix(docs): markdownlint MD049 in ubiquitous-language.md

Browse Source 
Cycle 58 commit 5a39f7c9 landed the ubiquitous-language meta-contract
but used asterisk emphasis (*immediately*) on line 114 where the
repo's markdownlint config (.markdownlint.json) requires underscore
emphasis (_immediately_). CI markdownlint job failed with 2 MD049
errors at line 114:43 and 114:55.

Restorative cycle per Step 1.5 healing-first classifier — cycle 57+58
both red, this fix targets cycle 58's contribution. go-build coverage
failure (cycle 57's separate root cause: cmd/ao 75.8% < 76% floor)
deferred to cycle 60 per single-concern principle.

Matches the cycle-48 markdownlint MD004 fix shape (commit cbdeda48 —
also a one-character-class-correction in a docs/releases/ file).
Drift-block: CI markdownlint job IS the regression detector — no
new test needed because the existing gate catches the violation.

Code-driven fitness: markdownlint errors 2 → 0; CI markdownlint
job: failure → success (expected on push).

Cycle 59 / restorative mode of the 2026-05-12 rescope.
This commit is contained in:
Boden Fuller
2026-05-12 14:26:17 -04:00
parent 5a39f7c977
commit cd542b73a1
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/contracts/ubiquitous-language.md
+1 -1
View File
@@ -111,7 +111,7 @@ Matches the existing meta-contract shape from `docs/contracts/update-principles.
Not claiming these are the only naming decisions worth pinning. The five ranked drifts here are the ones the bounded-context inventory measured as highest-pain (cross-referenced in multiple files with semantic conflict). Other terms may surface in future audits; they get added here as discovered.
Not claiming legacy names must be retired *immediately*. The rename schedule is per-cycle; each rename is bounded and reversible. Code can use legacy names until its rename cycle fires; documentation should start using canonical names from contract-landing day.
Not claiming legacy names must be retired _immediately_. The rename schedule is per-cycle; each rename is bounded and reversible. Code can use legacy names until its rename cycle fires; documentation should start using canonical names from contract-landing day.
Not claiming this contract overrides PRODUCT.md or GOALS.md. Where those documents use a legacy term, the rename gets harvested as follow-up work, not retroactively edited.