cleanup: strip dead notification chain refs from docs

docs/onboarding-checklist.md

@@ -10,33 +10,22 @@
 | # | Requirement | Why |
 |---|---|---|
 | 1 | **Enable Dependency Graph** (Settings → Code security) | `reusable-dependency-review` hard-fails without it |
-| 2 | Secrets available: `OCTO_BOT_TOKEN`, `PROJECT_TOKEN`, `TRIAGE_WEBHOOK_URL` | IM notify, board writes, triage agent. `TRIAGE_WEBHOOK_URL` is an org-level secret. |
-| 3 | Know your repo's **IM `project_group_id`** (32-hex) | `octo-ci-status` / `octo-pr-review-feed` route to it; each repo has its own |
-| 4 | Your main CI workflow is named **`CI`** | `octo-ci-status` matches it via `workflow_run` |
+| 2 | Secrets available: `PROJECT_TOKEN` | board writes |
 
 ## Starter templates (recommended)
 
 Pick from Actions → New workflow:
 - **Octo — Security suite** — weekly CodeQL + per-PR dependency-review + secret-scan (set `language`)
 - **Octo — Repo governance** — history-check, pr-title-lint, labeler, stale
-- **Octo — Issue automation** — welcome + add-to-board + IM notify + triage webhook
 - **Octo — Release drafter** — rolling draft release
 
-## Known gotchas (learned from the cc-channel-octo onboarding experiment)
-
-1. **`octo-issue-notify` MUST forward `TRIAGE_WEBHOOK_URL`.** The older caller
-   template only passed `OCTO_BOT_TOKEN`, so the triage webhook was silently
-   skipped and the agent never ran. The `secrets:` block must include:
-   ```yaml
-   secrets:
-     OCTO_BOT_TOKEN: ${{ secrets.OCTO_BOT_TOKEN }}
-     TRIAGE_WEBHOOK_URL: ${{ secrets.TRIAGE_WEBHOOK_URL }}
-   ```
-2. **`pull_request_target` callers have a one-PR delay.** pr-title-lint, labeler,
+## Known gotchas
+
+1. **`pull_request_target` callers have a one-PR delay.** pr-title-lint, labeler,
    pr-welcome, check-sprint, pr-review read the workflow definition from the
    *base* branch — they do not run on the PR that first adds them. They take
    effect on the next PR after merge.
-3. **CodeQL is weekly-only + high-input-surface repos only.** Don't add per-PR
+2. **CodeQL is weekly-only + high-input-surface repos only.** Don't add per-PR
    CodeQL; per-PR breadth is your own CI's `gosec`/`eslint`. Library/tool/mobile
    repos don't run CodeQL at all.
 

docs/workflow-architecture.md

@@ -1,5 +1,13 @@
 # Mininglamp-OSS — CI/CD & Automation Architecture
 
+> **2026-06-27 update — Plane 6 notification chain removed.** The IM
+> notification chain (`octo-ci-status`, `octo-issue-notify`, `octo-pr-result-notify`,
+> `octo-pr-review-feed`, `octo-pr-review-feed-comment`, and the shared
+> `actions/octo-notify` composite action) was decommissioned org-wide. Issue/PR
+> automation now runs through cron-driven multica autopilots; CI state changes
+> no longer push to IM. Sections below referring to those workflows are
+> historical context only — do not use them as a target for new work.
+>
 > The blueprint for every automation under the organization: reusable
 > workflows, their triggers, how they are versioned and distributed, and how
 > local git hooks relate to (but are **not** part of) the central system.
@@ -79,7 +87,7 @@ contend for another workflow's source of truth.
 | **3 — Supply chain / release** | "How is it shipped?" | `reusable-release-drafter`, `reusable-release-publish` |
 | **4 — Repository governance** | "Is the repo tidy & well-formed?" | `reusable-history-check`, `reusable-pr-labeler`, `reusable-stale`, `reusable-pr-title-lint`, `workflow-sanity` |
 | **5 — Project board** | "Project management" | `auto-add-to-project`, `reusable-check-sprint` |
-| **6 — Community & notification** | "How do we talk to humans?" | `issue-welcome`, `octo-ci-status`, `octo-issue-notify`, `octo-pr-result-notify`, `octo-pr-review-feed` + shared `actions/octo-notify` |
+| **6 — Community & notification** | "How do we talk to humans?" | `issue-welcome` (the rest of Plane 6 — `octo-ci-status` / `octo-issue-notify` / `octo-pr-result-notify` / `octo-pr-review-feed` / `octo-notify` — was removed 2026-06-27) |
 
 ### Legend for state below
 - ✅ exists today, keep as-is