Add daily logs and templates for project fidelity

- 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.

workspaces/fidelity/project-knowledge/06-daily/2026-04-13.md

@@ -0,0 +1,27 @@
+---
+type: daily
+project: fidelity
+date: 2026-04-13
+focus: [xflow-swiftui-migration, ao-discourse, rest-migration]
+work-items: [pdiap-14859, pdiap-15765, pdiap-15838]
+blockers: []
+updated: 2026-04-16
+tags:
+  - daily
+  - fidelity
+---
+# 2026-04-13
+
+## Standup Context
+
+- Corrected the approved title for `PDIAP-14859` to `Spike - Research strategy to remove final UIKit wrapping from XFlowSDK and XFlowViewMaker without disrupting consumer implementation`.
+- Manual clarification for Monday standup: reference Friday work rather than the prior calendar day.
+- Friday update for `PDIAP-14859`: created a draft rollout document for removing UIKit in favor of a SwiftUI-only path, including feature-flag planning.
+- Today update: publish the rollout document for `PDIAP-14859` and continue with `PDIAP-15838` `Remove Apollo for iOS`.
+- Standups should include story titles, not only Jira IDs, when the title is available.
+
+## Mattermost Sync
+
+- `PDIAP-14859`: sent Jeff the rollout draft for review after updating it around the global feature flag, broad `XQ1` validation, and the consumer-facing rollout flow.
+- Jeff replied that he will review the `PDIAP-14859` document this morning.
+- For `PDIAP-15765`, Jeff approved sending the config clarification that `CheckIdentity` was already correct and that `TeenIdentityCheck` needed the `validations` root key plus `eighteenOrAbove` inside `validation-rules`; the message was sent with an expected validation snippet.