Repository navigation
v3.13.2
What's new
Bug Fixes
ce:compound-refresh carried its own copy of the solution-document contract that ce:compound writes against, and that copy had drifted. It recognized four fewer knowledge-track problem types than the canonical contract, so documents filed as architecture_pattern or convention — three of which already exist in the repo — read as invalid to the very skill responsible for judging whether they're correct.
The bigger issue was two missing YAML quoting rules. Without them, a value containing a space followed by a hash ( #) is silently truncated by the YAML parser with no error raised. Because ce:compound-refresh's entire job is rewriting documents, it was exactly the surface where losing that rule would reintroduce the bug it exists to prevent.
Both files are now byte-identical to their ce:compound counterparts — matching the resolution template the two skills already shared. A new test asserts all three shared files stay identical and that the two knowledge-track enums parse to the same set, so this drift can't recur silently. The duplication itself stays intentional: the Claude Code build flattens each skill into a self-contained bundle, so having one skill point at another's file isn't safe across harnesses. The compound-docs copy of the contract is untouched — it has no track sections and predates this contract, so aligning it is a separate decision. (#841)