@theihtisham/agent-shadow-brain 7.22.0 → 7.22.1

package/docs/SHOWCASE.md

@@ -1,87 +1,87 @@
-# Workspace showcase
-
-The images show the 7.1.4 workspace with synthetic projects, memory records, reviews, and links. The Project Kit images use a separate persistent synthetic project. The live views use scripted local MCP calls. Displayed phases come from explicit reports, and durations come from measured calls in that demo.
-
-```bash
-shadow-brain demo workspace --port 0
-```
-
-Open the printed **Workspace** or **Live view** address. Use `--no-activity` for a fixed initial journal snapshot.
-
-## Project Kit
-
-In a project-local workspace, inspect observed stack markers and declared checks. Save a knowledge record and use it when drafting a skill for the selected client.
-
-![Project Kit showing observed stack evidence and local knowledge controls](assets/7.1.4-project-kit.png)
-
-Review the generated `SKILL.md` and its destination before applying it. The preview includes the user-supplied requirement and available checks.
-
-![Generated project skill preview with the target path and Markdown](assets/7.1.4-project-skill-preview.png)
-
-### Reported memory outcomes
-
-Record an observed result with a task, rating, reason, and optional references. The saved card shows the reporter and gives the user a way to remove the report. The switch controls whether later adaptive retrieval can use the reports.
-
-![Project Kit with a user-reported useful outcome and an influence toggle](assets/7.1.4-learning.png)
-
-The next matching task shows the report's signed contribution alongside the other ranking signals.
-
-![Context Lab showing a positive Project task feedback contribution and user attribution](assets/7.1.4-outcome-ranking.png)
-
-## Overview and attention queue
-
-Choose the project scope, review source coverage, and open a record from the attention queue. The queue flags conditions that merit inspection, including contested records and missing references.
-
-![Overview and the project memory attention queue](assets/7.1.4-overview.png)
-
-## Context Lab
-
-Assemble a brief, check its estimated tokens and rendered characters, then expand a candidate to see matched fields, ranking contributions, or a recorded link path.
-
-![Context Lab with task settings, brief metrics, and retrieval stages](assets/7.1.4-context-lab.png)
-
-### Compare profiles
-
-Compare the same task and scope with Adaptive and Legacy. The result lists which memories each profile adds and shows their estimated usage.
-
-![Adaptive and legacy comparison for the same task](assets/7.1.4-comparison.png)
-
-## Memory review and graph
-
-Inspect a saved record, its recorded references, and manual review controls. A review change is recorded in revision history.
-
-![Memory inspector with saved content, references, and review controls](assets/7.1.4-memory-review.png)
-
-Select an edge or focus the recorded relationships around one memory. The workspace distinguishes these relations from project membership and recording-agent links.
-
-![Focused graph showing recorded memory links and the inspector](assets/7.1.4-graph.png)
-
-## Integrations and features
-
-Read the documented capabilities and generate a setup example for the client. A project skill-file check and a live client handshake provide different evidence.
-
-![Integration cards and local diagnostics](assets/7.1.4-integrations.png)
-
-Choose when context, session briefings, and activity are available. The workspace keeps activity visibility and journal recording as separate controls.
-
-![The five runtime feature controls](assets/7.1.4-features.png)
-
-## Live operations and recorded replay
-
-Select a session or event to inspect the available history. The session network, timeline, and charts distinguish measured tool activity from explicit host reports.
-
-![Live operations with the session network and measured timing](assets/7.1.4-live.png)
-
-Replay navigates the loaded journal slice. Move to an event with the slider or step controls and return to the live stream when finished.
-
-![Journal replay controls over recorded events](assets/7.1.4-replay.png)
-
-![Animated capture of scripted local MCP activity and replay](assets/live-v7.1.4.gif)
-
-## Mobile layout
-
-Use the workspace on a narrow viewport to inspect the same saved records and context.
-
-![Workspace at a mobile viewport](assets/7.1.4-mobile.png)
-
-[Project Kit guide](PROJECT_KIT.md) · [Context Lab guide](CONTEXT_LAB.md) · [Workspace guide](WORKSPACE.md) · [Client integrations](INTEGRATIONS.md)
+# Workspace showcase
+
+The images show the 7.1.4 workspace with synthetic projects, memory records, reviews, and links. The Project Kit images use a separate persistent synthetic project. The live views use scripted local MCP calls. Displayed phases come from explicit reports, and durations come from measured calls in that demo.
+
+```bash
+shadow-brain demo workspace --port 0
+```
+
+Open the printed **Workspace** or **Live view** address. Use `--no-activity` for a fixed initial journal snapshot.
+
+## Project Kit
+
+In a project-local workspace, inspect observed stack markers and declared checks. Save a knowledge record and use it when drafting a skill for the selected client.
+
+![Project Kit showing observed stack evidence and local knowledge controls](assets/7.1.4-project-kit.png)
+
+Review the generated `SKILL.md` and its destination before applying it. The preview includes the user-supplied requirement and available checks.
+
+![Generated project skill preview with the target path and Markdown](assets/7.1.4-project-skill-preview.png)
+
+### Reported memory outcomes
+
+Record an observed result with a task, rating, reason, and optional references. The saved card shows the reporter and gives the user a way to remove the report. The switch controls whether later adaptive retrieval can use the reports.
+
+![Project Kit with a user-reported useful outcome and an influence toggle](assets/7.1.4-learning.png)
+
+The next matching task shows the report's signed contribution alongside the other ranking signals.
+
+![Context Lab showing a positive Project task feedback contribution and user attribution](assets/7.1.4-outcome-ranking.png)
+
+## Overview and attention queue
+
+Choose the project scope, review source coverage, and open a record from the attention queue. The queue flags conditions that merit inspection, including contested records and missing references.
+
+![Overview and the project memory attention queue](assets/7.1.4-overview.png)
+
+## Context Lab
+
+Assemble a brief, check its estimated tokens and rendered characters, then expand a candidate to see matched fields, ranking contributions, or a recorded link path.
+
+![Context Lab with task settings, brief metrics, and retrieval stages](assets/7.1.4-context-lab.png)
+
+### Compare profiles
+
+Compare the same task and scope with Adaptive and Legacy. The result lists which memories each profile adds and shows their estimated usage.
+
+![Adaptive and legacy comparison for the same task](assets/7.1.4-comparison.png)
+
+## Memory review and graph
+
+Inspect a saved record, its recorded references, and manual review controls. A review change is recorded in revision history.
+
+![Memory inspector with saved content, references, and review controls](assets/7.1.4-memory-review.png)
+
+Select an edge or focus the recorded relationships around one memory. The workspace distinguishes these relations from project membership and recording-agent links.
+
+![Focused graph showing recorded memory links and the inspector](assets/7.1.4-graph.png)
+
+## Integrations and features
+
+Read the documented capabilities and generate a setup example for the client. A project skill-file check and a live client handshake provide different evidence.
+
+![Integration cards and local diagnostics](assets/7.1.4-integrations.png)
+
+Choose when context, session briefings, and activity are available. The workspace keeps activity visibility and journal recording as separate controls.
+
+![The five runtime feature controls](assets/7.1.4-features.png)
+
+## Live operations and recorded replay
+
+Select a session or event to inspect the available history. The session network, timeline, and charts distinguish measured tool activity from explicit host reports.
+
+![Live operations with the session network and measured timing](assets/7.1.4-live.png)
+
+Replay navigates the loaded journal slice. Move to an event with the slider or step controls and return to the live stream when finished.
+
+![Journal replay controls over recorded events](assets/7.1.4-replay.png)
+
+![Animated capture of scripted local MCP activity and replay](assets/live-v7.1.4.gif)
+
+## Mobile layout
+
+Use the workspace on a narrow viewport to inspect the same saved records and context.
+
+![Workspace at a mobile viewport](assets/7.1.4-mobile.png)
+
+[Project Kit guide](PROJECT_KIT.md) · [Context Lab guide](CONTEXT_LAB.md) · [Workspace guide](WORKSPACE.md) · [Client integrations](INTEGRATIONS.md)

package/docs/STATS.md

@@ -1,21 +1,21 @@
-# Package and repository statistics
-
-Last successful refresh: **2026-11-14T11:49:13.195Z**. Counts are snapshots from public npm and GitHub APIs.
-
-| Metric | Count | Coverage |
-| --- | ---: | --- |
-| npm total downloads | **6,229** | 2026-04-10 through 2026-11-13, inclusive |
-| npm latest day | 199 | 2026-11-13 through 2026-11-13 |
-| npm last 7 days | 923 | 2026-11-07 through 2026-11-13 |
-| npm last 30 days | 1,018 | 2026-10-15 through 2026-11-13 |
-| GitHub stars | 0 | At refresh |
-| GitHub forks | 0 | At refresh |
-| GitHub watchers | 0 | At refresh |
-
-The package was created on 2026-04-10. The total sums non-overlapping ranges of at most 365 days from creation through the latest complete day returned by npm. This handles the API's 18-month request limit without silently truncating lifetime counts. npm counts downloads, including automated installs; these are not unique people or active users.
-
-The dedicated **README metrics** workflow refreshes this page and the plain-text README total every two days. The npm README is a snapshot from the published release. A failed request preserves the last successful snapshot.
-
-[Raw snapshot and coverage](npm-metrics.json) · [npm download API documentation](https://github.com/npm/registry/blob/main/docs/download-counts.md) · [Package](https://www.npmjs.com/package/@theihtisham/agent-shadow-brain) · [Repository](https://github.com/theihtishaam/agents-brain)
-
-Historical snapshots in [stats-history.json](stats-history.json) come from the previous monitoring implementation and are not used to calculate this total.
+# Package and repository statistics
+
+Last successful refresh: **2026-11-14T11:49:13.195Z**. Counts are snapshots from public npm and GitHub APIs.
+
+| Metric | Count | Coverage |
+| --- | ---: | --- |
+| npm total downloads | **6,229** | 2026-04-10 through 2026-11-13, inclusive |
+| npm latest day | 199 | 2026-11-13 through 2026-11-13 |
+| npm last 7 days | 923 | 2026-11-07 through 2026-11-13 |
+| npm last 30 days | 1,018 | 2026-10-15 through 2026-11-13 |
+| GitHub stars | 0 | At refresh |
+| GitHub forks | 0 | At refresh |
+| GitHub watchers | 0 | At refresh |
+
+The package was created on 2026-04-10. The total sums non-overlapping ranges of at most 365 days from creation through the latest complete day returned by npm. This handles the API's 18-month request limit without silently truncating lifetime counts. npm counts downloads, including automated installs; these are not unique people or active users.
+
+The dedicated **README metrics** workflow refreshes this page and the plain-text README total every two days. The npm README is a snapshot from the published release. A failed request preserves the last successful snapshot.
+
+[Raw snapshot and coverage](npm-metrics.json) · [npm download API documentation](https://github.com/npm/registry/blob/main/docs/download-counts.md) · [Package](https://www.npmjs.com/package/@theihtisham/agent-shadow-brain) · [Repository](https://github.com/theihtishaam/agents-brain)
+
+Historical snapshots in [stats-history.json](stats-history.json) come from the previous monitoring implementation and are not used to calculate this total.

package/docs/TROUBLESHOOTING.md

@@ -1,42 +1,42 @@
-# Troubleshooting
-
-## The Hub says Workspace unavailable
-
-Keep the launcher running and open the current URL. If an older tab points to a stopped server, start the same project on the same port and refresh. A port of `0` can change each time.
-
-```bash
-cd your-project
-shadow-brain project workspace . --port 62595
-```
-
-Open `http://127.0.0.1:62595/hub`. The status endpoint at `/api/workspace/status` reports the process instance, workspace mode, project scope, and storage health. A reachable server can report a storage error separately. Resolve the storage error before making changes and retain the existing project files. If the port is already in use, check the existing launcher or start on a free port and use the new address.
-
-## The installed version differs from this guide
-
-This guide describes the 7.1.4 build. It requires Node.js 22.13+ in the 22.x line, 24.x, or 26+.
-
-```bash
-node --version
-npm install -g @theihtisham/agent-shadow-brain@latest
-shadow-brain --version
-```
-
-If the command still reports the previous version, locate it with `Get-Command shadow-brain -All` in PowerShell or `command -v shadow-brain` in your shell. Restart the launcher after changing versions. A browser refresh alone continues using the old process.
-
-## The graph or journal is empty
-
-Check the selected project. Save a knowledge record or approve a PDF page to create a graph record. Connect a host using the recipe generated from the same project directory. In **Setup**, enable **Live dashboard activity** and **Record agent activity**. Ask the host to call `project_inspect` or `context_pack`, then look for the event. A reachable workspace and installed skill files are independent of host tool activity.
-
-## A feature setting or claim changed elsewhere
-
-Refresh to read the current revision before retrying. For a task claim, check its owner and lease. After a network failure, retry the same input to reuse the operation key. The work room and journal use different stores and can be inspected independently.
-
-## A PDF page has no text
-
-Image-only pages require OCR. The current Hub extracts a text layer and labels missing text. Upload a text-searchable PDF or save a verified excerpt as explicit project knowledge with its reference.
-
-## A context pack is empty or shorter than expected
-
-Check that the selected project contains relevant active memories, the context feature is enabled, and the token budget allows an excerpt. Try specific project terms. Context estimates describe the rendered pack. Model usage stays unavailable when the host supplies no usage receipts.
-
-[Quickstart](QUICKSTART.md) · [Workspace guide](WORKSPACE.md) · [Integrations](INTEGRATIONS.md)
+# Troubleshooting
+
+## The Hub says Workspace unavailable
+
+Keep the launcher running and open the current URL. If an older tab points to a stopped server, start the same project on the same port and refresh. A port of `0` can change each time.
+
+```bash
+cd your-project
+shadow-brain project workspace . --port 62595
+```
+
+Open `http://127.0.0.1:62595/hub`. The status endpoint at `/api/workspace/status` reports the process instance, workspace mode, project scope, and storage health. A reachable server can report a storage error separately. Resolve the storage error before making changes and retain the existing project files. If the port is already in use, check the existing launcher or start on a free port and use the new address.
+
+## The installed version differs from this guide
+
+This guide describes the 7.1.4 build. It requires Node.js 22.13+ in the 22.x line, 24.x, or 26+.
+
+```bash
+node --version
+npm install -g @theihtisham/agent-shadow-brain@latest
+shadow-brain --version
+```
+
+If the command still reports the previous version, locate it with `Get-Command shadow-brain -All` in PowerShell or `command -v shadow-brain` in your shell. Restart the launcher after changing versions. A browser refresh alone continues using the old process.
+
+## The graph or journal is empty
+
+Check the selected project. Save a knowledge record or approve a PDF page to create a graph record. Connect a host using the recipe generated from the same project directory. In **Setup**, enable **Live dashboard activity** and **Record agent activity**. Ask the host to call `project_inspect` or `context_pack`, then look for the event. A reachable workspace and installed skill files are independent of host tool activity.
+
+## A feature setting or claim changed elsewhere
+
+Refresh to read the current revision before retrying. For a task claim, check its owner and lease. After a network failure, retry the same input to reuse the operation key. The work room and journal use different stores and can be inspected independently.
+
+## A PDF page has no text
+
+Image-only pages require OCR. The current Hub extracts a text layer and labels missing text. Upload a text-searchable PDF or save a verified excerpt as explicit project knowledge with its reference.
+
+## A context pack is empty or shorter than expected
+
+Check that the selected project contains relevant active memories, the context feature is enabled, and the token budget allows an excerpt. Try specific project terms. Context estimates describe the rendered pack. Model usage stays unavailable when the host supplies no usage receipts.
+
+[Quickstart](QUICKSTART.md) · [Workspace guide](WORKSPACE.md) · [Integrations](INTEGRATIONS.md)