feat: add code-aware bootstrap baselines

[JonatasFreireDev]

Summary

• Discover and persist semantic implementation roots beside product/ during initialization.
• Require approved Product Landscape, Engineering System, and Design System baselines before real Specifications in newly initialized products.
• Add engineering-orchestrator to govern the shared engineering baseline and its human approval gate.
• Split canonical ownership into technical-landscape, engineering-standards, operations-baseline, and engineering-evidence specialist skills, each with its own templates and applicable inventory scripts.
• Keep engineering-system as the aggregate/versioning and Engineering Quality System owner instead of a monolithic author of every engineering contract.
• Validate declared owner_skill values in aggregate and root catalogs, while accepting absent ownership metadata in legacy adopter content.
• Synchronize FRAMEWORK, documentation, starter contracts, runtime assets, init/upgrade coverage, skill handoffs, and CLI inspection output.

Compatibility

• Fresh init receives specialist ownership metadata, root engineering catalogs, and all six engineering runtime skills for Codex, Cursor, and Claude.
• Upgrade does not overwrite adopter-owned engineering files, approval records, or custom content.
• Existing products without owner_skill remain valid; a declared incorrect owner becomes a blocker.
• The Events fixture remains unchanged because existing products opt into the additive ownership contracts through governed evolution and human re-approval.

Validation

• gofmt -w assets.go cmd internal
• go test ./...
• go vet ./...
• go run ./cmd/spec-framework validate --product-root examples/events --framework-root .
• go run ./cmd/spec-framework engineering-system validate --product-root starter/product
• skill contract audit for the five new canonical skills
• init/upgrade and runtime-skill smoke for Codex, Cursor, and Claude
• PowerShell and shell inventory-script smoke on a fresh code-aware repository
• release-candidate binary, upgrade preservation, forbidden-surface, and checksum smoke
• git diff --check

Delegated engineering execution

• Keep sequential execution as the compatible default and add an explicit delegated mode for harness-native subagents.
• Persist minimal-context engineering envelopes with canonical phases, returned dependencies, bounded parallelism, specialist-owned write scopes, blockers, decision candidates, and SHA-256 output hashes.
• Route assignment/observation through Dispatch Orchestrator and compact-return validation through Subagent Return Reviewer; the CLI remains portable and never starts agents itself.
• Reject stale handoffs, escaped scopes, invalid IDs, blocked or stale dependencies, duplicate active roles, output drift, and concurrent capacity races.
• Cover the CLI assign/return path plus concurrency, fallback, dependency, scope, staleness, and distribution behavior; Linux CI owns the race detector gate.