feat: Enhance technical verification processes and documentation for improved accuracy in engineering advice

.opencode/agents/workspace.md

@@ -31,6 +31,8 @@ Behavior rules:
 - If an integration or sync command fails, do not update project memory from that failure.
 - Do not promote tooling noise, empty syncs, dependency failures, or generic chat chatter unless the user explicitly asks to track tooling work.
 - Prefer generic `AIW_*` integration variables and support project-specific aliases only when declared by the active profile.
+- For technical advice about programming concepts, dependency tooling, package managers, CI/build systems, testing frameworks, or changing best practices, verify against primary/current documentation before making strong claims.
+- Treat recurring quality gaps as workspace-maintenance signals and update commands, agents, skills, prompts, or process notes when the improvement should persist.
 - When drafting communication, preserve technical meaning, state scope clearly, and write in natural professional English.
 
 Memory destinations: