Issue #3586226: Add 1.0 QA test scripts for manual testing.

Description

Adds manual QA test scripts for pre-1.0 testing of Context Control Center (#3586226).

Zoocha confirmed that documentation plus a test script in Markdown is enough for their QA process. This MR delivers that script for the external QA team.

Changes

• docs/qa/1.0-qa-scripts.md — step-by-step manual QA checklists with:
  • Environment and prerequisite setup
  • Suggested test dataset (context items, scopes, subcontext)
  • Major feature areas: overview, settings, scopes, context items, subcontext, agent configuration, context injection, context tools, moderation, revisions, usage tracking
  • Optional passes: multilingual, scheduling, importers, Canvas, Diff
  • Permissions/access control, extensions, 30-minute smoke test
  • PHPUnit commands for CI parity
  • Bug reporting guidance, common gotchas, test run log template
• docs/index.md — quick link to the new QA doc

Documentation only. No PHP, config, or behavior changes.

Closes #3586226

Testing instructions

1. Check out 3586226-ccc-qa-scripts and open docs/qa/1.0-qa-scripts.md.
2. Confirm the doc links resolve relative to other files under docs/.
3. Confirm docs/index.md links to qa/1.0-qa-scripts.md.
4. Optional: run mkdocs serve and verify the QA page renders in the docs site (the page is not yet in mkdocs.yml; link is via index only).

No runtime or PHPUnit verification required for this MR.

Checklist

• I have updated the MR title to use format: Issue #1234: My issue title.
• I have updated the MR description to include: Closes #1234
• I have performed a self-review of my own code
• I have added or updated tests, or explained in the description why this change is not covered by tests
• I have updated documentation for any new or changed functionality
• I have written testing instructions and verified them locally
• I have noted any required post-merge steps (config imports, cache rebuilds, manual changes)
• This MR contains no breaking API or hook changes, or they are explicitly documented in the description

Tests: Not applicable — documentation-only change.

Post-merge: None. Share docs/qa/1.0-qa-scripts.md with the QA team when scheduling pre-1.0 testing (~1–2 weeks lead time per issue discussion).

AI Compliance

Note

Check the one that best describes your usage, or leave all unchecked if AI was not significantly used.

• AI Assisted Code
  Mainly written by a human; AI used for autocomplete or partial generation under full human supervision.
• AI Generated Code
  Mainly generated by AI, reviewed and approved by a human before this MR was created.
• Vibe Coded
  Generated by AI and only functionally reviewed before this MR was created.