feat(community/agents): add AL agent quality guidance

- add 20 agent knowledge rules with good and bad AL samples
- clarify setup dialog shape, temporary persistence, permissions, profiles, instructions, capability registration, and interface wiring
- add the community-owned AL agents review skill
- make review fixture discovery layer-aware with custom, community, and Microsoft precedence
- document layer-aware evaluation behavior

community/knowledge/agents/instruction-structure-is-role-rules-steps.md

@@ -0,0 +1,30 @@
+---
+bc-version: [27..]
+domain: agents
+keywords: [instructions, responsibilities, guidelines, steps, setinstructions]
+technologies: [al]
+countries: [w1]
+application-area: [all]
+---
+
+# Instruction documents use responsibilities, guidelines, then ordered steps
+
+## Description
+
+The runtime treats instructions as the agent's standing prompt. A one-line goal produces inconsistent navigation. Microsoft's instruction framework is three layers: responsibilities (what the agent owns), guidelines (rules for every task), and instructions (ordered steps per task, with substeps). That structure is BC-specific, not generic prompt flavour.
+
+## Best Practice
+
+Store a document that states responsibilities, then non-negotiable guidelines (when to request a review, when not to post), then numbered steps for each task. Keep that text in the resource you pass to `SetInstructions`.
+
+See sample: `instruction-structure-is-role-rules-steps.good.al`.
+
+## Anti Pattern
+
+A single sentence such as Check customer credit for the sales order. Detection signal: instruction resource or `SetInstructions` payload with no responsibilities / guidelines / steps sections.
+
+See sample: `instruction-structure-is-role-rules-steps.bad.al`.
+
+## See also
+
+`instructions-describe-work-not-tool-ids.md` and `use-documented-instruction-keywords.md` define how to write the steps inside this structure.