docs: Add CoprrectionOps

[mnkiefer]

• Adds new design pattern CorrectionOps to improve workflows using trusted human corrections without retraining models.

[Copilot]

Pull request overview

Adds new documentation covering organization-scale workflow practices and introduces the CorrectionOps design pattern for improving workflows using trusted human corrections (without retraining models).

Changes:

• Add new CorrectionOps pattern documentation page.
• Add new Organization Practices section with pages for Safe Rollout and Sharing Workflows.
• Update glossary, sidebar navigation, and redirects to surface the new docs and route legacy URLs.

Show a summary per file

File	Description
docs/src/content/docs/reference/glossary.md	Adds glossary entries for CorrectionOps and organization-practice terms.
docs/src/content/docs/patterns/correction-ops.md	New pattern page describing CorrectionOps and a starter architecture.
docs/src/content/docs/organization-practices/index.mdx	New landing page for the Organization Practices docs section.
docs/src/content/docs/organization-practices/safe-rollout.md	New guidance on staged → shadow → direct-write rollout progression.
docs/src/content/docs/organization-practices/sharing-workflows.md	New guidance on workflow sharing models and governance questions.
docs/astro.config.mjs	Adds redirects for legacy shadow URLs and adds sidebar entries for new sections/pages.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comments suppressed due to low confidence (2)

docs/src/content/docs/patterns/correction-ops.md:24

• Spelling is inconsistent with the rest of the docs: this repo predominantly uses US spelling “labeling” (single “l”). Consider changing “labelling” → “labeling” here.

Typical fits include labelling and classification, routing and prioritization, moderation and approvals, and summaries or recommendations that humans later correct.

docs/src/content/docs/patterns/correction-ops.md:279

• Spelling is inconsistent with the rest of the docs: this repo predominantly uses US spelling “labeling” (single “l”). Consider changing “labelling” → “labeling” here.

Discussion labelling, routing, moderation, prioritization, approvals, and summaries can all reuse this shape. The production object changes, but the CorrectionOps setup does not.

• Files reviewed: 6/6 changed files
• Comments generated: 4

[github-actions]

Hey @mnkiefer 👋 — thanks for putting together this documentation on CorrectionOps! The content itself looks well-structured and on-topic. However, there are a couple of things to address before this can move forward:

• Contribution process — Per the project's CONTRIBUTING.md, non-core team members should not submit pull requests directly. Instead, the preferred flow is to open a detailed issue with an agentic plan, and a core team member will implement it using a coding agent.
• WIP status + title typo — The PR is still marked as a draft/WIP and the title contains a typo ("CoprrectionOps" → "CorrectionOps").

To move this contribution forward, please consider closing this PR and opening an issue instead with your documentation plan. Here's a prompt you can hand to your AI coding agent to help:

Create a GitHub issue for the github/gh-aw repository proposing new documentation for the CorrectionOps organization practice.

The issue should include:
1. A description of what CorrectionOps means in the context of agentic workflows
2. The proposed documentation structure (sections, pages, nav entries)
3. Key concepts to cover: safe rollout, workflow sharing, correction patterns
4. Specific file paths where new markdown pages should be created under docs/
5. Any redirects or glossary entries needed

Follow the Diátaxis documentation framework used by this project. Provide a complete, step-by-step implementation plan so a core team member can hand it directly to a coding agent.

Generated by Contribution Check · ● 1M · ◷

[mnkiefer]

• Closing in favor of docs: Add Sharing Workflows guide #28789