[monarchmaisuriya]

Update the Contextualise pin from v0.27.0 (5d47673, merged in #2111) to v0.28.0 (877fafc), ready for artifact review. Submitted by @monarchmaisuriya.

• v0.28.0: attach a whole workspace, and newest-first Attach lists.
  • Whole workspaces: in the Attached button's Workspaces tab, a local workspace is one row, and picking it attaches the workspace rather than one of its repositories. It brings the git repositories its chats changed (read from the tasks Contextualise already records), shows as one Attached row with those repositories listed, is removed as one, and lapses when Paseo no longer has the workspace. When one of its chats ends a turn in another repository, the next new chat gets that one too.
  • Limits: a new chat gets at most 10 attached folders; the rest are named in its prompt. Every folder still passes the existing checks (not home, root, the chat's own folder, Paseo's data folder, or a worktree's folder unless attached as that worktree), now applied when a folder is saved and again when a chat starts.
  • Newest first: the Attached button's Projects and Workspaces tabs, Attach > Project, and Attach > Terminal output list what was active most recently first, and each row leads with its age ("3h"), as Attach > Chat already did. Attach > Tag rows show when they were last tagged. The pickers follow the existing "Show when it was last used" setting.

Permissions

• Unchanged since v0.27.0: the manifest, dependencies, and lockfile. Only the version in package.json changed.
• New behaviour:
  • the plugin's existing links.json gains an attachedWorkspaces key (older versions ignore it);
  • the existing agent.turn_ended handler, after recording a task, updates the folders an attached workspace brings;
  • the existing agent.create hook gives chats those folders the same way it gives attached folders today.
• Network: no new network access.

Tested

• npm test passes (537 tests), and the server and client typechecks are clean at 877fafc.
• Mutation probes on the new behaviour (refresh at turn end, lapse, the worktree rule at chat start, dropping lapsed attachments, the sort) each made a test fail.
• Tried on a real Paseo install: attaching a local workspace, the Attached row with its repositories, and the newest-first order with ages.
• I did not run the registry's scripts/validate.ts locally.

Branch base

One commit on upstream main (23a8cb4); the only change is the pin (artifact commit, tag, and repository commit) in contextualise.json.

🤖 Generated with Claude Code

[paseo-bot]

Contextualise v0.28.0 is approved, @monarchmaisuriya, and I'm merging it now. Nothing is required from you.

The pin moves to v0.28.0 (877fafc). I made no registry edits. The listing keeps using your own OVERVIEW.md and manifest.

Next release, if you touch it: OVERVIEW.md doesn't mention attaching a whole workspace or the Attached button's Workspaces and Projects tabs. A short paragraph there would tell people what a workspace attachment brings and the 10-folder limit per new chat. The overview is written for the listing page, where installation is already shown (overview guidance).

Review data

• Artifact: git https://github.com/monarchmaisuriya/contextualise.git at 877fafc8078c79a7748413cf125720dd62c3c335. Tag v0.28.0 (annotated) resolves to that commit. Previous pin 5d47673fa144c217e8bfbc94bfe78aa2b9560458 (v0.27.0).
• Inspected: both trees fetched at exact commits (no submodules, no hooks, nothing built or run) and compared file by file. paseo-plugin.json, package-lock.json and OVERVIEW.md are byte-identical to v0.27.0; package.json changes only the version. Build stays npm ci --omit=dev --ignore-scripts against the unchanged lockfile, and there are no lifecycle scripts.
• Changed behavior, read in full: server/knowledge/plugin.ts, server/knowledge/links.ts, server/sources.ts, server/tags.ts, shared/linked-projects.ts, the two client files, and the new server/newest-first.ts and client/workspace-rows.ts.
  • Attaching a local workspace saves the git repositories its chats changed (from tasks the plugin already records) under a new attachedWorkspaces key in the existing links.json. They are refreshed when one of that workspace's chats ends a turn and dropped when Paseo no longer has the workspace.
  • Every folder passes the existing checks (not home, root, the chat's own folder, Paseo's data folder, or a worktree's folder unless attached as that worktree), when saved and again at chat start. A new chat gets at most 10 attached folders and the rest are named in its prompt.
  • Attach lists are sorted newest first using the chat list Paseo already returns.
  • The only new filesystem call is lstat of <workspace folder>/.git. No network requests, subprocesses, eval, environment reads, deletions or new dependencies in the added code.
• Registry: scripts/validate.ts passes locally (496 records) and the Validate check passes on the reviewed head. Listing description, media and icon come from the artifact unchanged.
• Not inspected: runtime behavior (plugin code was not executed).