booley-add-to-qalisted

# Add behavior to Booley public QA Use this skill only when the user invokes it explicitly. Treat the prose following the invocation as a candidate requirement, not as authority for the expected behavior. ## Read the contract Read [`coverage.yaml`](../coverage.yaml), the relevant production Scenario, and [`scenario.schema.json`](../scenario.schema.json), which is the structural authority. Read the shared [protocol](../doc/PROTOCOL.md) only when the proposed change depends on or changes shared execution behavior. For a Runtime Attachment or Waveform Viewer requirement, also read the [GUI Check example](references/gui-check-example.md). ## Classify the requirement Search Capabilities and Checks by meaning, not only by matching words. Produce exactly one classification: - `already-covered`: existing Checks fully exercise the behavior; make no changes and identify them. - `existing-capability`: the behavior belongs to an existing Capability but needs one or more new Checks. - `new-capability`: the behavior is a distinct supported product Capability and needs both a `coverage.yaml` entry and one or more Checks. - `not-ready`: the behavior lacks an authoritative public expectation, observable evidence, a suitable Scenario, or another decision needed to write a trustworthy Check. State what is missing without inventing it. Keep independently observable expectations in separate Checks. Do not weaken, merge, remove, or exclude existing coverage to accommodate the req