Add the Eve Content Scout agent

[ferueda]

Summary

• add the standalone TypeScript Content Scout agent on Eve 0.27.8
• pin Node 24.18.0, npm 11.16.0, the Gateway model route, and Flex execution
• expose only a loopback HTTP Basic-authenticated Eve channel
• disable tools, state, external capabilities, and input/output telemetry
• validate the final shared Go and TypeScript contracts

Review path

1. Read agents/content-scout/agent/instructions.md for agent purpose and evidence rules.
2. Read agent/lib/policy.ts and agent/lib/model.ts for the exact runtime policy.
3. Read agent/agent.ts and agent/channels/eve.ts for the Eve surface.
4. Read test/contracts.test.ts and test/policy.test.ts for the cross-language and capability guards.
5. Treat package-lock.json as generated dependency resolution rather than reviewing it line by line.

Boundaries

No Noema database access, Sessions access, tools, publishing, cross-job memory, Go adapter wiring, or live canary.

Verification

• npm ci and npm run check under exact Node 24.18.0 and npm 11.16.0
• typecheck passed
• 10 tests passed
• Eve production build passed
• make check passed on the combined Go tree

Stack

Based on #24 so the review stack is linear. Production integration is the next PR.

[ferueda]

Superseded as a Noema PR by #20, but the Eve agent work is intentionally preserved. The branch and commit remain as the seed for a separate Content Scout project, where its trigger and contracts will be adapted to the external event-consumer boundary.