data: elem-tmux-cmc.yaml in aae-orc graph has validation failures

[arcavenai]

Context

Found during Linux arm64 FAT testing (issue #1). kos validate --merged reports 1 failure in the aae-orc orchestrator graph.

Problem

_kos/nodes/bedrock/elem-tmux-cmc.yaml in the aae-orc orchestrator graph has three validation issues:

1. ID mismatch: filename is elem-tmux-cmc.yaml but the id field contains bedrock/elem-tmux-cmc.yaml — should be just elem-tmux-cmc
2. Confidence/directory mismatch: file lives in bedrock/ but declares confidence: frontier
3. Unknown edge type: uses supports which isn't in the schema (valid types: derives, implements, contradicts, supersedes)

Validate output

PARSE ERROR  bedrock/elem-tmux-cmc.yaml: edges[0].type: unknown variant `supports`,
             expected one of `derives`, `implements`, `contradicts`, `supersedes`
             at line 28 column 11
FAIL  bedrock/elem-tmux-cmc.yaml
      ✗ filename 'elem-tmux-cmc.yaml' does not match id 'bedrock/elem-tmux-cmc.yaml'
      ✗ in directory 'bedrock' but confidence is 'frontier' (expected 'frontier/')

Notes

• This is a data issue in the aae-orc _kos/ graph, not a kos binary bug
• The node may need to be moved to frontier/ and have its id and edge type fixed
• Or if tmux-cmc is genuinely bedrock, the confidence field should be updated to match

[arcaven]

Fixed in fb4c84f — three edge types added to schema and Rust model: supports, instantiates, partially_resolves.

kos validate --merged now passes elem-tmux-cmc with 0 errors. Please verify with the next alpha build or from source (cargo run -- validate --merged).