feat: add protected event ingest foundation agent:clawd

[TargiX]

agent:clawd

Visible API outcome

• Adds protected POST /api/events ingestion on top of the merged bounded event normalizer.
• Requires an explicitly configured Bearer credential and returns one uniform unauthorized response for missing, malformed, or incorrect credentials.
• Stores only accepted normalized/redacted events in a bounded development/test memory sink.
• Returns deterministic receipt/event references plus accepted, rejected, stored, duplicate, evicted, and retained counts.
• Treats exact retries as duplicates and atomically rejects reused event identifiers carrying different normalized content.

Deliberate production block

This PR does not pretend the memory adapter is durable. Production/Vercel selects no memory sink and authenticated requests fail closed with 503 storage_not_ready before body acceptance or storage. A later slice must implement and explicitly wire a durable adapter before production ingest can succeed.

Verification

• mise x node@24 -- corepack pnpm check
  • ESLint
  • TypeScript
  • homepage navigation contract
  • existing event validator contract
  • protected ingest auth/storage/idempotency/redaction/error contract
  • Next.js production build
• git diff --check
• dev-safe inspect, then task-owned launchers bound to 127.0.0.1
  • development URL: http://signalops-protected-ingest-foundation.signalops-ingest-e5df.localhost:1355
  • unauthenticated ingest: 401 unauthorized
  • authenticated ingest: 200, stored 1
  • exact retry: same receipt, stored 0, duplicate 1
  • production URL: http://signalops-protected-ingest-foundation.signalops-ingest-prod-e5df.localhost:1355
  • authenticated production ingest: 503 storage_not_ready
  • both task-owned launchers stopped; dev-safe inspect reports no active routes
• Codex autoreview (local dirty bundle): first pass found the Node runtime contract was implicit; fixed by declaring/documenting Node >=24 and pnpm 10.24.0 to match CI. Final pass: clean, no actionable findings (overall_confidence: 0.91).

Transfer learning

Readiness boundaries should be executable, not marketing copy: a local demo adapter must identify itself as non-durable, receipts must reveal retention behavior, and production must reject writes before validation/storage when durable infrastructure is absent.

Ready for Ilya's manual review and merge. No auto-merge.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
signalops	Ready	Preview, Comment	Jul 18, 2026 7:43pm

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 34 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 279f3435-ce3c-4e39-890e-7eefaa623b9e

📥 Commits

Reviewing files that changed from the base of the PR and between 1f5b1ed and 327a3ad.

📒 Files selected for processing (8)

• README.md
• package.json
• scripts/test-signalops-ingest.mjs
• src/app/api/events/route.ts
• src/lib/signalops/ingest-auth.ts
• src/lib/signalops/ingest-sink.ts
• src/lib/signalops/ingest.ts
• tsconfig.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch clawd/signalops-protected-ingest-foundation

---

_{Comment @coderabbitai help to get the list of available commands.}