Refactor workspace structure and documentation

- Deleted obsolete files: obsidian-vault.md, onboarding.md, workspace-model.md
- Updated opencode.json to remove references to deleted files.
- Revised profile.md to clarify the status of legacy paths and communication evidence.
- Adjusted prompts to reflect new file paths and improve clarity.
- Enhanced daily logs with focus, work-items, and blockers properties.
- Updated work-item notes to include systems, workstreams, people, and related properties.
- Improved context maintenance guidelines to ensure accurate and durable project knowledge.
- Refined base filters to exclude template files and ensure only relevant notes are displayed.
- Updated daily templates to ensure proper formatting and consistency.
- Modified workflows to align with the new vault structure and improve context synchronization.

.opencode/skills/copilot-prompt-engineering/SKILL.md

@@ -18,10 +18,10 @@ Use this skill when the user wants a prompt for another AI assistant, GitHub Cop
    - test strategy
    - story/PR drafting
 2. Pull only the relevant context:
-   - `ai/work-items/` for ticket-specific context
-   - `ai/context/systems/` for component context
-   - `ai/context/workstreams/` for recurring constraints
-   - `ai/context/ios/` for Swift/iOS guidance
+   - `vault/02-work-items/` for ticket-specific context
+   - `vault/03-context/systems/` for component context
+   - `vault/03-context/workstreams/` for recurring constraints
+   - `vault/03-context/ios/` for Swift/iOS guidance
 3. Make the prompt self-contained.
 4. Tell the target AI what to inspect before acting.
 5. State constraints, non-goals, and validation expectations.

.opencode/skills/index.md

@@ -24,7 +24,6 @@ Skills available to the workspace agent.
 
 ## Related
 
-- [Tooling Map](../../knowledge/maps/tooling.md)
+- [Tooling Map](../../vault/07-maps/tooling.md)
 - [Commands Index](../commands/index.md)
 - [Prompts Index](../../prompts/index.md)
-

.opencode/skills/ios-swift-answering/SKILL.md

@@ -11,8 +11,8 @@ Use this skill for Swift, SwiftUI, iOS architecture, concurrency, testing, or de
 ## Workflow
 
 1. Identify whether the question is general Swift/iOS or Fidelity-specific.
-2. Read `ai/context/ios/current-practices.md` for currentness rules.
-3. Read `ai/context/ios/project-swift-guidance.md` when the answer may affect XFlow, Fid4, XFlowViewMaker, FTFrameworks, feature flags, or consumer validation.
+2. Read `vault/03-context/ios/current-practices.md` for currentness rules.
+3. Read `vault/03-context/ios/project-swift-guidance.md` when the answer may affect XFlow, Fid4, XFlowViewMaker, FTFrameworks, feature flags, or consumer validation.
 4. If the answer depends on current Apple APIs, Xcode versions, or migration guidance, verify with official Apple/Swift documentation before making strong claims.
 5. Separate:
    - current best practice