Issue #3586395: Document the AI Context role and permission matrix for 1.0.

Description

Follow-up to #3586358 (closed).

The current permission model is sufficient for 1.0; what was missing was site-builder guidance. This MR documents the beta5 role/permission matrix and clarifies the two permissions most often mixed up on the permissions form.

Changes

Documentation (docs/developers/configuration.md)

• Add consumer, author, editor, and administrator role bundles
• Add consumer vs CCC editorial access comparison table
• Add role capability matrix
• Document all 15 module permissions plus ai_context_editorial workflow transition permissions
• Document administrative route requirements
• Link 1.1 follow-up #3586357

Permission label polish (ai_context.permissions.yml)

• Rename display title: View AI Context Items in CCC (view ai context items)
• Rename display title: Use Published AI Context in AI Features (access published ai context)
• Clarify descriptions; machine permission names unchanged

Related doc updates

• README.md trust-model wording
• docs/features/overview.md permission table

Notes

• No access-behavior, routing, or permission machine-name changes
• No new permissions added
• Existing automated access coverage (AiContextAccessControlMatrixTest, list/usage functional tests) remains the behavioral source of truth
• Canonical published-item viewing for the consumer permission is documented today; stricter consume-vs-UI separation is tracked in #3586357 for 1.1

Closes #3586395 (closed)

Testing instructions

1. Check out branch 3586395-permission-matrix-docs on the issue fork.
2. Run ./lint.sh from web/modules/contrib/ai_context.
3. Open /admin/people/permissions/module/ai_context and confirm the two renamed permission titles appear:
   • View AI Context Items in CCC
   • Use Published AI Context in AI Features
4. Read docs/developers/configuration.md → Permissions and verify:
   • consumer, author, editor, and administrator bundles are present
   • workflow transition permissions are listed
   • consumer vs listing distinction is clear
   • administrator bundle notes that listing still requires view ai context items
5. Spot-check README.md and docs/features/overview.md for updated permission labels.

No functional behavior change is expected beyond updated permission labels on the permissions form.

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 added. Docs-only change plus permission title/description updates. Existing access-matrix and functional tests cover the underlying permission behavior.

Post-merge: None required beyond normal release notes/changelog mention if desired.

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.