topo-validate

/topo-validate

Run a full consistency check on docs/solution-map.topo and regenerate the dependency graph.

Step 1: Load the Map

Read docs/solution-map.topo. If it does not exist, tell the user to run /init-project or create it from the template.

Step 2: Parse All Component Blocks

Extract every TOPO block and build an in-memory index:

• Component ID (tag + name, e.g. [SL] ValidateItem)
• All depends_on table entries
• All depended_on_by table entries
• For [CL] blocks: the parity value
• For [DE] blocks: the server-logic, client-logic, ui-controls lists
• For all blocks: the lifecycle value

Step 3: Bidirectional Dependency Check

For every depends_on entry pointing to target [X] Name:

• Verify [X] Name exists in the map
• Verify [X] Name has a depended_on_by entry referencing this component

For every depended_on_by entry pointing to source [X] Name:

• Verify [X] Name exists in the map
• Verify [X] Name has a depends_on entry referencing this component

Report: DEPENDENCY MISMATCH: [SL] ValidateItem depends_on [DE] contoso_itemtype, but [DE] contoso_itemtype does not list [SL] ValidateItem in depended_on_by

Step 4: Orphan Reference Check

Any component referenced in depends_on, depended_on_by, server-logic lists, client-logic lists, ui-controls lists, parity references, or backing-logic references that has no block in the map.

Report: ORPHAN REFERENCE: [SF] InventoryApiClient referenced by [SL] ValidateItem but has no [SF] block

Step 5: Entity Cross-Reference Check

For every [DE] block:

• Every component listed in server-logic must have a corresponding [SL] block
• Every component listed in client-logic must have a corresponding [CL] block
• Every component listed in ui-controls must have a corresponding [UC] block

Report: MISSING BLOCK: [SL] ValidateItem listed in [DE] contoso_listlineitem server-logic but no [SL] block exists