Merge dev → main (automated)

.gitignore

@@ -145,8 +145,15 @@ Worklog Specific Ignores
 # Ignore Worklog directory by default
 .worklog/*
 
+# Ignore nested Worklog worktree directories anywhere in the tree
+**/.worklog/
+
 !.worklog/config.yaml
 
+# SQLite runtime sidecar files (WAL/SHM) for worklog DBs
+worklog.db-shm
+worklog.db-wal
+
 # opencode temporary files and directories
 .opencode/
 .tmp

.implement_state.json

@@ -1,8 +1,8 @@
 {
-  "work_item_id": "WL-0MRSGMTYU009OZCF",
-  "worktree_path": "/home/rgardler/projects/ContextHub/.worklog/worktrees/wl-WL-0MRSGMTYU009OZCF-add-audit-file-to-wl-audit-set-for-file",
+  "work_item_id": "WL-0MS8SVY7P0094K6D",
+  "worktree_path": "/home/rgardler/projects/ContextHub/.worklog/worktrees/wl-WL-0MS8SVY7P0094K6D-fix-skills-and-commands-must-run-in-corr",
   "repo_root": "/home/rgardler/projects/ContextHub",
   "parent_branch": "dev",
   "commit_msg": "",
-  "started_at": "2026-07-21T18:30:22Z"
+  "started_at": "2026-08-01T01:17:51Z"
 }

.pi/skills/heartbeat/scripts/heartbeat.py

@@ -40,7 +40,7 @@ def run_wl(args):
         json.JSONDecodeError: If wl output is not valid JSON.
     """
     cmd = ['wl'] + args
-    result = subprocess.run(cmd, capture_output=True, text=True)
+    result = subprocess.run(cmd, capture_output=True, text=True, check=False)
     if result.returncode != 0:
         raise RuntimeError(
             f"wl command failed: {' '.join(cmd)}\n"
@@ -145,7 +145,7 @@ def check_queue():
                     ]
                     try:
                         pi_result = subprocess.run(
-                            pi_cmd, capture_output=True, text=True, timeout=600
+                            pi_cmd, capture_output=True, text=True, timeout=600, check=False
                         )
                         if pi_result.returncode != 0:
                             return (
@@ -191,7 +191,7 @@ def parse_args():
 
 def main():
     """Entry point for command-line invocation."""
-    args = parse_args()
+    parse_args()
     result = check_queue()
     print(result)
     if result.startswith('Heartbeat error'):

CHANGELOG.md

@@ -1,5 +1,18 @@
 # Changelog
 
+## Unreleased
+### Features
+- Show total actionable count in browse list title ("top N of M") with auto-refresh (WL-0MS4FIEN40037GB9)
+- Smart selection: always show critical and completed/in_review items in TUI lists (WL-0MS8W5LTW006YZ4B)
+- Hide child work items from top-level selection lists; drill down via Tab (WL-0MS964SIA0057ABR)
+- Navigation stack for hierarchical browsing in Herdr plugin (WL-0MS4FI763006105Y)
+- Missing text-insertion shortcuts: i/r/u-p-*/u-s/u-t/x-c/x-d/a-a/a-y/a-r chords (WL-0MS4FHW290053SH4)
+- Auto-sync: periodic background wl sync (WL-0MS4FIUYS001K08K)
+- Run !/!! prefixed commands visibly in a new herdr pane; keep output pane open (WL-0MS7MFILJ0079283, WL-0MS9HIUE0002JAKQ)
+- Total actionable count display in detail view with GitHub issue number (WL-0MS4FIM8T001XAVF)
+- Rich settings: browseItemCount and showHelpText toggle (WL-0MS4FJ2TX009V7V5)
+- Skills and commands run in correct project directory (WL-0MS8SVY7P0094K6D)
+
 ## v1.0.4 (2026-07-26)
 ### Features
 - Add periodic request scheduling to pi worklog plugin (WL-0MRHYQU1S009DJ9B)

CLI.md

@@ -446,11 +446,13 @@ Suggest the next work item(s) to work on. Non-actionable items (deleted, complet
 
 #### Hierarchy-aware selection
 
-`wl next` is hierarchy-aware: it returns **parent items** instead of descending into their children. For example, if an epic has open child tasks, `wl next` returns the epic itself — not one of its children. This surfaces the high-level unit of work for you to claim, after which you can work on its sub-tasks.
+`wl next` is strictly root-only: it returns **parent items** only and never returns an item with a `parentId` set. For example, if an epic has open child tasks, `wl next` returns the epic itself — never one of its children. This surfaces the high-level unit of work for you to claim, after which you can work on its sub-tasks (reachable via `wl list --parent <id>` or drill-down in the TUIs).
 
-Leaf items (items without children, or whose children are all completed) continue to be returned normally. Items whose parent is completed, deleted, or otherwise absent from the candidate pool are promoted to root level (orphan promotion) and compete on their own merit.
+Leaf items (items without children, or whose children are all completed) continue to be returned normally. **Orphan promotion is removed** — children whose parent is completed, deleted, or otherwise absent from the candidate pool are hidden entirely and are NOT promoted to root level. Such children remain reachable via `wl list --parent <id>`, `wl show`, and search.
 
-Items whose parent (or ancestor) has status `in-progress` are **not** promoted — the entire in-progress subtree is skipped from `wl next` recommendations. This includes critical-priority children: they are only surfaced when their parent is not a valid (open, non-completed, non-deleted, non-in-progress) candidate.
+Items whose parent (or ancestor) has status `in-progress` are **not** returned — the entire in-progress subtree is skipped from `wl next` recommendations. This includes critical-priority children.
+
+In blocker-surfacing and critical-escalation paths, child blockers are never returned directly: a child blocker whose parent is a selectable actionable root is surfaced as that parent instead, and a child blocker whose parent is not selectable is hidden entirely (returning null with a clear reason when no other work is available).
 
 In batch mode (`-n <count>`), children of returned parents are also excluded from subsequent results, ensuring the batch never contains items from the same subtree.
 
@@ -471,13 +473,13 @@ When multiple candidate items exist, `wl next` ranks them using the following cr
 3. **Blocked penalty** — items with active dependency blockers are excluded by default (see `--include-blocked`).
 4. **Tie-breakers** — sort_index, then age (older items first) break remaining ties.
 
-Items with `status: 'blocked'` that have `critical` priority trigger a special escalation path: their direct blockers are surfaced immediately, bypassing the general ranking logic. Blocked `critical` items that are children of an open parent are still escalated — the parent item's blockers will be surfaced if the critical child is in its tree.
+Items with `status: 'blocked'` that have `critical` priority trigger a special escalation path: their direct blockers are surfaced immediately, bypassing the general ranking logic. Blocked `critical` items that are children of an open parent are still escalated — the parent item's blockers will be surfaced if the critical child is in its tree. Child blockers are never returned directly (see "Hierarchy-aware selection" above).
 
 #### Backward compatibility
 
 The `--include-blocked` flag behavior is unchanged. The ranking boost only affects ordering among candidates that are already considered (i.e., unblocked items by default).
 
-The JSON output schema is unchanged — only the selection behavior differs: parent items are now returned instead of children.
+The JSON output schema is unchanged — only the selection behavior differs: only root items (parents) are now returned instead of children.
 
 Options:
 
@@ -603,6 +605,7 @@ Options:
 `-s, --status <status>` (optional)
 `-p, --priority <priority>` (optional)
 `--parent <id>` — Filter by parent ID (direct children only) (optional).
+`--root-only` — Show only root-level items (items with no parent). Mutually exclusive with `--parent` (optional).
 `--tags <tags>` (optional)
 `-a, --assignee <assignee>` (optional)
 `-n, --number <n>` (optional) — Limit the number of items returned
@@ -621,6 +624,8 @@ wl list -s open -p high
 wl list -s open,in-progress    # status is open OR in-progress
 wl list --status open,completed,blocked
 wl list -s open,in-progress --stage in_review  # status AND stage filters
+wl list --root-only            # root items only (no parents)
+wl list --root-only -p critical
 wl search "signup"
 wl -F concise list -s in-progress
 wl --json list -s open --tags backlog

README.md

@@ -76,7 +76,7 @@ For freeze triage and profiling details (including `TUI_CHORD_DEBUG`, `strace`,
 
 ### Install the Pi Worklog browse extension
 
-The repository includes a Pi extension that adds a Worklog browse flow (`/wl` and `Ctrl+Shift+B`) which lists the next 5 recommended work items (`wl next -n 5`) and previews the selected item in a widget above the editor as selection changes (`title <id>`, `Priority/Stage/Status`, `Risk/Effort`, and the first 7 description lines). Pressing Enter on a selected item opens a focused scrollable detail view backed by `wl show <id> --format markdown`, with keyboard navigation support for Up/Down, PageUp/PageDown, Space, `g` (top), `G` (bottom), and `Esc` (close).
+The repository includes a Pi extension that adds a Worklog browse flow (`/wl` and `Ctrl+Shift+B`) which lists the next 5 recommended work items (`wl next -n 5`) and previews the selected item in a widget above the editor as selection changes (`title <id>`, `Priority/Stage/Status`, `Risk/Effort`, and the first 7 description lines). The top-level list is root-only: child work items are hidden and only appear under their parent via Tab drill-down (children are reachable through `wl list --parent <id>`). Pressing Enter on a selected item opens a focused scrollable detail view backed by `wl show <id> --format markdown`, with keyboard navigation support for Up/Down, PageUp/PageDown, Space, `g` (top), `G` (bottom), and `Esc` (close).
 
 Install it globally by creating a symlink under `~/.pi/agent/extensions`:
 

TUI.md

@@ -51,7 +51,7 @@ The TUI is implemented as a Pi extension located in `packages/tui/`:
 
 ### Browse & Select
 
-On launch, the TUI shows a list of recommended next work items. Navigate with
+On launch, the TUI shows a list of recommended next work items (root items only — child work items are hidden and appear only under their parent via drill-down). Navigate with
 Up/Down arrows, press Enter to see full details, or use shortcut keys:
 
 - **i** — insert `implement <id>` into the editor

docs/icons-design.md

@@ -453,18 +453,32 @@ WL_NO_ICONS=1 wl list --format full
 
 ### Output Examples
 
-**CLI (TTY) with icons:**
+**CLI (TTY) with icons (normal format):**
 ```
-ID:    TEST-1
-Title: Set up CI pipeline
-Status: 🟢 Open [OPEN] · Stage: In Progress | Priority: 🚨 critical [CRIT]
+| Field     | Value |
+| --------- | ----- |
+| ID        | TEST-1 |
+| Title     | Set up CI pipeline |
+| Status    | 🟢 Open [OPEN] · Stage: In Progress \| Priority: 🚨 critical [CRIT] |
+| SortIndex | 100 |
+| Risk      | — |
+| Effort    | — |
+
+Description: A test item for audit formatting
 ```
 
 **CLI with icons disabled:**
 ```
-ID:    TEST-1
-Title: Set up CI pipeline
-Status: [OPEN] · Stage: In Progress | Priority: critical
+| Field     | Value |
+| --------- | ----- |
+| ID        | TEST-1 |
+| Title     | Set up CI pipeline |
+| Status    | [OPEN] · Stage: In Progress \| Priority: critical |
+| SortIndex | 100 |
+| Risk      | — |
+| Effort    | — |
+
+Description: A test item for audit formatting
 ```
 
 **TUI list:**

docs/skill-path-conventions.md

@@ -48,11 +48,11 @@ working directory the agent was in when the skill was loaded.
 
 ### AGENTS.md References
 
-The global AGENTS.md at `~/.pi/agent/AGENTS.md` uses `skills/<name>/...`
-prefixes since it lives one directory above the `skills/` directory:
+The global AGENTS.md at `~/.pi/agent/AGENTS.md` uses absolute
+`/home/rgardler/.pi/agent/skills/<name>/SKILL.md` paths in markdown links:
 
 ```
-resources/skills/ship/SKILL.md           # ~/.pi/agent/AGENTS.md → ~/.pi/agent/skills/ship/SKILL.md  
+[ship skill](/home/rgardler/.pi/agent/skills/ship/SKILL.md)   # from ~/.pi/agent/AGENTS.md
 ```
 
 ### Backward Compatibility

docs/tutorials/04-using-the-tui.md

@@ -162,34 +162,43 @@ When OpenCode is active, the response appears in a bottom pane:
 
 ## Step 6a: Pi Extension Browse Shortcuts
 
-When using the Pi agent with the Worklog browse extension (launched via `piman`), you can quickly insert commands into the editor using keyboard shortcuts. These shortcuts are **config-driven** — defined in `packages/tui/extensions/shortcuts.json` and dispatched dynamically by the shortcut registry, so they can be extended or customized without editing source code.
+When using the Pi agent with the Worklog browse extension (launched via `piman`), you can quickly insert commands into the editor using keyboard shortcuts. These shortcuts are **config-driven** — defined in `packages/tui/extensions/Worklog/shortcuts.json` and dispatched dynamically by the shortcut registry, so they can be extended or customized without editing source code.
 
 ### Browse List View Shortcuts
 
 In the browse selection list (when you see a list of work items), press one of the following keys to insert a command for the selected item:
 
-| Key | Command Inserted |
-|-----|------------------|
-| `i` | `implement <selected-id>` |
-| `p` | `plan <selected-id>` |
-| `n` | `intake <selected-id>` |
-| `c` | `create <description>` |
-| `a` | `audit <selected-id>` |
-
-The command text is inserted into the Pi editor (without a trailing newline), allowing you to review or edit it before pressing Enter to submit.
+| Key | Command Inserted | Stage filter |
+|-----|------------------|-------------|
+| `c` | `/intake` (create new item) | — |
+| `n` | `/intake <id>` | `idea` |
+| `p` | `/plan <id>` | `intake_complete` |
+| `i` | `/skill:implement <id>` | `intake_complete`, `plan_complete`, `in_progress` |
+| `s` | search | — |
+| `r` | producer-review toggle | — |
+| `f i` / `f n` / `f p` / `f r` | stage filters (idea / intake / plan / in_review) | — |
+| `u p l/m/h/c` | update priority (low/medium/high/critical) | — |
+| `u s` | update stage/status | — |
+| `u t` | update title | — |
+| `x c` / `x d` | close / delete | — |
+| `a a` / `a y` / `a r` | audit (automatic / approve / reject) | `in_review` |
+
+The command text is inserted into the Pi editor (without a trailing newline), allowing you to review or edit it before pressing Enter to submit. Chords (multi-key shortcuts like `u p h`) are entered by pressing each key in sequence.
 
 ### Detail View Shortcuts
 
-In the detail scrollable view (when viewing a single work item), the same shortcuts work identically: press `i`, `p`, `n`, or `a` to insert the corresponding command for the currently displayed work item. The detail view also clears its preview widget before closing the modal, giving you a clean editor to work in.
+In the detail scrollable view (when viewing a single work item), the same shortcuts work identically: press `i`, `p`, `n`, `c`, `s`, or `r` (plus the `u`, `x`, `a`, and `f` chords) to insert the corresponding command for the currently displayed work item. The detail view also clears its preview widget before closing the modal, giving you a clean editor to work in.
 
 When viewing details, a shortcut hint line appears at the bottom of the rendered content showing available keys for the current work item's stage (same formatting and filtering as the selection list hints). When a chord leader key (e.g., `u`) is pressed, the hint line updates to show available chord completions. The hint line respects the `showHelpText` setting and can be hidden via `/wl settings`.
 
 ### How It Works
 
 Each shortcut is defined as a JSON object with:
-- `key`: The single-character key (e.g., `"i"`)
-- `command`: The template string to insert (e.g., `"implement <id>"`)
+- `key` (or `chord`): The single-character key or chord sequence (e.g., `"i"` or `["u", "p", "h"]`)
+- `command`: The template string to insert (e.g., `/skill:implement <id>`)
 - `view`: Which view(s) the shortcut applies to (`"list"`, `"detail"`, or `"both"`)
+- `label` / `description`: Human-readable metadata shown in the help-line hints
+- `stages` (optional): Restricts the shortcut to items in the listed stages (e.g., audit chords only appear for `in_review` items)
 
 The `shortcutRegistry` loads `shortcuts.json` at extension init time and dispatches matched shortcuts in both the browse list and detail view handlers. Navigation keys (`Up`, `Down`, `Enter`, `Escape`, `PageUp`, `PageDown`, `G`) remain functional in both views.
 

package.json

@@ -1,10 +1,12 @@
 {
   "name": "worklog",
-  "version": "1.0.4",
+  "version": "1.0.5",
   "description": "A simple experimental issue tracker for AI agents",
   "main": "dist/index.js",
   "type": "module",
-  "workspaces": ["packages/shared"],
+  "workspaces": [
+    "packages/shared"
+  ],
   "bin": {
     "worklog": "./dist/cli.js",
     "wl": "./dist/cli.js"