skills: add obsidian-sorter; point project-docs at the inbox workflow

- new obsidian-sorter skill: file notes via the 010 inbox on .27
- project-docs now writes to the inbox and lets the sorter choose the
  folder + type, instead of the retired <vault>/Projects/ path
- obsidian-note template gains title/type/created and keeps skills:/tools:

skills/project-docs/SKILL.md

@@ -23,7 +23,7 @@ When invoked, `project-docs` coordinates five documentation layers:
 | Platform | Target Audience | Purpose & Tone | Generated / Updated Artifacts |
 | :--- | :--- | :--- | :--- |
 | **Gitea** | Developers / Resume | Technical documentation & repository README. **Standard concise markdown**. Highlights tech stack, usage, and key tools/skills demonstrated for employment. | `<project>/README.md` (embedded Mermaid diagram, Archify links, setup/usage guide). |
-| **Obsidian** | Humans / Hiring Managers | **Human understanding**. Simple, clear, layperson-friendly language, brief. Highlights skills, tools, and concepts that showcase for employment while forming a usable tool for understanding things. | `<vault>/Projects/<ProjectName>.md` (simple overview, employment highlights, embedded Mermaid). |
+| **Obsidian** | Humans / Hiring Managers | **Human understanding**. Simple, clear, layperson-friendly language, brief. Highlights skills, tools, and concepts that showcase for employment while forming a usable tool for understanding things. | A note written into `010 inbox/` on host **`.27`** (simple overview, employment highlights, embedded Mermaid). The **`obsidian-sorter`** skill files it into `200 projects/<category>/` and updates the Table of Contents. |
 | **Mermaid + Archify** | Architectural Visualization | High-level system architecture and interactive HTML maps. | 1. `<project>/docs/<topic>.mmd`<br>2. `<project>/docs/diagrams/<topic>.png` (rendered via `mmdc`)<br>3. `<project>/docs/<topic>-map.html` (rendered via Archify)<br>4. Published to `https://maps.lab.audasmedia.com.au/<project>/docs/`. |
 | **Vikunja** | Humans | **High-level task tracking**. Simple, brief, actionable human steps (milestones, key deliverables). | Vikunja project board or `<project>/docs/vikunja-tasks.json`. |
 | **Outline** | AI Agents | **Deep AI context & document index**. Itemizes what is in each document in the collection so AI agents can inject specific files directly without searching. **Strictly uses `ste-writing` skill rules** (Simplified Technical English). | `<project>/docs/outline/` collection (`00-index.md`, `01-system-overview.md`, `02-config-and-env.md`, `03-code-map.md`, `04-agent-runbook.md`). |
@@ -45,7 +45,10 @@ Scans git commits, file edits, or structural changes, then updates affected docu
 For every project, step through the 5 platforms and **ask/confirm** before writing:
 
 1. **Gitea**: *"Does a Gitea repository exist for this project, or should it be created? [Repo Name]"*
-2. **Obsidian**: *"Should an Obsidian project note be created for human understanding and portfolio showcase? [Confirm / Vault Location / Note Name]"*
+2. **Obsidian**: *"Should an Obsidian project note be created for human understanding and portfolio showcase? [Confirm / Note Name]"*
+   - Write it to `~/obsidian/010 inbox/` **on `.27`** using the note template.
+   - **Do not choose a folder or a type.** The `obsidian-sorter` skill proposes the
+     destination and the vault owner approves it. See the `obsidian-sorter` skill.
 3. **Mermaid & Archify**: *"Do you want a Mermaid architecture diagram and Archify interactive map for this project? [Confirm / Topic Name]"*
 4. **Vikunja**: *"Should a Vikunja project/board be created for human task tracking? [Confirm / Board Name]"*
 5. **Outline**: *"Should an Outline document collection be created for AI agents to resume context across restarts? [Confirm / Collection Name]"*