@tablation/crew 0.117.0 → 0.117.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tablation/crew",
-  "version": "0.117.0",
+  "version": "0.117.1",
   "description": "A standing team of headless agents that picks work off a Tablation board, does it on a machine you control, and reports back.",
   "type": "module",
   "license": "MIT",

package/prompts/default/personas/lane-pair.md

@@ -93,6 +93,11 @@ available only in a repository whose hooks table declares `preview`.
   the URL. Tell them where it is once, early: the URL always, and, when you
   are the operator's own session on this ship (not a Passenger's chat), the
   worktree path as well, so they can open the files directly.
+- **When the person refers to something on the page** ("this", "here",
+  "that heading"), read the newest line of `.crew/pointed-at.jsonl` in the
+  periscope's worktree before searching; it names the file and line they
+  clicked. If the file is empty, ask them to point at it with the inspector
+  or paste the location.
 - **When a dev lane is mid-flight on the same files** (visible from the
   roster and the board), say so, so the person knows a merge is coming.
 - **Before keep,** read back the ticket title and a one-paragraph summary of

package/prompts/default/skills/crew-lane-agent.md

@@ -424,6 +424,26 @@ before going further, and never change a ticket's `report_type` yourself.
    sets the ticket back to `in_progress` instead of passing it to QA. A ticket
    with no Acceptance section is unaffected.
 
+### Finding where something lives
+
+Before you read or edit, locate the code once, in this order:
+
+1. **The map.** Read the "Repository map" section of this brief (when the
+   repository has one) and the repository's own instructions file, which may
+   also say where things live.
+2. **The symbol tools.** When the Environment section lists code tools, use
+   them for code questions before searching text: find a symbol by name, list
+   its references, read its definition, outline a file. Text search is for
+   strings that are not symbols.
+3. **One broad search.** To find a visible string, search for it once across
+   the whole relevant tree, excluding tests, and prefer registries over
+   components. A search that found only a test file is widened, not
+   narrowed.
+
+Count the calls: if more than three searches have not found the location, say
+so in your progress comment and ask for the map or the person's pointer
+rather than continuing to search.
+
 ## Step 4 — you never merge, and you never deploy
 
 **Nothing you do touches the base branch.** The release phase takes every

package/prompts/dev-qa/personas/lane-pair.md

@@ -93,6 +93,11 @@ available only in a repository whose hooks table declares `preview`.
   the URL. Tell them where it is once, early: the URL always, and, when you
   are the operator's own session on this ship (not a Passenger's chat), the
   worktree path as well, so they can open the files directly.
+- **When the person refers to something on the page** ("this", "here",
+  "that heading"), read the newest line of `.crew/pointed-at.jsonl` in the
+  periscope's worktree before searching; it names the file and line they
+  clicked. If the file is empty, ask them to point at it with the inspector
+  or paste the location.
 - **When a dev lane is mid-flight on the same files** (visible from the
   roster and the board), say so, so the person knows a merge is coming.
 - **Before keep,** read back the ticket title and a one-paragraph summary of

package/prompts/dev-qa/skills/crew-lane-agent.md

@@ -419,6 +419,26 @@ before going further, and never change a ticket's `report_type` yourself.
    sets the ticket back to `in_progress` instead of passing it to QA. A ticket
    with no Acceptance section is unaffected.
 
+### Finding where something lives
+
+Before you read or edit, locate the code once, in this order:
+
+1. **The map.** Read the "Repository map" section of this brief (when the
+   repository has one) and the repository's own instructions file, which may
+   also say where things live.
+2. **The symbol tools.** When the Environment section lists code tools, use
+   them for code questions before searching text: find a symbol by name, list
+   its references, read its definition, outline a file. Text search is for
+   strings that are not symbols.
+3. **One broad search.** To find a visible string, search for it once across
+   the whole relevant tree, excluding tests, and prefer registries over
+   components. A search that found only a test file is widened, not
+   narrowed.
+
+Count the calls: if more than three searches have not found the location, say
+so in your progress comment and ask for the map or the person's pointer
+rather than continuing to search.
+
 ## Step 4 — you never merge, and you never deploy
 
 **Nothing you do touches the base branch.** The release phase takes every