Map the existing Eve control plane into NodeKit

[HomenShum]

Outcome

Brownfield-maps NodeVideo's existing Eve control plane into the canonical NodeAgent application contract without moving files, replacing Eve, or changing worker authority.

What changed

• adds a root flat nodeagent.application/v1 manifest
• maps apps/eve-agent/agent as the filesystem-authored agent
• logically declares the existing song-conditioned auto-edit pack through canonical pack.yaml
• adds explicit local-isolation and credentialed-live eval bindings
• commits secret-free .nodeagent discovery/resolution metadata
• adds an independent map validator and runs it from the existing check chain
• classifies all three Eve agent.ts subagents through the adapter-aware compiler without creating duplicate YAML definitions
• documents runtime, credential, authentication, evaluation, and compiler boundaries

Proof

Compiled with NodeKit commit f4ac7c6 from node-platform #4:

• config hash e1ee1155566d...
• 217 files bound
• all 63 tracked apps/eve-agent/agent files bound
• all three Eve subagents classified
• canonical song pack and both top-level eval bindings bound
• diagnostics: 0 errors / 0 warnings
• generated artifacts contain secret names only

Validation:

• NodeKit compile/check/inspect/repo-check: passed
• Eve Node 24 isolation, typecheck, build, and info: passed
• root lint, typecheck, capability validation, NodeAgent-map validation, and build: passed
• Vitest with --testTimeout=15000: 34 files / 175 tests passed

Honest boundary

This is mapping-only. Eve 0.24.4 remains the runtime; the generated metadata is not consumed by Eve yet and does not prove a shared local/eval/production execution path, NodeAgent-native events, shadow parity, a live model run, or authenticated production deployment. Live Eve evals were not run because model and control-plane credentials were unavailable.

The repository's default 5-second Vitest timeout remains red on one pre-existing render-metrics-v2 duration; that same test passes with the 15-second timeout used above. This PR does not weaken that threshold or represent it as a green default gate.

Review/merge after the compiler behavior in node-platform #4 is accepted. No deployment or publication is included.