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/david-delagneau.md

@@ -0,0 +1,33 @@
+---
+type: person
+project: fidelity
+role: collaborator
+status: active
+updated: 2026-04-16
+tags:
+  - person
+  - fidelity
+---
+# David Delagneau
+
+## Role
+
+Repeated Fidelity collaborator in historical Slack threads.
+
+---
+
+## Known Context
+
+- Appears heavily in pipeline, Jenkins, SonarQube, test-reporting, and release-process work
+- Later historical activity also includes Sparta SDK proof-of-concept implementation and framework setup work
+- Often provides implementation updates, process notes, and operational debugging context to Jeff
+- Frequently handled CI/CD, Jenkins, reporting, and repo/setup tasks while Norman focused on SDK and consumer debugging
+- Later archive activity shows him taking lead on SpartaSDK setup, JSON decoding, and repo/bootstrap work
+
+---
+
+## Guidance
+
+- Treat David as a relevant source for CI/CD, release-process, and framework-setup context
+- Treat David as especially relevant for Jenkins, SonarQube, Pod/repo setup, and Sparta SDK bootstrapping context
+- If future context clarifies the formal role or team, update this file directly