Frame app review as a plugin example

Remove historical naming and external orchestrator references, and present the app-folder review as one example of the broader host-native skill pattern.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

docs/README.md

@@ -3,6 +3,6 @@
 - [How agents consume BCQuality](agent-consumption.md) explains the operational
   flow from Entry dispatch through structured findings and integration.
 - [Build a lightweight standalone review runner](standalone-runner.md) explains
-  the walk-up app-folder flow and how an external runner can add model
+  one concrete walk-up skill flow and how an external runner can add model
   selection, concurrency, retries, and telemetry without moving orchestration
   into BCQuality.

docs/agent-consumption.md

@@ -1,13 +1,16 @@
 # How agents consume BCQuality
 
-BCQuality is content — knowledge files and skills. It is consumed by agents that live elsewhere (AL-Go, a VS Code extension, a GitHub Agent invocation, etc.). This document explains the end-to-end flow, so that skill authors, orchestrator maintainers, and contributors share one mental model.
+BCQuality is content — knowledge files and skills. It is consumed by agents
+supplied by a host or orchestrator. This document explains the end-to-end flow
+so that skill authors, orchestrator maintainers, and contributors share one
+mental model.
 
 For the high-level framing and repo structure, start with the
 [README](../README.md). This document is the operational view.
 
 ## The actors
 
-- **Orchestrator** — the tool that triggers work (e.g. AL-Go on a pull request, or a VS Code extension on save). Lives *outside* BCQuality. Knows *when* to run something, not *what* to run.
+- **Orchestrator** — the tool that triggers work. Lives *outside* BCQuality. Knows *when* to run something, not *what* to run.
 - **Agent** — an LLM-driven process spawned by the orchestrator. The agent has no built-in knowledge of BC or of BCQuality's conventions. It knows how to read instructions and call tools.
 - **BCQuality repo** — two kinds of content:
   - **Global skills** in `/skills/` — the `entry.md` entry-point skill plus the READ · DO · WRITE contracts that govern the rest of the repo.
@@ -21,7 +24,7 @@ action skill: it creates the task context and enters the same flow at Entry.
 
 ```mermaid
 flowchart LR
-    O[Orchestrator<br/>AL-Go] -->|1 trigger + task context| A[Agent]
+    O[Host or orchestrator] -->|1 trigger + task context| A[Agent]
     A -->|2 invoke entry.md| E[Entry<br/>routing skill]
     E -->|3 dispatch record| A
     A -->|4 invoke dispatched skill| S[Action skill<br/>e.g. al-code-review]

docs/standalone-runner.md

@@ -97,7 +97,6 @@ A compatible runner:
 - preserves knowledge paths verbatim and verifies references before publishing;
 - records the BCQuality commit or release used for the run.
 
-BC-ALAgents, AL-Go, a Copilot custom agent, or a small host-native plugin can
-all implement this runner contract. They remain optional consumers:
-BCQuality's knowledge and skills stay independent of their orchestration
-choices.
+A CI integration, custom agent, or small host-native plugin can implement this
+runner contract. These remain optional consumers: BCQuality's knowledge and
+skills stay independent of their orchestration choices.