@f5-sales-demo/xcsh 19.70.2 → 19.71.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "type": "module",
3
3
  "name": "@f5-sales-demo/xcsh",
4
- "version": "19.70.2",
4
+ "version": "19.71.0",
5
5
  "description": "Coding agent CLI with read, bash, edit, write tools and session management",
6
6
  "homepage": "https://github.com/f5-sales-demo/xcsh",
7
7
  "author": "Can Boluk",
@@ -56,13 +56,13 @@
56
56
  "dependencies": {
57
57
  "@agentclientprotocol/sdk": "0.16.1",
58
58
  "@mozilla/readability": "^0.6",
59
- "@f5-sales-demo/xcsh-stats": "19.70.2",
60
- "@f5-sales-demo/pi-agent-core": "19.70.2",
61
- "@f5-sales-demo/pi-ai": "19.70.2",
62
- "@f5-sales-demo/pi-natives": "19.70.2",
63
- "@f5-sales-demo/pi-resource-management": "19.70.2",
64
- "@f5-sales-demo/pi-tui": "19.70.2",
65
- "@f5-sales-demo/pi-utils": "19.70.2",
59
+ "@f5-sales-demo/xcsh-stats": "19.71.0",
60
+ "@f5-sales-demo/pi-agent-core": "19.71.0",
61
+ "@f5-sales-demo/pi-ai": "19.71.0",
62
+ "@f5-sales-demo/pi-natives": "19.71.0",
63
+ "@f5-sales-demo/pi-resource-management": "19.71.0",
64
+ "@f5-sales-demo/pi-tui": "19.71.0",
65
+ "@f5-sales-demo/pi-utils": "19.71.0",
66
66
  "@sinclair/typebox": "^0.34",
67
67
  "@xterm/headless": "^6.0",
68
68
  "ajv": "^8.20",
@@ -17,17 +17,17 @@ export interface BuildInfo {
17
17
  }
18
18
 
19
19
  export const BUILD_INFO: BuildInfo = {
20
- "version": "19.70.2",
21
- "commit": "05387057f93d75a54a49918fd0a62f29047ecf16",
22
- "shortCommit": "0538705",
20
+ "version": "19.71.0",
21
+ "commit": "820c7a81493686a02db8bb81e628c6437143bd79",
22
+ "shortCommit": "820c7a8",
23
23
  "branch": "main",
24
- "tag": "v19.70.2",
25
- "commitDate": "2026-07-22T00:53:13Z",
26
- "buildDate": "2026-07-22T01:20:48.788Z",
24
+ "tag": "v19.71.0",
25
+ "commitDate": "2026-07-22T01:27:46Z",
26
+ "buildDate": "2026-07-22T01:52:11.339Z",
27
27
  "dirty": true,
28
28
  "prNumber": "",
29
29
  "repoUrl": "https://github.com/f5-sales-demo/xcsh",
30
30
  "repoSlug": "f5-sales-demo/xcsh",
31
- "commitUrl": "https://github.com/f5-sales-demo/xcsh/commit/05387057f93d75a54a49918fd0a62f29047ecf16",
32
- "releaseUrl": "https://github.com/f5-sales-demo/xcsh/releases/tag/v19.70.2"
31
+ "commitUrl": "https://github.com/f5-sales-demo/xcsh/commit/820c7a81493686a02db8bb81e628c6437143bd79",
32
+ "releaseUrl": "https://github.com/f5-sales-demo/xcsh/releases/tag/v19.71.0"
33
33
  };
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: librarian
3
- description: Researches external libraries and APIs by reading source code. Returns definitive, source-verified answers.
3
+ description: Researches external libraries, APIs, and authoritative documentation by reading source code and vendor docs. Returns definitive, source-verified answers.
4
4
  tools: read, grep, find, bash, lsp, web_search, ast_grep
5
5
  model: pi/smol
6
6
  thinking-level: minimal
@@ -17,24 +17,25 @@ output:
17
17
  properties:
18
18
  repo:
19
19
  metadata:
20
- description: GitHub repo (owner/name) or package name
20
+ description: GitHub repo (owner/name), package name, or documentation site/domain
21
21
  type: string
22
22
  path:
23
23
  metadata:
24
- description: File path within the repo or node_modules
24
+ description: File path within the repo or node_modules, or the full page URL for a documentation source
25
25
  type: string
26
+ excerpt:
27
+ metadata:
28
+ description: Verbatim code or doc excerpt proving the claim
29
+ type: string
30
+ optionalProperties:
26
31
  line_start:
27
32
  metadata:
28
- description: First relevant line (1-indexed)
33
+ description: First relevant line (1-indexed); omit for documentation sources
29
34
  type: number
30
35
  line_end:
31
36
  metadata:
32
- description: Last relevant line (1-indexed)
37
+ description: Last relevant line (1-indexed); omit for documentation sources
33
38
  type: number
34
- excerpt:
35
- metadata:
36
- description: Verbatim code or doc excerpt proving the claim
37
- type: string
38
39
  api:
39
40
  metadata:
40
41
  description: Extracted API signatures, types, or config relevant to the question
@@ -79,10 +80,12 @@ Before acting, determine what kind of question this is:
79
80
  - **Conceptual**: "How do I use X?", "Best practice for Y?" — Prioritize types, docs, and usage examples.
80
81
  - **Implementation**: "How does X implement Y?", "Show me the source of Z" — Clone and read the actual code.
81
82
  - **Behavioral**: "Why does X behave this way?", "What's the default for Y?" — Read implementation, find where values are set, check tests.
83
+ - **Documentation**: "What are the steps to configure X?", "What does the vendor doc say about Y?" — Fetch authoritative documentation pages and quote them verbatim.
82
84
 
83
85
  ## 2. Locate the source (local first)
84
86
  - **Check local dependencies first**: Look in `node_modules/<package>`, `vendor/`, or similar. If the library is already installed, read it there — no clone needed. Prioritize `.d.ts` type definitions and exported types.
85
87
  - **Otherwise clone**: Use `web_search` to find the canonical repo, then `git clone --depth 1 <url> /tmp/librarian-<name>`.
88
+ - **For documentation questions**: Use `web_search` to find the authoritative page (official docs or vendor portal), then use `read` on the URL to fetch page content. Quote verbatim excerpts with their exact URLs and cross-reference at least two pages.
86
89
  - **For a specific version**: Clone then `git checkout tags/<version>`, or read the locally installed version.
87
90
 
88
91
  ## 3. Investigate
@@ -116,6 +119,6 @@ Before acting, determine what kind of question this is:
116
119
  </directives>
117
120
 
118
121
  <critical>
119
- Source code is truth. Documentation is aspiration. Training data is history.
122
+ Source code is truth. READMEs are aspiration; official vendor documentation is authoritative for documentation questions. Training data is history.
120
123
  You **MUST** keep going until you have a definitive, source-verified answer.
121
124
  </critical>