runtime-contract-audit

Étoiles9

Forks3

Mis à jour15 mars 2026 à 18:11

Audit LawnBerry Pi runtime contract drift across ports, startup behavior, systemd units, frontend proxies, docs, scripts, and config. Use for port mismatches, startup confusion, README vs runtime checks, and source-of-truth comparison work.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

acredsfan

acredsfan/lawnberry_pi

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes des systèmes informatiquesProfessions informatiques et mathématiques·SOC 15-1211

SKILL.md

readonly

name	runtime-contract-audit
description	Audit LawnBerry Pi runtime contract drift across ports, startup behavior, systemd units, frontend proxies, docs, scripts, and config. Use for port mismatches, startup confusion, README vs runtime checks, and source-of-truth comparison work.
argument-hint	What runtime surface or port/startup behavior should be audited?
user-invocable	true

Runtime Contract Audit

What this skill does

This skill performs a focused drift audit for ports, startup wiring, proxy behavior, and maintainer-facing runtime instructions.

Use it for

port mismatch reports
startup command confusion
frontend-to-backend proxy drift
systemd/runtime/docs inconsistency checks
validating that a change did not silently break the established contract

Source-of-truth files

Read and compare these first:

docs/developer-toolkit.md
README.md
docs/OPERATIONS.md
docs/TESTING.md
frontend/vite.config.ts
frontend/server.mjs
frontend/playwright.config.ts
systemd/
backend/src/main.py
relevant scripts under scripts/

Procedure

Capture the claimed runtime contract from maintainer docs.
Verify the canonical ports and behavior in code and service units.
Compare these surfaces explicitly:
- backend bind port and path prefix
- frontend dev port, preview port, and production server behavior
- proxy target for /api
- local development commands vs deployed service commands
- docs examples vs actual service wiring
Produce a concise mismatch table grouped by severity.
If fixing drift, update the smallest set of docs/config files needed to restore a single consistent story.
Re-check all touched surfaces after the edit.

Decision rules

treat backend/src/main.py, service units, and active frontend config as stronger truth than prose docs
keep 8081, 3000, and 4173 unless intentionally changing the contract everywhere
avoid broad rewrites; prioritize contradictions that would mislead maintainers or operators

Completion checks

strongest source of truth is cited for each finding
any port mismatch is resolved or clearly documented
startup instructions match actual runtime behavior
no stale proxy or service-unit references remain in edited files

Plus depuis ce dépôt

même dépôt

sim-hardware-validation

acredsfan/lawnberry_pi

Use for LawnBerry Pi simulation vs real-hardware validation. Covers SIM_MODE selection, .env and config checks, simulation-safe test-first workflow, hardware preflight expectations, and avoiding false claims that local success proves on-device behavior.

2026-06-259

ai-model-quality-pass

acredsfan/lawnberry_pi

Use for improving LawnBerry Pi AI result quality without breaking the existing backend contract. Covers ai_service review, model artifact or rule improvement, conservative evaluation, performance notes, and avoiding premature accelerator-specific churn.

2026-03-159

control-camera-regression-review

acredsfan/lawnberry_pi

Review regression-sensitive LawnBerry Pi manual control and camera paths: RoboHAT USB handoff, watchdog feeding, motor authorization, joystick responsiveness, MJPEG and snapshot fallback, camera ownership, and stream backpressure handling.

2026-03-159

maintainer-doc-sync

acredsfan/lawnberry_pi

Keep LawnBerry Pi maintainer documentation synchronized with implementation. Use when runtime behavior, supported hardware scope, subsystem maturity, immediate focus, two-week plan, release notes, or callable interfaces have changed and docs must be updated in the same pass.

2026-03-159

maintainer-reentry

acredsfan/lawnberry_pi

Use when returning to LawnBerry Pi after time away, starting substantial maintenance, or needing a fast project re-entry workflow. Covers docs to read first, runtime ports, hardware baseline, simulation vs hardware mode, important files by task, and validation planning.

2026-03-159

maintenance-orchestration

acredsfan/lawnberry_pi

Use when a LawnBerry Pi task spans re-entry, specialist routing, implementation, documentation sync, and validation. Covers choosing the right specialist workflow and sequencing investigation, changes, doc updates, and test planning.

2026-03-159

Runtime Contract Audit

What this skill does

This skill performs a focused drift audit for ports, startup wiring, proxy behavior, and maintainer-facing runtime instructions.

Use it for

port mismatch reports

startup command confusion

frontend-to-backend proxy drift

systemd/runtime/docs inconsistency checks

validating that a change did not silently break the established contract

Source-of-truth files

Read and compare these first:

docs/developer-toolkit.md

README.md

docs/OPERATIONS.md

docs/TESTING.md

frontend/vite.config.ts

frontend/server.mjs

frontend/playwright.config.ts

systemd/

backend/src/main.py

relevant scripts under scripts/

Procedure

Capture the claimed runtime contract from maintainer docs.

Verify the canonical ports and behavior in code and service units.

Compare these surfaces explicitly:

backend bind port and path prefix
frontend dev port, preview port, and production server behavior
proxy target for /api
local development commands vs deployed service commands
docs examples vs actual service wiring

Produce a concise mismatch table grouped by severity.

If fixing drift, update the smallest set of docs/config files needed to restore a single consistent story.

Re-check all touched surfaces after the edit.

Decision rules

treat backend/src/main.py, service units, and active frontend config as stronger truth than prose docs

keep 8081, 3000, and 4173 unless intentionally changing the contract everywhere

avoid broad rewrites; prioritize contradictions that would mislead maintainers or operators

Completion checks

strongest source of truth is cited for each finding

any port mismatch is resolved or clearly documented

startup instructions match actual runtime behavior

no stale proxy or service-unit references remain in edited files