feat: decouple intent/code from core (ontology-declared SourceRoles)

[mroops0111]

Summary

Decouples the hard-coded intent / code source taxonomy from core so a third-party ontology can declare its own source roles and run the full extract, propose, HITL, model, view loop without touching @braidhq/core or @braidhq/schema. DDD becomes one ontology among several, declaring intent / code as data.

The guiding principle: the framework never branches on a role's identity, only on a capability the ontology declares for that role. The role name disappears from the framework; the capability stays.

What changed

schema

• SourceRole is now an open branded string (matching the LoaderKind precedent) instead of a closed z.enum(['code','intent']).
• BatchInputMode renamed intent | derive to role-agnostic direct | derived.
• Skill-input provider source-intent generalized to source with a role filter parameter.
• OntologyResponse carries sourceRoles; new OntologyListResponse.

core

• SourceRoleDescriptor capability model on OntologyPlugin (id, label, required, unitBearing, pathSegment) replaces requiredSourceRoles. unitBearing is a single capability that drives both batch unit production and Reactor gating.
• Workspace.sourcesWithRole(role) replaces intentSources() / codeSources(); domain stays pure, the application layer resolves the ontology.
• BatchService.resolveMode, ReactorService.isUnitBearingSource, and the unit lister all read the declared capability, not a role literal.

server

• intentScan becomes a generic unitScan filtered by the ontology's unit-bearing roles.
• New host-level GET /ontologies catalog endpoint (pre-workspace flows like the wizard); GET /ontology now returns sourceRoles.

sdk / ontology-ddd

• SDK re-exports SourceRole; defineOntologyPlugin takes sourceRoles and merges an extended ontology's roles.
• DDD declares intent (unit-bearing) and code as data.

studio

• Add-source dialog, create-workspace wizard, and the batch page render whatever roles the active ontology declares, fetched from the endpoints above, instead of hard-coded literals.

Not in this PR

• The metadata.intentMissing / implementationMissing evidence flags encode a trust/corroboration model, not the source taxonomy, so they are left for design: trust / convergence model for domains with no privileged fact-SSoT #68 (trust / convergence for domains with no privileged fact source). They do not block this change: a non-software ontology's nodes carry sourceReferences and never set them.

Verification

• pnpm typecheck green across all 15 packages.
• Every package's test suite passes when run on its own; litmus grep "'intent'|'code'|source-intent" packages/*/src hits only packages/ontology-ddd.
• Framework and shared @braidhq/test-utils fixtures are role-neutral (primary / secondary); tests that exercise the real DDD ontology keep intent / code as its declared vocabulary.
• Also fixes a pre-existing build break in examples/redoc-extending-ddd (used a non-existent defineOntology export).

Refs #50

🤖 Generated with Claude Code