chore: Configure Obsidian to use Markdown links

Author: zah

.obsidian/app.json

@@ -1 +1,5 @@
-{}
+{
+  "useMarkdownLinks": true,
+  "alwaysUpdateLinks": true,
+  "newLinkFormat": "relative"
+}

.obsidian/backlink.json

@@ -0,0 +1,3 @@
+{
+  "backlinkInDocument": true
+}

.obsidian/workspace.json

@@ -13,12 +13,12 @@
             "state": {
               "type": "markdown",
               "state": {
-                "file": "specs/configuration.md",
+                "file": "specs/cli-spec.md",
                 "mode": "source",
                 "source": false
               },
               "icon": "lucide-file",
-              "title": "configuration"
+              "title": "cli-spec"
             }
           }
         ]
@@ -94,7 +94,7 @@
             "state": {
               "type": "backlink",
               "state": {
-                "file": "specs/configuration.md",
+                "file": "specs/cli-spec.md",
                 "collapseAll": false,
                 "extraContext": false,
                 "sortOrder": "alphabetical",
@@ -104,7 +104,7 @@
                 "unlinkedCollapsed": true
               },
               "icon": "links-coming-in",
-              "title": "Backlinks for configuration"
+              "title": "Backlinks for cli-spec"
             }
           },
           {
@@ -113,12 +113,12 @@
             "state": {
               "type": "outgoing-link",
               "state": {
-                "file": "specs/configuration.md",
+                "file": "specs/cli-spec.md",
                 "linksCollapsed": false,
                 "unlinkedCollapsed": true
               },
               "icon": "links-going-out",
-              "title": "Outgoing links from configuration"
+              "title": "Outgoing links from cli-spec"
             }
           },
           {
@@ -142,13 +142,13 @@
             "state": {
               "type": "outline",
               "state": {
-                "file": "specs/configuration.md",
+                "file": "specs/cli-spec.md",
                 "followCursor": false,
                 "showSearch": false,
                 "searchQuery": ""
               },
               "icon": "lucide-list",
-              "title": "Outline of configuration"
+              "title": "Outline of cli-spec"
             }
           }
         ]
@@ -170,8 +170,8 @@
   },
   "active": "01bf72509d2b5652",
   "lastOpenFiles": [
-    "specs/cli-spec.md",
     "specs/configuration.md",
+    "specs/cli-spec.md",
     "specs/connectivity-layer.md"
   ]
 }

specs/cli-spec.md

@@ -4,7 +4,7 @@
 
 The AW CLI (`aw`) unifies local and remote workflows for launching and managing agent coding sessions. Running `aw` with no subcommands starts the TUI dashboard. Subcommands provide scriptable operations for task/session lifecycle, configuration, repository management, and developer ergonomics.
 
-The CLI honors the layered configuration model in [[configuration]] (system, user, project, project-user, env, CLI flags). Flags map from config keys using the `--a-b-c` convention and env var prefix `AGENTS_WORKFLOW_`.
+The CLI honors the layered configuration model in [configuration](configuration.md) (system, user, project, project-user, env, CLI flags). Flags map from config keys using the `--a-b-c` convention and env var prefix `AGENTS_WORKFLOW_`.
 
 ### Primary Goals
 

specs/configuration.md

@@ -9,7 +9,7 @@
 * Motivation and support for tracking the origin of each configuration value, with use cases such as: debug-level log reporting, enforced setting explanation, and editor pre-fill mes
 sages.
 
-Layered configuration supports system, user, project, and project-user scopes. Values can also be supplied via environment variables and CLI flags. See [[cli-spec.md]] for flag mappings.
+Layered configuration supports system, user, project, and project-user scopes. Values can also be supplied via environment variables and CLI flags. See [cli-spec](cli-spec.md) for flag mappings.
 
 ### Keys