e36d81f357
Fixes linker error on Linux where yaze_gfx_debug.a (performance_dashboard.cc) was calling AtlasRenderer::Get() and AtlasRenderer::GetStats() but wasn't linking against yaze_gfx_render which contains atlas_renderer.cc. Root cause: yaze_gfx_debug was only linking to yaze_gfx_types and yaze_gfx_resource, missing the yaze_gfx_render dependency. This also fixes the undefined reference errors for HttpServer methods which were already properly included in the agent.cmake source list. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
46 lines
1.3 KiB
Markdown
46 lines
1.3 KiB
Markdown
# AI Initiative Template
|
||
|
||
Use this template when kicking off a sizable AI-driven effort (infrastructure, editor refactor,
|
||
automation tooling, etc.). Keep the filled-out document alongside other planning notes and reference
|
||
it from the coordination board.
|
||
|
||
```
|
||
# <Initiative Title>
|
||
|
||
## Summary
|
||
- Lead agent/persona:
|
||
- Supporting agents:
|
||
- Problem statement:
|
||
- Success metrics:
|
||
|
||
## Scope
|
||
- In scope:
|
||
- Out of scope:
|
||
- Dependencies / upstream projects:
|
||
|
||
## Risks & Mitigations
|
||
- Risk 1 – mitigation
|
||
- Risk 2 – mitigation
|
||
|
||
## Testing & Validation
|
||
- Required test targets:
|
||
- ROM/test data requirements:
|
||
- Manual validation steps (if any):
|
||
|
||
## Documentation Impact
|
||
- Public docs to update:
|
||
- Internal docs/templates to update:
|
||
- Coordination board entry link:
|
||
- Helper scripts to use/log: `scripts/agents/smoke-build.sh`, `scripts/agents/run-tests.sh`, `scripts/agents/run-gh-workflow.sh`
|
||
|
||
## Timeline / Checkpoints
|
||
- Milestone 1 (description, ETA)
|
||
- Milestone 2 (description, ETA)
|
||
```
|
||
|
||
After filling in the template:
|
||
1. Check the coordination board for conflicts before starting work.
|
||
2. Link the initiative file from your board entries so other agents can find details without copying
|
||
sections into multiple docs.
|
||
3. Archive or mark the initiative as complete when the success metrics are met.
|