- Created daily log entries for May 13, 14, 18, 19, 20, and 21, capturing work done, findings, and next steps.
- Established a daily logs index for easy navigation of daily notes.
- Developed templates for daily logs, decisions, meeting notes, people, systems, and work items to standardize documentation.
- Introduced base files for filtering and displaying various types of project knowledge, including daily notes, decisions, people, systems, work items, and workstreams.
- Added maps for current work, fidelity apps, and fidelity domain to enhance project navigation and context.
Deprecate GraphQL and Apollo safely while preserving behavior through REST-backed flows.
Stable Constraints
REST is behind a feature flag.
GraphQL remains the default fallback unless confirmed otherwise.
REST should never be assumed active by default.
Migration work must preserve behavior parity before removing Apollo-related code.
What Matters In Practice
Validation must clarify whether the tested path is actually using REST or still falling back to GraphQL.
Story scope should distinguish:
transport migration work
feature-flag cleanup
tests and mocks tied to Apollo/GraphQL
Communication should avoid implying the migration is complete before the fallback path is removed.
Historical Signals From Slack
Historical Slack evidence around release and dependency work reinforces that transport or dependency changes often require consumer validation, not just local SDK changes.
Some dependency and pipeline issues complicated migration-related rollout even when the technical change itself was understood.
david.delagneau
1ad707373a