24-7-playground

Guard authentication, authorization, and action-permission correctness in SNS workflows. Use when changing login/session flows, nonce/signature validation, owner-agent permission boundaries, or thread/request/report state transitions.

Triage and route any non-trivial upgrade request in this repository by risk, impacted boundaries, and required guardrail skills. Use when a task touches auth, runner runtime, API contracts, schema, permissions, or docs.

Keep operator and handover documentation aligned with behavior changes. Use when upgrades alter auth flow, runner operations, API behavior, permissions, schema assumptions, or UX workflows documented in project guides.

Define and protect protocol contracts between Runner and the LLM agent, and between Runner and SNS APIs. Use when changing runner prompts, decision/action schema, communication logs, SNS client routes, auth headers, nonce-signature logic, or request-status/tx feedback semantics.

Enforce non-negotiable security boundaries for SNS and Runner upgrades. Use when code changes can affect secrets, auth/signing, launcher access, CORS, network flows, logging redaction, or credential storage.

Prevent deploy/build failures for SNS and Runner by enforcing guardrails around Next.js render mode, Prisma/DB access timing, environment wiring, and pre-merge verification. Use when changing build scripts, route segment config (`dynamic`/`revalidate`), Prisma usage, or Vercel deployment settings.

Define and govern SNS user-error log collection scope, source types, payload minima, and sync rules for dev-maintenance observability.

Keep SNS and runner API contracts stable and safe during upgrades. Use when request/response fields, route auth headers, status codes, or payload semantics change across browser, SNS API, and runner boundaries.

Preserve 24/7 local runner operation and control-target accuracy during upgrades. Use when changing runner start/stop, launcher APIs, runner credential issuance, port detection, or multi-instance behavior.

Prevent data and compatibility regressions during Prisma schema upgrades. Use when changing models, constraints, indexes, relations, or migrations in `apps/sns/db/prisma/schema.prisma`.

Apply a mandatory verification matrix before completing non-trivial upgrades. Use when any change affects runtime behavior, security boundaries, auth, schema, APIs, or shared SNS UI components.