Add loop-jev (TypeSafe System One) for cheaper loop decisions

[cobusgreyling]

Yes — Jev is now a first-class Loop Engineering tool, not a side repo only.

What

New package tools/loop-jev (npx @cobusgreyling/loop jev …) uses TypeSafe Jev as the System One layer in front of the coding agent:

Command	Decision
route	cheapest model tier that can still do the turn
retrieve	which passages belong in context
guard	pass / review / block jailbreaks, injection, secret leaks
classify	failure mode on a trace or ledger
turn	route and input-guard in one Jev call

Jev assesses; code owns thresholds (same pattern as loop-gate / loop-context: exit 0 proceed, 2 escalate).

Low-confidence frontier picks fall back to balanced instead of overspending.

Without TYPESAFE_API_KEY (or ~/.config/typesafe/api_key), a heuristic fallback keeps CI green. --no-fallback requires a live call. Secrets in state are redacted before send; doctor never prints the key.

Also wired into:

• loop jev … pass-through
• MCP tools loop_jev_route / loop_jev_guard / loop_jev_classify
• skill skills/loop-jev
• docs/jev.md

Companion showcase: https://github.com/cobusgreyling/Jev (packages/js).

Auth (do not commit)

export TYPESAFE_API_KEY=…
# or chmod 600 ~/.config/typesafe/api_key
npx @cobusgreyling/loop jev doctor

[github-actions]

This PR changes paths that must run the real validate and audit workflows (tools, patterns, scripts, or CI).

Fork PRs from first-time contributors start with those workflows waiting for approval. A maintainer needs to open the Checks tab and click Approve and run workflows. Until that happens, branch protection will show the PR as blocked even after a review.

Content-only PRs (docs/, examples/, stories/, skills/, root markdown) skip this step — required checks are posted from this workflow instead.

— loop-engineering fork-pr-gate

[github-actions]

Thanks @cobusgreyling for contributing a tool example — visible, reviewable PRs like this grow the reference for everyone.

What happens next

• Maintainer aims for same-day review on story, adopter, and scoped docs/example PRs (CONTRIBUTING.md).
• good first issue PRs: comment on the linked issue so we can assign and close on merge.

More ways to help

• Contributor quickstart + open issues
• Good first issue backlog

— loop-engineering maintainers

[github-actions]

Loop Readiness Audit

Score: 100/100 (L3)

Strong loop readiness — good candidate for L3 with explicit gates.

Top suggestions

• Run the loop and commit changelog-drafter-state.md (or append loop-run-log.md) so Loop Ready can see a fresh timestamp
• Scaffold a harness: npx @cobusgreyling/loop-init . --with-foundry (or npx @cobusgreyling/harness-foundry init --from loop-engineering:daily-triage)
• Scaffold memory tiers: npx @cobusgreyling/loop-init . --with-memory
• Scaffold a fleet: npx @cobusgreyling/loop-init . --with-fleet

_{Posted by audit.yml · loop-audit docs}