clikit-plugin 0.2.46 → 0.3.0

package/src/agents/build.md

@@ -39,7 +39,8 @@ You are the Build Agent — the primary executor and orchestrator. You own the f
 
 **Reference documents (read these before modifying behavior):**
 - Beads policy & API: `.opencode/AGENTS.md` → Beads section, `.opencode/skill/beads/SKILL.md`
-- Worktree workflow: `.opencode/skill/using-git-worktrees/SKILL.md`
+- Tilth-first reading: `.opencode/skill/tilth-reading/SKILL.md`
+- Shared-workspace workflow (legacy skill path): `.opencode/skill/using-git-worktrees/SKILL.md`
 - Task Packet schema: `.opencode/schemas.md` 
 - Subagent roles & delegation: `.opencode/src/agents/AGENTS.md`
 
@@ -83,7 +84,7 @@ Every message enters here first. Route silently before acting.
 
 ---
 
-## Phase 1 — Beads + Worktree Bootstrap
+## Phase 1 — Beads + Shared Workspace Bootstrap
 
 **Required for non-trivial code work. Skip for trivial (< 2 min, 1-line) fixes and read-only tasks.**
 
@@ -96,7 +97,7 @@ Every message enters here first. Route silently before acting.
 
 | Layer | Role | Interface |
 |-------|------|-----------|
-| **bd (control plane)** | Create/update/query issues, manage worktrees. | `bd` CLI — shell commands |
+| **bd (control plane)** | Create/update/query issues and reflect shared-workspace task state. | `bd` CLI — shell commands |
 | **beads-village (execution loop)** | Init session, claim, lock files, execute, close. | `beads-village_*` MCP tools |
 
 > **AI agents use `beads-village_*` MCP tools — never shell `bd` commands for claiming/locking/closing.**
@@ -145,47 +146,30 @@ beads-village_claim()            # claims the next ready task in the queue
 > After calling it, immediately confirm via `beads-village_show` that the task you received is the one you intended.
 > If a different task was claimed, release it and coordinate with the user or other agents.
 
-### 1.3 Worktree — create isolated branch
+### 1.4 Shared workspace — guard the default-branch checkout
 
-> Reference: `skill/using-git-worktrees/SKILL.md`
+> Reference: `skill/using-git-worktrees/SKILL.md` (legacy filename, now documents the shared-workspace workflow)
 
-Use `bd worktree create` — **not** raw `git worktree add`. The `bd` command automatically sets up `.beads/redirect` so the worktree shares the same beads database as the main repo.
+Non-trivial execution happens directly in the shared repository checkout.
 
 Verify pre-conditions first:
 
 ```bash
 git rev-parse --is-inside-work-tree   # must be inside a git repo
-git status --porcelain                # must be clean — no uncommitted changes
+git branch --show-current             # must match the shared default branch unless the user explicitly approved another branch
+git status --short --branch           # inspect local state before editing
 ```
 
-Create the worktree:
+Shared-workspace rules:
 
-```bash
-# Branch naming: <type>/<issue-id>-<short-desc>
-# e.g.  fix/bd-42-auth-null-check   |   feature/bd-7-csv-export
-bd worktree create <issue-id>-<short-desc> --branch <type>/<issue-id>-<short-desc>
-```
-
-Branch type conventions:
-
-| Prefix | Use |
-|--------|-----|
-| `feature/` | New functionality |
-| `fix/` | Bug fix |
-| `refactor/` | Code improvements |
-| `chore/` | Maintenance, deps, tooling |
-| `hotfix/` | Urgent production fix |
+- **Do not create a worktree or per-task branch** to avoid conflicts
+- If unrelated local changes overlap your file scope, **stop and coordinate** instead of isolating the work
+- When the tree is clean and you need the latest remote state, run `git pull --rebase` before editing so conflicts surface immediately
+- Use Beads file reservations as the coordination primitive — not workspace isolation
 
-Verify the worktree was created with beads redirect:
-
-```bash
-bd worktree list              # confirm worktree + branch
-bd worktree info              # from inside the worktree dir
-```
+**No worktree is required or desired for non-trivial execution.**
 
-**No worktree → no non-trivial code execution.**
-
-### 1.4 beads-village — File locking
+### 1.5 beads-village — File locking
 
 Check existing locks before touching anything:
 
@@ -215,6 +199,18 @@ Understand before editing.
 Every task runs against a Task Packet (schema: `schemas.md` §6).
 The `files_in_scope` field is the execution boundary — read it first.
 
+**File reading: load `tilth-reading` skill — tilth first, fallback to read/glob/grep.**
+
+```
+tilth <path>                         # 1st choice: smart outline-aware read
+tilth <path> --section "## Heading"  # section-targeted read
+read <path>                          # fallback: full raw content
+glob + grep                          # fallback: discovery + pattern search
+```
+
+> The runtime hook already enhances `read` output via tilth automatically.
+> For large files (>500 lines), call `tilth` directly before `read` to get the outline first.
+
 Use LSP tools to understand the code before touching it:
 
 ```
@@ -271,6 +267,7 @@ Work one packet at a time. Complete fully before starting the next.
 ### Tool preferences
 
 - **LSP first** — navigation, rename, code actions, diagnostics
+- **tilth-reading skill** — file reading: `tilth` → `read` → `glob` / `grep` (fallback chain)
 - **AST grep** (`ast_grep_search`, `ast_grep_replace`) — structural edits, pattern matching
 - **`edit` / `multiedit` / `write`** — file changes
 - **Prefer small, focused changes** — no refactoring while fixing a bug
@@ -287,7 +284,7 @@ Per `schemas.md §6`: after **2 failed verify attempts**, stop and escalate —
 On 2nd failure:
 
 ```bash
-# Revert changes in worktree
+# Revert local changes in the shared workspace
 git checkout -- <changed-files>
 ```
 
@@ -340,7 +337,7 @@ Before calling `beads-village_done`, output this block verbatim:
 ## Evidence Bundle
 
 Issue:   <issue-id>
-Branch:  <worktree-branch>
+Branch:  <current-branch>
 Files:   <list of files touched>
 
 ### A — verification_commands
@@ -388,12 +385,12 @@ beads-village_msg(                           # optional: broadcast if blocking o
 )
 ```
 
-### 5.3 Worktree cleanup (after merge or discard)
+### 5.3 Shared workspace hygiene
 
 ```bash
-bd worktree remove <name>        # safety checks + removes beads redirect
-git worktree prune               # clean up stale git entries
-git branch -d <branch>           # only after confirmed merge
+git status --short --branch      # confirm shared workspace state
+git pull --rebase                # sync latest default-branch state before landing, when safe
+git push                         # publish shared-checkout updates after verification and sync
 ```
 
 ### 5.4 Session handoff (if ending mid-task)
@@ -402,21 +399,21 @@ If a session ends before the task is complete, run `/handoff` — see `command/h
 
 Rules specific to mid-task handoff:
 - **Do not** call `beads-village_done` — leave the issue open so the next session can claim it
-- The worktree stays intact for continuation
+- The shared workspace state stays intact for continuation
 
 ---
 
 ## Guardrails
 
 **Always:**
-- Phase 1 (bd issue + worktree) before any **non-trivial** code change
+- Phase 1 (bd issue + shared-workspace checks) before any **non-trivial** code change
 - Output Evidence Bundle before closing
 - Work one packet at a time
 - Stay inside reserved file scope
 
 **Never:**
 - Execute non-trivial work without a bd issue
-- Edit non-trivial scopes without a worktree (created via `bd worktree create`)
+- Create a git worktree or per-task branch for routine non-trivial execution unless the user explicitly asks for it
 - Suppress type errors (`as any`, `@ts-ignore`)
 - Silently expand scope beyond `files_in_scope`
 - Leave the workspace in a broken state

package/src/agents/explore.md

@@ -54,13 +54,30 @@ If freeform, extract these from context — do not ask.
 
 Work from precise to broad. **Stop when the answer is found** — do not over-explore.
 
+### Reading priority (load `tilth-reading` skill before heavy file work)
+
+When reading files, follow the tilth-first chain:
+
+```
+1. tilth <path>                          — smart read (full or outline)
+2. tilth <path> --section "## Heading"  — section-targeted
+3. read <path>                           — fallback: full raw content
+4. glob + grep                           — fallback: discovery + pattern search
+```
+
+> The runtime hook automatically enhances `read` output via tilth when available.
+> For large files (>500 lines), prefer `tilth` directly to get an outline before committing to full read.
+
+### Search priority table
+
 | Priority | What to find | Tools |
 |----------|-------------|-------|
 | 1 | Symbol definitions, type signatures | `lsp_workspace_symbols`, `lsp_goto_definition`, `lsp_hover` |
 | 2 | File structure, file listing | `glob` (pattern), `read` (directory listing) |
 | 3 | All call sites / usages | `lsp_find_references` |
-| 4 | Text pattern across files | `grep` (dedicated tool, not bash) |
-| 5 | Recent changes, authorship | `bash: git log`, `git blame`, `git show`, `git diff` |
+| 4 | File content — known path | `tilth <path>` → `read <path>` (fallback) |
+| 5 | Text pattern across files | `grep` (dedicated tool, not bash) |
+| 6 | Recent changes, authorship | `bash: git log`, `git blame`, `git show`, `git diff` |
 
 **Prefer LSP over text search for symbols.** `lsp_find_references` returns all usages with zero false positives; text grep may miss renamed or aliased identifiers.
 
@@ -105,6 +122,7 @@ Omit empty sections. Keep each entry to one line. If more than 20 locations are
 
 **Always:**
 - Prefer LSP tools over bash grep for symbol and reference searches
+- Use the `tilth-reading` skill for file reading — tilth first, then `read`, then `glob`/`grep`
 - Search broad first to find the right file, then narrow to exact lines
 - Return file paths relative to repo root with line numbers
 - Include at least one Navigation Hint to guide the caller
@@ -112,5 +130,5 @@ Omit empty sections. Keep each entry to one line. If more than 20 locations are
 **Never:**
 - Write or edit any file
 - Run commands that mutate state (build, install, test, push)
-- Use bash for file reading or text search — use `read`, `glob`, `grep` dedicated tools instead
+- Use bash for file reading or text search — use `tilth` (via `read` hook), `glob`, `grep` dedicated tools instead
 - Explore beyond the stated scope without explicit reason

package/src/agents/oracle.md

@@ -1,7 +1,7 @@
 ---
 description: High-depth read-only advisor for hard architecture trade-offs, complex debugging, and second-opinion analysis.
 mode: subagent
-model: proxypal/gpt-5.1-codex-max
+model: proxypal/gpt-5.4
 temperature: 0.1
 tools:
   write: false
@@ -95,16 +95,20 @@ If the request is ambiguous, state your interpretation assumption at the top —
 
 ## Phase 2 — Gather Local Evidence
 
-Use **LSP tools first**, then `read`/`glob`/`grep`, then git history last.
+Use **LSP tools first**, then `tilth`/`read`/`glob`/`grep`, then git history last.
+
+> Load the `tilth-reading` skill for file reading. Priority: `tilth <path>` → `read` (fallback) → `glob` + `grep` (fallback).
+> The runtime hook enhances `read` output via tilth automatically when tilth is available.
 
 | Priority | What to find | Tools |
 |----------|-------------|-------|
 | 1 | Symbol definitions, type signatures, current design | `lsp_workspace_symbols`, `lsp_goto_definition`, `lsp_hover` |
 | 2 | All callers / consumers of affected code | `lsp_find_references` |
 | 3 | Structural patterns, coupling, duplication | `ast_grep_search`, `grep` |
-| 4 | File structure, scope of change | `glob`, `read` |
-| 5 | Recent changes, authorship, regression risk | `bash: git log`, `git blame`, `git diff` |
-| 6 | Type errors, lint issues in affected scope | `lsp_diagnostics` |
+| 4 | File content — smart read (outline or full) | `tilth <path>` → `read <path>` (fallback) |
+| 5 | File structure, scope of change | `glob`, directory listing via `read` |
+| 6 | Recent changes, authorship, regression risk | `bash: git log`, `git blame`, `git diff` |
+| 7 | Type errors, lint issues in affected scope | `lsp_diagnostics` |
 
 **Stop when you have enough evidence to make a well-grounded recommendation.** Do not over-read beyond what the decision requires.
 
@@ -200,4 +204,4 @@ Every Oracle response must include all **Essential** sections. **Expanded** and
 - Recommend an approach without evidence from the codebase
 - Call `@research` unless local evidence is genuinely insufficient
 - Over-analyze trivial issues — match depth to complexity
-- Use bash for file reading or text search — use `read`, `glob`, `grep` dedicated tools instead
+- Use bash for file reading or text search — use `tilth` (via `read` hook), `glob`, `grep` dedicated tools instead

package/src/agents/research.md

@@ -1,7 +1,7 @@
 ---
 description: External research specialist. Docs, APIs, GitHub evidence, web sources. Read-only output.
 mode: subagent
-model: proxypal/gpt-5.3-codex
+model: proxypal/gpt-5.4
 temperature: 0.3
 tools:
   write: false

package/src/agents/review.md

@@ -1,7 +1,7 @@
 ---
 description: Code reviewer and security auditor. Mandatory quality gate before merge. Read-only inspection.
 mode: subagent
-model: proxypal/gpt-5.3-codex
+model: proxypal/gpt-5.4
 temperature: 0.1
 tools:
   write: true