reason: Trellis workflow and task execution rules


reason: Backend development constraints and verification baseline


reason: Frontend rendering and app-layer conventions


reason: Cross-layer contract checklist for protocol/backend/frontend changes


reason: Project routing, protocol-source-of-truth, and git safety constraints


reason: Frontend AG-UI and shared rendering rules


reason: Current tool registry and tool name mapping


reason: Current direct Python tool registration path


reason: Worker enabled_tools loading from system agent config


reason: Current worker output contract includes ui_hints


reason: Current TEXT_MESSAGE_END payload still emits ui_hints


reason: History path still compiles ui_hints into ui_schema


reason: Frontend event/history parser consumes ui_schema from backend


reason: Current UI renderer consumes compiled ui_schema


reason: Current worker ui_hints -> ui_schema data-flow documentation


reason: SSE payload contract for worker and tool events


reason: Run-agent contract and ui_schema references


reason: HTTP endpoint contract for history and events payloads