v0.23.2
Patch release: the third and last of the shared-namespace collisions in the product→architect handoff, found by running the product pipeline through the full profile. All three plugins (product, architect, scalardb) move to 0.23.2 together.
Fixed
NFR-IDs could be minted twice, by two skills, for different requirements.docs/design.md
§1.5 told architect to createNFR-nodes for architect-originated NFRs without saying where the
number comes from, which silently assumed product had already rundefine-nfr. It has not always:
a product run that stops at--profile=mvphands off todefine-requirements, which finds no
NFR-and mintsNFR-001; resume the product pipeline afterwards anddefine-nfrmints
NFR-001too. An end-to-end run through the full profile produced exactly this — six IDs, each
with two meanings, in the single graph both plugins share. §1.5 gained rule 4: allocate every new
ID asmaxover the graph for that prefix+ 1, the same ruleOQ-follows. The §1.5
verification list now includes "no ID appearing twice", soreview-consistencyand
/product:reviewcatch a recurrence instead of leaving it to a later reader.