Repository navigation
v3.13.1
What's new
A small maintenance release: a fix to the knowledge-doc categorization schema and two new solution-doc learnings drawn from the review artifact contract work.
Bug Fixes
- ce-compound: The knowledge-track schema accepted
architecture_pattern,design_pattern,tooling_decision, andconventionas valid track values, but the reference guide's track table listed none of them and gave none of them a category directory — an author choosing one of these four had a validproblem_typeand nowhere to file the document. All four now map tobest-practices/, the directory where documents already using these tracks were already being filed, rather than splintering into four directories that would each hold a single document. The guide also now states that the narrowest applicable value is preferred, gives a one-line description of what each of the four tracks means, and clarifies that the knowledge-track field rules apply to every type in the table, not just the original four.
Documentation
- Adds a learning on why an artifact contract with no validated write path ends up with no conforming producers, drawn from measuring review-run artifacts before scoping issue #793: seven artifacts across 26 runs, no two sharing a shape, every documented ledger field absent, and an undocumented field present in all of them.
- Extends the existing input-set learning with a third contaminant beyond gitignored build output and ambient user config: standing on the wrong branch, which defeats the usual "check for untracked/dirty files" recommendation because another branch's tracked files are clean and so never show up as ignored or dirty.
- Documents a verification method: correcting a repeated fact by searching for one phrasing leaves other occurrences worded differently, so enumerate the individual claims instead — doing so turned up an error nobody was looking for. The learning's title was broadened from counts to repository claims generally, since it now covers whether a documented path exists at all.