Add project-knowledge structure and templates

- Introduced new maps for navigating project knowledge, including "Current Work," "Fidelity Domain," "Fidelity Apps," "Work Items," and "People."
- Created base files for daily notes, decisions, people, systems, work items, and workstreams with defined properties and views.
- Developed templates for daily notes, decisions, meeting notes, persons, systems, work items, and workstreams to standardize documentation.
- Updated scripts and prompts to reflect the new project-knowledge directory structure.
- Removed outdated onboarding and start-here documents, consolidating relevant information into the new maps.
- Ensured all references in workflows and scripts point to the new project-knowledge paths.

project-knowledge/04-people/tauf.md

@@ -0,0 +1,44 @@
+---
+type: person
+project: fidelity
+role: CI and Jenkins support
+status: active
+teams: [ci-cd, ios-frameworks]
+topics: [jenkins, pipelines, podspec-publication, release-support]
+related: [consumer-integration, pdiap-15765]
+aliases: [Taufiqur Ashrafy, Tauf]
+tags:
+  - person
+  - fidelity
+updated: 2026-04-17
+---
+
+# Taufiqur Ashrafy
+
+## Role
+
+- CI / Jenkins support contact who helps unblock pipeline and publication issues.
+
+---
+
+## Collaboration Pattern
+
+- David reaches out to Tauf when Jenkins or release-pipeline steps need support, especially around XFlowViewMaker publication or approval/pipeline follow-through.
+- Tauf has been specifically relevant to the `PDIAP-15765` propagation work because David planned to ping him about the remaining XFlowViewMaker approval path.
+
+---
+
+## Communication Notes
+
+- Useful contact for operational release and pipeline troubleshooting.
+- David has seen podspec-repo edits happen after publication and specifically called out Tauf as someone involved in CI support around that ecosystem.
+- Often referred to informally as `Tauf`.
+- Fidelity Teams may show names in a surname-first style, so this person may appear under a different display order there.
+- In the current XFlowViewMaker propagation issue, Tauf clarified that the needed fix belongs in the podspec repo rather than FTFrameworks source, and pointed David toward removing the XFlowViewMaker version constraint for `ftaccountopen`.
+
+---
+
+## Related Context
+
+- `project-knowledge/03-context/workstreams/consumer-integration.md`
+- `project-knowledge/02-work-items/pdiap-15765.md`