Log first responder

The agent prompt

Copy this brief into your coding agent from the root of the project you want to build in. It names the behaviour, the constraints, and the checks to run — the decisions Jev makes stay explicit so you can see what the model actually decided.

Build a local "Log first responder" dashboard in this repository with Jev from TypeSafe AI.

First inspect the repo and follow its existing architecture. Use the official TypeSafe skill for current patterns, installing it with npx skills add typesafe-ai/skills --skill typesafe-ai if absent.

Accept pasted newline-delimited JSON log events. Validate and redact likely secrets locally before any API call. For each safe event, ask Jev for a Choice category (routine, application error, dependency failure, security signal, unknown), a Score severity rubric, and a Noul indicating whether immediate human attention is warranted. Show a filterable queue and a clearly explained policy that escalates only high-severity or high-attention results above a configurable confidence floor.

Requirements:
- Keep the API key and Jev call on the server.
- Cap file size, event count, and concurrency.
- Never render raw log content as HTML. Redact tokens, authorization headers, emails, and obvious credentials before transport and display.
- Make the deterministic escalation policy separately testable.
- Include realistic synthetic fixtures; no production logs.
- Add tests for validation, redaction, partial failure, and routing.

Run the relevant checks and explain the privacy boundary in the handoff.

Built something like this

Community projects in the directory that solve a similar problem:

• jevlogs
• commit-miner
• semdecide