docs: document inlined-imports: true for cross-org workflow_call scenarios

[Copilot]

Cross-org workflow_call fails at activation because the caller's GITHUB_TOKEN cannot check out a platform repo in a different organization. The inlined-imports: true frontmatter flag already solves this (embeds all imports into the lock file at compile time, eliminating the cross-org checkout), but was undocumented for this use case.

Changes

• reference/imports.md — Renamed section to "Self-Contained Lock Files" and restructured around two use cases: cross-org workflow_call (new, primary) and repository rulesets (existing). Added trade-off note: larger lock file vs. no cross-org token requirement.

• patterns/central-repo-ops.mdx — Fixed stale "How It Works" description (was showing the old github.event_name == 'workflow_call' ternary; now describes the actual resolve-host-repo / GITHUB_WORKFLOW_REF approach). Added "Cross-Organization Setup" section prescribing inlined-imports: true when caller and callee are in different orgs.

• reference/faq.md — Fixed broken anchor caused by section rename. Added FAQ entry for the cross-org checkout error with fix and link.

Example

# platform-gateway.md — hosted in org-b, called from org-a trigger files
---
on:
  workflow_call:
engine: copilot
inlined-imports: true        # embeds imports at compile time; no cross-org checkout needed
imports:
  - shared/common-tools.md
  - shared/security-setup.md
---

[Copilot]

Pull request overview

Documents inlined-imports: true as the recommended fix for cross-organization workflow_call failures caused by runtime import checkout limitations, and updates related docs/anchors accordingly.

Changes:

• Restructures imports reference to emphasize “Self-Contained Lock Files” and adds a cross-org workflow_call use case + trade-offs.
• Updates the central repo ops pattern to describe the current cross-repo checkout mechanism and adds cross-organization guidance.
• Fixes a broken FAQ anchor and adds a new FAQ entry covering the cross-org checkout error and resolution.

Show a summary per file

File	Description
docs/src/content/docs/reference/imports.md	Renames/reframes the inlined-imports: true docs around self-contained lock files and adds cross-org workflow_call guidance.
docs/src/content/docs/reference/faq.md	Updates the renamed-section anchor and adds an FAQ entry for cross-org checkout failures.
docs/src/content/docs/patterns/central-repo-ops.mdx	Refreshes “How It Works” and adds a cross-organization setup section recommending inlined-imports: true.

Copilot's findings

Tip

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

• Files reviewed: 3/3 changed files
• Comments generated: 1

[Copilot]

The Cross-Organization Setup section states that when the platform repo is in a different organization the caller’s GITHUB_TOKEN cannot check out the platform repo’s files. That failure is specifically for private (or otherwise not publicly readable) repos; a public platform repo is still checkoutable cross-org. Consider qualifying the text (e.g., “different organization and the platform repo is private/not accessible to the caller”) to avoid implying cross-org is always broken.