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.

core/integrations/communication-model.md

@@ -65,7 +65,7 @@ Prefer generic `AIW_*` variables for reusable workspaces:
 - `AIW_MATTERMOST_SYNC_INTERVAL_MINUTES`
 - `AIW_SLACK_EXPORT_PATH`
 
-Project-specific variables may remain as compatibility aliases, but new integrations should prefer `AIW_*`.
+Project-specific variables may remain as profile aliases, but new integrations should prefer `AIW_*`.
 
 ---
 
@@ -80,4 +80,3 @@ If a connector fails:
 - do not infer project facts from the failure
 
 The agent may report the operational failure to the user, but it must not promote the failure as project memory unless the user explicitly asks to track tooling work.
-

core/integrations/obsidian-model.md

@@ -48,7 +48,7 @@ Technical runtime remains outside the vault:
 - `scripts/*/generated/`
 - archives and local virtual environments
 
-Legacy `ai/context`, `ai/state`, `ai/work-items`, `ai/logs`, and `knowledge` paths may exist temporarily as compatibility fallback during migration.
+Communication evidence may exist under `ai/inbox/` or connector `generated/` folders, but promoted memory belongs in `vault/`.
 
 ---
 

core/memory/operational-memory.md

@@ -86,7 +86,7 @@ vault/00-start/*.md
 vault/03-context/process/*.md
 ```
 
-Legacy `ai/*` and `knowledge/*` paths may remain as compatibility fallback, but new writes should target `vault/` first when a canonical note exists.
+Raw evidence stays outside `vault/`; promoted memory is written to `vault/`.
 
 ---
 

core/profiles/create-project-profile.md

@@ -48,7 +48,7 @@ vault/09-templates/
 
 Keep project-specific facts out of `core/`.
 
-Legacy `ai/context`, `ai/state`, `ai/work-items`, and `ai/logs` paths may be kept temporarily for compatibility, but new project profiles should treat `vault/` as canonical memory.
+Treat `vault/` as canonical memory. Keep connector inboxes and generated evidence outside the vault.
 
 ---