adding/updating the Q1-2026 report

[danbaruka]

Description

This PR adds the Shared DevEx Report to the Open Source Committee (OSC) for Q1 2026, as the common document produced by the Developer Advocates for OSC reporting.

• What problem does this PR solve? The OSC requires periodic Developer Experience Working Group progress reports (every four weeks) and a record of DevEx pain points plus a plan for improvement. This report fulfils that requirement for Q1 2026.
• What is the purpose of this change? To submit the Q1-2026 DevEx status, resolved items (session discoverability, changelog discoverability, release cadence), remaining pain points, community/repo engagement (8+ new contributors, new PRs), draft documentation (Blaze SDK + Yaci Store integration PR Add Blaze SDK + Yaci Store integration guide #186), and ongoing improvements in one shared document for the OSC.

Related Issue

N/A (or link an issue if one exists).

Type of Change

Check the type of change this PR introduces:

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactor (improves code structure or readability without changing functionality)
• Other (please describe):

Changes Made

• Added: DA Milestones/DevEx-WG-Overview/Q1-2026.md — Shared DevEx Report to OSC for Q1 2026, including:
  • Acceptance criteria (progress reporting, pain points & strategy, common document)
  • DevEx WG overview (mission, meeting cadence, Q1-2026 session schedule, coordination, participants)
  • Current DevEx status (onboarding, documentation quality, session participation & accessibility, website & infrastructure, community & repository engagement)
  • Resolved in Q1 2026 (session discoverability, changelog discoverability, release cadence)
  • Pain points to address and plan for improvement (for OSC Open Source Strategy)
  • Draft documentation for Core Cardano repositories (Blaze SDK + Yaci Store integration — PR Add Blaze SDK + Yaci Store integration guide #186)
  • Ongoing improvements

Checklist

Ensure you have completed the following steps before submitting your PR:

• My code follows the project's coding style and guidelines.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation (if applicable).
• My changes generate no new warnings or errors.
• I have added tests that prove my fix is effective or that my feature works.
• I have checked for merge conflicts.
• I have rebased my branch onto the latest main or master branch.