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/03-context/systems/iosinstaller.md

@@ -0,0 +1,50 @@
+---
+type: system
+project: fidelity
+status: active
+systems:
+  - fid4
+  - artifactory
+workstreams:
+  - consumer-integration
+people: []
+related:
+  - consumer-integration
+  - fid4
+  - artifactory
+tags:
+  - system
+  - fidelity
+updated: 2026-04-17
+aliases:
+  - Artifactory IOS Build Installer
+---
+
+# iOSInstaller
+
+## Role
+
+- Internal Fidelity app used to inspect distributed mobile builds.
+- Current known use: download App Store/internal builds and inspect the build's `Podfile.lock`.
+
+---
+
+## Stable Patterns
+
+- Useful when the repo does not keep `Podfile.lock` in Git but you still need to inspect what dependencies a shipped build used.
+- Can support version-validation and reproduction work for Fid4 / flagship investigations.
+- This is a base note; capture exact access patterns, URLs, and screenshots gradually as they become important.
+
+---
+
+## Risks
+
+- Build snapshots alone may still be insufficient for exact reproduction if the private podspec repo changed after the build was produced.
+
+---
+
+## Related Context
+
+- `fid4.md`
+- `artifactory.md`
+- `../workstreams/consumer-integration.md`