- Add invite code display and binding functionality via API - Fix notification unread count sync on auth state change - Improve notification mark read with server state validation - Add auth state listener to trigger notification refresh - Add YaoCoinConverter for coin-to-yao type conversion - Remove YaoLegend from divination screens (UI cleanup) - Abbreviate relation labels in yao detail view - Add re-register notice to account delete screen - Update 'coins' terminology to 'points' in localization - Fix backend points consumption to only run in CHAT mode - Add HttpxAuthNoiseFilter to suppress auth endpoint logging - Fix notification static_schema import path - Add test coverage for notification bloc error handling - Update AGENTS.md page header rules and image handling - Delete deprecated run-dev.sh script
2.4 KiB
Project AGENTS Router
Root AGENTS.md is routing + cross-domain policy only.
Do not place backend/frontend implementation details here.
Scope
- Applies to repository root and cross-domain tasks.
- Subdomain rules:
backend/AGENTS.md,apps/AGENTS.md. - If rules conflict, use the stricter one.
Rule Order
- System / developer / platform safety instructions
- Workspace runtime rules (
AGENTS.md+rules/*) - This file (routing + project-level constraints)
- Subdomain rules (backend/apps)
Mandatory Routing
backend/**must followbackend/AGENTS.md.apps/**must followapps/AGENTS.md.- Cross-domain changes must satisfy all relevant subdomain rules.
infra/**follows this file plusinfra/conventions.
Project-Wide Constraints
- Default development branch is
dev; do not develop directly onmain. - Never push unless explicitly requested by the user.
- Keep AGENTS layered and lean: shared rules at root, domain rules in sub-AGENTS.
- No Error Swallowing: All exceptions must propagate or be converted to typed errors. Never catch an exception, log it, and silently continue. This destroys debuggability.
Protocol Source of Truth
docs/protocols/ is the single source of truth for protocol and data format.
- Update protocol docs before changing data/API/UI contracts.
- Document compatibility strategy (backward-compatible vs migration).
- Keep frontend/backend implementations aligned with documented protocol.
Database Access
When viewing data in the database, use supabase mcp tools (supabase_execute_sql, supabase_list_tables, etc.) instead of direct queries or other methods.
Image Handling
When reading images, check whether the model has native multimodal capability first. If it does, use Read tool to read images directly. If it does not, fall back to understand_image tool. Only use Read tool for non-image files.
Trellis Instructions
These instructions are for AI assistants working in this project.
Use the /trellis:start command when starting a new session to:
- Initialize your developer identity
- Understand current project context
- Read relevant guidelines
Use @/.trellis/ to learn:
- Development workflow (
workflow.md) - Project structure guidelines (
spec/) - Developer workspace (
workspace/)
Keep this managed block so 'trellis update' can refresh the instructions.