@timurproko/a1 0.1.8-dev.546 → 0.1.8-dev.560

package/dist/ui/components/dialog-panel.js

@@ -27,9 +27,9 @@ export function renderDialogPanel(state, width, theme) {
     });
     const description = state.rows[state.index]?.description ?? "";
     const hint = typeof state.hint === "string"
-        ? theme.fg("dim", `  ${state.hint}`)
-        : renderShortcutHints(state.hint, theme, 2);
-    const plainHint = typeof state.hint === "string" ? `  ${state.hint}` : shortcutHintsText(state.hint, 2);
+        ? theme.fg("dim", ` ${state.hint}`)
+        : renderShortcutHints(state.hint, theme, 1);
+    const plainHint = typeof state.hint === "string" ? ` ${state.hint}` : shortcutHintsText(state.hint, 1);
     return [
         rule,
         ...rows,

package/docs/architecture/project-structure.md

@@ -92,15 +92,18 @@ Build output mirrors the production namespaces directly under ignored `dist/`, w
 
 Every task worktree must be created at `{working-dir}/.worktrees/<task-id>`, where `{working-dir}` is the agent session's initial working directory. The `.worktrees` directory is inside that working directory, not beside it. For working directory `D:/Git/a1`, `D:/Git/a1/.worktrees/<task-id>` is correct and `D:/Git/a1-<task-id>` is forbidden.
 
-From the initial working directory, create and address a task worktree explicitly:
+From the initial working directory, create the task branch and worktree, run `a1 session link-worktree <absolute-worktree>` from the owning A1 session, and continue to address it explicitly:
 
 ```sh
 git fetch origin develop
-git worktree add --detach .worktrees/<task-id> origin/develop
+git worktree add -b <type>/<short-description> .worktrees/<task-id> origin/develop
+a1 session link-worktree <absolute-worktree>
 git -C .worktrees/<task-id> status
 ```
 
-The primary worktree stays on `develop` for integration and must not be used for task edits. Do not edit, move, or remove another session's worktree.
+A successful link response confirming the exact canonical worktree is required before planning, implementation, test, or delivery-documentation edits. If linking fails or confirms another path, stop task edits and report the blocker instead of continuing with primary-checkout footer metadata. A session resuming an existing delivery or switching streams links the exact owned worktree before editing it.
+
+The association switches bare A1's footer repository context and pull-request discovery; it does not change process or tool cwd and does not register, claim, release, or authorize cleanup of the worktree. Repository commands therefore keep an explicit worktree path. The primary worktree stays on `develop` for integration and must not be used for task edits. Do not edit, adopt, move, or remove another session's worktree.
 
 ## Documentation and comments
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@timurproko/a1",
-  "version": "0.1.8-dev.546",
+  "version": "0.1.8-dev.560",
   "description": "Standalone terminal workspace for supervised native and managed agents",
   "type": "module",
   "privateLaunchContract": "neutral-launch-v1",
@@ -64,8 +64,8 @@
     "typecheck:bin": "tsgo -p tsconfig.bin.json"
   },
   "dependencies": {
-    "@earendil-works/pi-coding-agent": "0.87.0",
-    "@earendil-works/pi-tui": "0.87.0",
+    "@earendil-works/pi-coding-agent": "0.87.1",
+    "@earendil-works/pi-tui": "0.87.1",
     "@silvia-odwyer/photon-node": "0.3.4",
     "chalk": "5.6.2",
     "cross-spawn": "7.0.6",