Reorganize ff-oce prompt

[noencke]

Broadly, this re-organizes the prompt such that IDs, names, "things-you-want-to-reference" are all at the top, and more details about behavior come later. It also adds FF Hot and AFR to the ICM team list. Other than that addition, the changes should be organization, not additive or subtractive.

• Added Quick Reference section at the top with centralized lookup tables:
  • IcM Teams: all 3 OCE teams with IDs. This is a "bug fix" - prior to this, the agent was only looking up the FFC ICM.
  • Severity/SLA table
  • ADO Repos: ff_internal with all IDs
  • ADO Pipeline Definitions: defs with key stages
  • ADO Build API result codes
  • Teams Channels: FF Hot channel IDs
  • Access Groups: all prerequisite groups in one table
  • Key Links: FRS escalation, wiki URLs
• Consolidated Finding Internal Documentation: same content, tighter
• Reorganized OCE Tasks: 9 focused subsections (down from 11):
  • Merged "Shift Logistics & Scheduling" + "Shift Handoff" → Shift Logistics & Handoff
  • Merged "Kusto Telemetry Investigation" into Partner Incident Support (it was just 1 line)
  • Merged "Automation Collateral Rotation" + "Proactive Telemetry Monitoring" → Proactive Monitoring & Maintenance
  • All reference data (IDs, constants) moved to Quick Reference: tasks now focus on what to do

[Copilot]

Pull request overview

Reorganizes the Fluid Framework OCE agent prompt to centralize “lookup” data (IDs, constants, links) in a new Quick Reference section and move procedural guidance into focused task sections.

Changes:

• Added a “Quick Reference” section (IcM teams/IDs, SLAs, ADO repo/pipelines, result codes, Teams channel IDs, access groups, key links).
• Restructured and consolidated the OCE task list into fewer, more focused subsections.
• Updated the IcM team coverage to include FF Hot and Azure Fluid Relay Client in addition to Fluid Framework Client.

[github-actions]

🔗 No broken links found! ✅

Your attention to detail is admirable.

linkcheck output

> fluid-framework-docs-site@0.0.0 ci:check-links /home/runner/work/FluidFramework/FluidFramework/docs
> start-server-and-test "npm run serve -- --no-open" 3000 check-links

1: starting server using command "npm run serve -- --no-open"
and when url "[ 'http://127.0.0.1:3000' ]" is responding with HTTP status code 200
running tests using command "npm run check-links"


> fluid-framework-docs-site@0.0.0 serve
> docusaurus serve --no-open

[SUCCESS] Serving "build" directory at: http://localhost:3000/

> fluid-framework-docs-site@0.0.0 check-links
> linkcheck http://localhost:3000 --skip-file skipped-urls.txt

Crawling...

Stats:
  272172 links
    1863 destination URLs
    2108 URLs ignored
       0 warnings
       0 errors