Skip to content

fix(orchestrators): restore /v2/orchestrators/portal render by importing CenteredContainer#884

Merged
DeveloperAlly merged 2 commits intodocs-v2from
copilot/fix-orchestrators-portal-loading
Apr 21, 2026
Merged

fix(orchestrators): restore /v2/orchestrators/portal render by importing CenteredContainer#884
DeveloperAlly merged 2 commits intodocs-v2from
copilot/fix-orchestrators-portal-loading

Conversation

Copy link
Copy Markdown

Copilot AI commented Apr 21, 2026

Description

/v2/orchestrators/portal was failing at runtime with Expected component 'CenteredContainer' to be defined, which prevented the page from loading. This PR resolves the missing MDX component reference in the page module.

Scope

In scope:

  • /home/runner/work/docs/docs/v2/orchestrators/portal.mdx

Out of scope:

  • Navigation/IA changes (docs.json)
  • Content rewrites or layout changes
  • Any other portal pages/components

Validation

Targeted command:

  • node operations/tests/unit/mdx.test.js --file v2/orchestrators/portal.mdx

Follow-up Tasks

none

Type of Change

  • Bug fix (fixes an issue)
  • New content (adds new documentation)
  • Content update (improves existing content)
  • Style/formatting fix
  • Information architecture change
  • Other (please describe)

Related Issues

Tracked by the linked issue in this PR thread.

Changes Made

  • MDX runtime fix
    • Added the missing CenteredContainer import used by the hero code block wrapper in the orchestrators portal page.
  • No behavioral expansion
    • Kept page structure, copy, and routing unchanged; only resolved the undefined component reference.
import { CenteredContainer } from '/snippets/components/wrappers/containers/Containers.jsx'

Testing

  • Tested locally with npm run dev
  • Verified all links work
  • Checked formatting and style
  • Reviewed against style guides
  • Screenshots (if UI changes)

Screenshots (if applicable)

Unable to capture in this sandbox due to preview/network restrictions.

Checklist

  • My changes follow the style guides
  • I've reviewed the Component Library for available components
  • I've updated related pages if needed
  • I've checked for broken links
  • My changes are clear and easy to understand
  • I've tested locally
  • I've added/updated keywords and metadata if needed

Additional Notes

This is a surgical one-line import fix to address a page-killing runtime error on a critical route.

Governance Approval

  • Approval class: Not required
  • Approver: N/A
  • Rationale: Single page-level MDX import fix; no governance-sensitive surfaces changed.
  • Evidence / decision record: /home/runner/work/docs/docs/v2/orchestrators/portal.mdx

Copy Governance Gate - L5

Complete before requesting review. Every item must be checked or the PR is not ready.

Auto-checked by CI (lint-copy.js + lint-structure.js)

  • No Tier 1 banned words or phrases
  • No unresolved {/* REVIEW: */} flags in rendered content
  • No non-USD currency outside declared regional scope
  • No empty cells in decision tables
  • pageType, audience, lastVerified present in frontmatter

Human review required

Sequence (L2)

  • Page opens with operator outcome - value kept, no conditionals
  • Majority operator path is featured before variants
  • Introduced paths are developed on-page or linked

Completeness (L3)

  • Decision aids (tables, matrices, flowcharts) are complete - no placeholders
  • Every warning or consequence is followed by a prevention action and link
  • Primary actions and URLs appear in body copy (not only in accordions)

Tone (L4)

  • No sentence ends on a hedge, disclaimer, or restatement
  • No section ends with a Note that apologises rather than forward-points

Brief compliance

  • L0 (Q1-Q4) was completed before drafting
  • L1 persona mapping table was completed before drafting

If any structural item fails: fix before requesting review. Do not ask a reviewer to identify the issue.

If the same section fails review twice: do not attempt a third fix. Escalate to the documentation lead for L6 diagnostic.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • 208.67.222.222
    • Triggering command: REDACTED, pid is -1 (packet block)
  • api.ipify.org
    • Triggering command: /opt/hostedtoolcache/node/24.14.1/x64/bin/node node --no-deprecation /opt/hostedtoolcache/node/24.14.1/x64/lib/node_modules/mintlify/node_modules/@mintlify/cli/bin/start.js dev --port 3001 /concepts/r-role.mdx p/bin/git ance-framework.mnode (dns block)
    • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node --no-deprecation /opt/hostedtoolcache/node/24.14.1/x64/lib/node_modules/mintlify/node_modules/@mintlify/cli/bin/start.js dev --port 38871 --no-open /usr/bin/git ls/product-writish --global uname git ls-f�� -- operations/scripts ndor/bin/git e-extension-0.0.awk --local ndor/bin/unzip git (dns block)
  • captive.apple.com
    • Triggering command: /opt/hostedtoolcache/node/24.14.1/x64/bin/node node --no-deprecation /opt/hostedtoolcache/node/24.14.1/x64/lib/node_modules/mintlify/node_modules/@mintlify/cli/bin/start.js dev --port 3001 /concepts/r-role.mdx p/bin/git ance-framework.mnode (dns block)
    • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node --no-deprecation /opt/hostedtoolcache/node/24.14.1/x64/lib/node_modules/mintlify/node_modules/@mintlify/cli/bin/start.js dev --port 38871 --no-open /usr/bin/git ls/product-writish --global uname git ls-f�� -- operations/scripts ndor/bin/git e-extension-0.0.awk --local ndor/bin/unzip git (dns block)
  • icanhazip.com
    • Triggering command: /opt/hostedtoolcache/node/24.14.1/x64/bin/node node --no-deprecation /opt/hostedtoolcache/node/24.14.1/x64/lib/node_modules/mintlify/node_modules/@mintlify/cli/bin/start.js dev --port 3001 /concepts/r-role.mdx p/bin/git ance-framework.mnode (dns block)
    • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node --no-deprecation /opt/hostedtoolcache/node/24.14.1/x64/lib/node_modules/mintlify/node_modules/@mintlify/cli/bin/start.js dev --port 38871 --no-open /usr/bin/git ls/product-writish --global uname git ls-f�� -- operations/scripts ndor/bin/git e-extension-0.0.awk --local ndor/bin/unzip git (dns block)
  • ph.mintlify.com
    • Triggering command: /opt/hostedtoolcache/node/24.14.1/x64/bin/node node --no-deprecation /opt/hostedtoolcache/node/24.14.1/x64/lib/node_modules/mintlify/node_modules/@mintlify/cli/bin/start.js dev --port 3001 /concepts/r-role.mdx p/bin/git ance-framework.mnode (dns block)
    • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node --no-deprecation /opt/hostedtoolcache/node/24.14.1/x64/lib/node_modules/mintlify/node_modules/@mintlify/cli/bin/start.js dev --port 38871 --no-open /usr/bin/git ls/product-writish --global uname git ls-f�� -- operations/scripts ndor/bin/git e-extension-0.0.awk --local ndor/bin/unzip git (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Copilot AI linked an issue Apr 21, 2026 that may be closed by this pull request
2 tasks
Copilot AI changed the title [WIP] Fix orchestrators portal page loading issue fix(orchestrators): restore /v2/orchestrators/portal render by importing CenteredContainer Apr 21, 2026
Copilot AI requested a review from DeveloperAlly April 21, 2026 08:28
@DeveloperAlly DeveloperAlly marked this pull request as ready for review April 21, 2026 09:38
@DeveloperAlly DeveloperAlly merged commit 109be77 into docs-v2 Apr 21, 2026
2 checks passed
@DeveloperAlly DeveloperAlly deleted the copilot/fix-orchestrators-portal-loading branch April 21, 2026 09:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Orchestrators Portal Page does not load

2 participants