Imported from ravisingh11/ai-software-toolkit-reference-app (
AGENTS.md). Install upstream withnpx skills add ravisingh11/ai-software-toolkit-reference-app. Copyright stays with the author.
Application instructions
This repository is Fieldnotes, the deployed reference consumer of AI Software Toolkit. Keep application contracts in docs/design.md and upstream toolkit policy in the pinned .proof runtime. Never modify vendored runtime merely to make a check pass.
Use PRs for normal main changes. Preserve unrelated work. Use bounded native subagents when useful; they must not overwrite another lane. No credentials, real customer data, or production identity claims in this public demo. Demo workspaces expire after 24 hours. Keep API authorization independent of UI affordances.
Before PR: npm ci, npm run build, npm run lint, npm run test:coverage, npm run validate:migrations, npm run test:e2e, python3 .proof/validators/validate_repository.py, git diff --check. Run app-specific .agents/skills/qa for agent functional QA; deterministic tests alone are not agent QA. Missing producers are never passed. Functional QA stays advisory.
Deploy only a clean committed revision; use scripts/release.sh once available. Verify live health revision and real API/browser operation. Code rollback never reverses D1 schema; migrations must be backward compatible. See docs/design.md and docs/deployment.md.
Workspace Hygiene
- At task start, inspect status, the current branch, registered worktrees, relevant open PRs, and active task ownership. Reuse a suitable checkout; preserve primary/default, locked, shared, and actively used worktrees.
- Record task-owned scratch paths and processes. Retain release evidence and reusable outputs in a named artifact location; unknown temporary files are not disposable merely because of their age or name.
- When cleanup is requested, fetch the intended upstream and verify current PR state. Committed or pushed does not mean merged: require exact commit reachability from the intended upstream target before ordinary removal. Fail closed on Git or API errors; missing results are not safety evidence.
- Before removal, check tracked, untracked, and ignored files, nested Git repositories/submodules, active processes, and checkout ownership. Preserve local-only commits, local databases/configuration, and evidence. A clean tracked-file status alone is insufficient; recheck immediately before acting.
- Record paths, before/after refs, preservation evidence, and recovery refs or
archive manifests. Use the application's archive operation for managed
worktrees; otherwise use
git worktree removewithout force. Do not use broad temporary-directory deletion or globalgit clean. Preserve needed ignored files separately; a Git snapshot may omit them. - Squash/cherry-pick equivalence is not exact reachability. Retain these
branches/worktrees for explicit review or a verified recoverable archive;
never force-delete based on patch equivalence or empty
git cherryoutput. - At completion, stop task-owned processes and remove only task-created, disposable scratch after its consumers stop. Report branch, PR, worktree, scratch, and retained-evidence disposition, including blockers. Branch deletion still requires an explicit request; remote deletion and PR merge/closure require explicit task authority and current checks.
These instructions guide agent behavior; they do not schedule cleanup or enforce retention automatically. Verify repo-specific cleanup commands before using them.
