Platform Breaking Changes and Debugging Rundown Specification

Role: Senior Developer Experience Architect & Platform Ecosystem Lead

Context

• Upstream framework and runtime changelogs: {{runtime_version_changelogs}}
• Scheduled deprecation schedules and breaking APIs: {{deprecated_apis}}
• Consuming engineering personas across services: {{ecosystem_developer_personas}}
• Observability and profiling tool updates: {{debugging_toolchain_updates}}
• Migration effort tolerance thresholds: {{migration_effort_threshold}}
• Reader retention and action telemetry objectives: {{subscriber_engagement_goals}}

Task

Draft a formal technical specification for a platform engineering release bulletin that translates complex dependency upgrades, runtime changes, and debugging recipes into zero-friction developer migration workflows.

Method

1. Categorize {{runtime_version_changelogs}} by architectural risk, binary compatibility, and operational blast radius.
2. Map {{deprecated_apis}} directly to step-by-step migration recipes designed for {{ecosystem_developer_personas}}.
3. Define debugging and observability playbooks highlighting key changes in {{debugging_toolchain_updates}}.
4. Establish modular section schemas that isolate blocking upgrades from optional performance optimizations.
5. Calibrate migration guide complexity against {{migration_effort_threshold}} to prevent cognitive fatigue.
6. Define metadata taxonomy including semantic version badges, compiler flags, and deprecation timers.
7. Formulate instrumentation hooks to measure subscriber engagement and migration adoption per {{subscriber_engagement_goals}}.

Constraints

• Every highlighted API deprecation MUST include an immediate Before vs. After code diff.
• Bulletins MUST NOT recommend unversioned dependencies or unverified compiler flag tweaks.
• Structural layouts must enforce a strict priority hierarchy with breaking issues placed first.
• Explanations of complex stack-trace changes must include reproduction snippets.
• Output must specify an issue-level semantic versioning indicator.

Output format

• Section 1: Bulletin Information Architecture (taxonomy, visual hierarchy, module constraints)
• Section 2: Code Diff & Migration Specification (syntax rules, AST codemod guidance, test assertions)
• Section 3: Debugging Playbook Layout Spec (profiling runbook schema, flamegraph visualization rules)
• Section 4: Production Publication Checklist & Metric Targets (sign-off pipeline, adoption telemetry)

Self-review

• Verify all variables are referenced and contextually applied to developer enablement.
• Check that mandatory code diff requirements are formally encoded in the output contract.
• Validate that debugging recipes contain executable, verifiable triage patterns.