boring-ui: Instructions file for Codex

AGENTS.md

Read this first. Re-read after compaction.

This file is intentionally lean: it contains only hard rules and routing pointers. Detailed coding practices, workflow, architecture, and package docs live under docs/.

Hard rules

1. Human override: if the user tells you to do something, listen. The user is in charge.
2. No file deletion without explicit written permission.
3. No destructive git/filesystem ops without explicit instruction: no rm -rf, git reset --hard, git clean -fd, git push --force.
4. No secrets in git/logs. Never paste tokens into commits, comments, or logs.
5. Never push directly to remote main. Use a branch/worktree unless the owner or Kanzen trunk procedure explicitly authorizes local-main work; keep local main green.
6. Keep the canonical project checkout on main. The primary boring-ui-v2 checkout is the coordination anchor and should track origin/main, not an agent feature branch. Agents must do coding in isolated branch worktrees (which must always be created inside the .worktrees/ directory) and leave the anchor clean/current for handoffs.
7. Do not overwrite other agents' work. Investigate unexpected changes before editing.
8. Tangible progress, anti-ceremony, and honest credit.
   • No process porn: a process artifact exists only when it hard-gates a named feature or capability.
   • Feature-first ratio: process/ops beads capped at ~5% of open beads; each must name the feature work it gates.
   • Honesty is absolute: no fake tests, no weakened assertions, no false closes. A false close is reopened with an incident comment.
   • Refusal-only implementations earn partial credit, labeled (refusal-only), and never close a feature work item.
9. Session history is host app user data: Pi chat transcripts/session lists are owned by the deployed core app host, not by the sandbox/workspace runtime. Store them on the host app's durable volume via BORING_AGENT_SESSION_ROOT (typically /data/pi-sessions), not in container home/root. If host-side BORING_AGENT_WORKSPACE_ROOT=/data/workspaces, keep the host session root as sibling /data/pi-sessions unless the user explicitly chooses another mounted volume.
10. Default communication style: concise, direct, high-signal. Honor user requests for stop caveman, normal mode, or any other explicit tone change.
11. Reconcile architecture proposals with the ratified long-term plan: before proposing cross-package architecture, ontology changes, or new durable primitives, read the ratified long-term vision, architecture plan, and owner rulings linked below. State how the proposal aligns and name every conflict. Never silently supersede a frozen ruling; a conflict requires an explicit owner decision and an update to the ratified plan.