[monarchmaisuriya]

Update the Contextualise pin from v0.17.2 (a697bc6) to v0.18.0 (3826875), ready for artifact review. Submitted by @monarchmaisuriya.

• Project knowledge reaches agents: the project map and the tool server's instructions now name the paseo-contextualise server and say when to search it; Claude agents get the four read tools on their first turn (alwaysLoad); search ranks a project's own docs, decisions, and conventions above code symbols and leaves test-file symbols out unless asked.
• Cleaner index for folders of repositories: a project folder that is not a git repository but holds repositories now indexes only the files each repository's index lists, so ignored folders (virtual environments, build output) stay out.
• Calmer screens: one shared search box, copy button, and list across screens; a one-line header on the Project knowledge screen; a Project knowledge tab in each workspace; one Save beside the edited setting; a usage line ("N of M agents used project knowledge").
• Fixes: secret removal, committed symbolic links, prompt markers, slow glob and heading matching, worker time limits, parser memory, and more (see the release notes).

Permissions

• New UI surface: a workspace panel (addWorkspacePanel, "Project knowledge") and two Command Center items.
• New plugin RPCs: knowledge.usage and knowledge.project-for (takes a workspace id; the folder is looked up through Paseo's workspace list).
• The injected MCP server entry now sets alwaysLoad: true (only Claude reads it; other providers drop it).
• Git: every call now adds --no-optional-locks -c core.fsmonitor=false, and edited files are hashed with --no-filters. Inside a non-git project folder, nested repositories are read with git ls-files only.
• New local file per project: daily usage counts (<hash>.usage.json, mode 0600) holding counts and short hashes only; no queries, paths, or agent ids.
• requirements.paseo is unchanged (>=0.13.0).

Tested

• npm test passes (346 tests) and typecheck is clean at 3826875.
• The screens were checked on a throwaway Paseo 0.14.0 daemon with fake data, desktop and phone width.
• Updated from git to v0.18.0 on my own Paseo 0.14.0 daemon, where it is running.
• npm run validate in this repository: "438 record(s) are well-formed".

🤖 Generated with Claude Code

[paseo-bot]

Contextualise v0.18.0 is approved, @monarchmaisuriya. I updated the registry review date and retained your overview, description and interface images. No action is required from you.

For a later release, add a Project knowledge screenshot so users can see the new workspace panel before installing. Media guidance.

Review data

• Policy: main REVIEW.md blob 3c5e763c9565b93ea33fa48c9aeb83e415c72d67. Reviewed registry head 99821d590b3481276ad7a5214e5479871b3215b6; initial head f10553c9cb0e75b15feb6fdf7cf3ac29df38959a. Read this PR, the original submission #1348 and accepted PR #1349, and the prior v0.17.2 review #1502. Submitter and source ownership agree.
• Independently fetched and compared Git artifacts https://github.com/monarchmaisuriya/contextualise.git, root commits a697bc643d4ca22b6f78a3d7ce3b4aa2b031d239 → 3826875a6e943c6f572a7b79f4da163c85b36063. The v0.18.0 tag resolves to the proposed commit. No hooks or submodules; archive paths/types checked before confined extraction. Archive SHA-256 old e6db6ca05af49bc08ea374a7f81187bc95fdc98ac1688d3aa43763cfc64cd83d, new d33e21dbabf8e04b69133c20eadec3a14da10b05090f8badfb3087025ab339ea.
• Inspected the 60-file delta, changed production modules and affected consumers, runtime entries, manifest, package/lock, author overview and listing media. Manifest preparation remains npm ci --omit=dev --ignore-scripts. All 95 production lock entries are unchanged, resolve to npm's registry, carry integrity, and have no marked install hooks. Root dependency declarations agree with the lock. No additional preparation scripts or runtime software installer introduced; dependency implementations and bundled unchanged grammar WASM were not exhaustively audited.
• New usage accounting (server/knowledge/usage.ts:37-91) writes daily counts and short hashes under the plugin's knowledge directory with mode 0600 and 30-day retention. It stores no queries or raw access tokens and adds no external destination. The loopback MCP listener verifies an HMAC token, derives the project scope from it, and counts calls to the same four read tools. The agent-create hook adds alwaysLoad and usage counting; exact server/tool matching now controls automatic permission responses (server/knowledge/plugin.ts:210-215). These are source-derived traces, not exercised requests.
• Indexing now excludes Git symlink/submodule modes, rejects non-regular final file entries and bounds file reads. Git calls use argument arrays, disable fsmonitor/optional locks, and hash edited files without filters; nested repositories in plain folders are listed through their indexes. This is purposeful project indexing, not a claim of a complete filesystem sandbox against concurrent same-user changes. Search weighting uses fixed kind constants and bound query values. Prompt markers and recognized-secret redaction were strengthened.
• Existing attachment/vendor behavior remains: user-selected conversations, terminal output and indexed knowledge reach the receiving agent provider; vendor fetches use existing connectors via background agents. Optional generation sends redacted input to the selected provider. Worker startup now shares a deadline and archives agents created after it expires. Provider/MCP internals enforce their own boundaries; redaction does not guarantee removal of every secret. No new concealed transmission, credential destination, shell interpolation or destructive action found in the changed paths.
• Workspace knowledge reads a workspace ID, resolves its directory through Paseo's workspace list, and displays that project's existing knowledge. UI changes share search/copy/pagination controls and alter settings draft presentation; no new client access source found. Existing English overview/description remain usable, with no registry fallback needed. All three existing interface images and the icon are byte-identical to the accepted artifact and return 200 image/png at the exact new commit; viewed the Tags screenshot. Refreshing media for new capabilities is optional advice.
• Trusted current-main online changed-record validation passes: 438 well-formed records, one matching artifact, zero skipped. Trusted registry tests pass 189/189. Plugin/dependency code and plugin tests were never installed, built, imported or executed. No live UI, vendor, indexing or provider QA performed; author test claims were read, not reproduced. Final-head Validate run 41234739745 passed before approval.