{
“markdown”: ”# 🛸 DOCSKURBY DIGEST: test-topic-123\n\n🚀 Quick Start\nThe string test-topic-123 is a generic structural placeholder and the namesake for “The Strict Naming & Runtime Enforcer” agent. This agent ruthlessly enforces explicit naming and cross-domain robustness.\n\n🔧 Configuration\nAudit configuration files and tests to replace generic strings.\n\n| 🛠️ Target | ✅ Replacement Strategy |\n| :--- | :--- |\n| Naming Format | Replace placeholders with namespaced identifiers like [env].[region].[service].[data-type]. |\n| Versioning & Casing | Append explicit versioning (v1) and enforce strict lowercase. |\n| Automated Cleanup | Automate temporary infrastructure cleanup via TTL (auto_ttl_days: 1). |\n| Agent Parameters | Inject personas directly into the prompt string. The role kwarg is invalid for agent(). |\n\n📦 Dependencies\n| Component | Integration Method |\n| :--- | :--- |\n| Uvicorn / Discord.py | Co-locate Uvicorn by disabling native signals (server.install_signal_handlers = lambda: None). |\n| Telemetry Context | Carry context via Node/Bun AsyncLocalStorage and use safe lazy dynamic imports. |\n| WordPress Builds | Edit JS/PHP in src/ and always run npm run build from the plugin root. |\n| WP-CLI | Run sudo -u www-data wp to prevent permissions errors. |\n\n💡 Best Practices\n* Structured Naming: Replace generic placeholders with structured identifiers. Maintain executable documentation.\n* Test Independence: Assert strictly on behavioral outcomes and isolate shared state.\n* Tooling Consistency: Ignore quartz/local-plugins in workspace configs to prevent overwrite loops.\n* UI Parsing: Strip emojis in Quartz using regex mapFn and wrap Mermaid edge labels in double quotes (-->|\"label\"|).\n* OMP Troubleshooting: Execute debugging CLI commands under a real PTY (pty: true).\n\n🚨 Gotchas / Warnings\n* Generic Placeholders (test-topic-123): NEVER deploy generic strings in shared/production environments. They obscure observability and introduce collision risks.\n* Read-Only Reviewers: Agents tagged agent_type=\"reviewer\" cannot write to the filesystem. NEVER attempt I/O with them.\n* Shared State: Designing tests that rely on shared state from previous tests will lead to cascading failures.\n* Direct Build Edits: Modifying build/ files in WordPress directly is an anti-pattern and will be overwritten.\n\n🔍 Research / References\n* Workspace Source: test-topic-123-perfected.md\n* Workspace Profile: test-topic-123-profile.md”
}