Activity

1. donjor-agent

   added

   dxdeveloper experience, CLIs, skillsdeveloper experience, CLIs, skills

   on Sep 2, 2026
2. donjor-agent

   added the

   Task 🔨

   issue type on Sep 2, 2026
3. donjor

   added a commit that references this issue on Sep 2, 2026

   docs(fork): record the partial retirement of the per-workspace skills…

   ...

   9876bdf
4. donjor

   added a parent issue on Sep 3, 2026

   • guard-seam [Strategy] every ledger action, its guard, no recurrence [📡#443] #445
5. donjor-agent

   changed the title [-]Claude workspace snapshots still carry machine slash commands [📥][/-] [+]Claude workspace snapshots still carry machine slash commands [💡#445][/+] on Sep 3, 2026
6. donjor-agent

   marked this as blocking on Sep 3, 2026

   • retire-test the five conflicting upstream-fixes commits [✨#865] #447
7. donjor-agent commented on Sep 3, 2026

   

   donjor-agentBot

   on Sep 3, 2026

   Author

   More actions

   🤖 claude/anthropic claude-fable-5-1 (high)

   The ledger now records the partial

   #494 merged as 9876bdf7bc, head 5af5455, with no Closes link, so this stays open by design.

   docs/internals/fork-delta.md now carries fix(provider): resolve repo skills per workspace (#188) in both Retired and Kept, which is how the ledger spells a partial. The .1261 walk reduced that commit from 546 insertions across 17 files to 35 insertions across 2 server files. What survives is the cwd-keyed Claude capabilities probe cache at capacity 16 and the slashCommands merge alongside skills in upstream's snapshotForCwd. Everything else, the workspace-skills remote call, its contract schemas, the client atom family, the chat-view preference, and the Codex pair, is retired against upstream bc918e7.

   That remainder is exactly the gap this issue describes, and it is now carried in the stack rather than proposed.

   What is left here

   One decision, not one implementation. The kept remainder is live fork code, so the shape this issue asked for already exists. What is unresolved is where the issue belongs: it reads Untriaged 📥 with Status Inbox, parentless, and the natural home is Slice F, upstream fixes, alongside the retirement it now describes.

   Re-entry trigger. The next upstream tag the fork carries. If that tag merges slashCommands in snapshotForCwd and keys the Claude probe cache on cwd, the kept remainder is superseded and this closes not planned with the Kept row moving to Retired. If it does not, the remainder stays and this issue is the record of why the fork carries it, at which point it takes its slice and a parent.
8. donjor-agent commented on Sep 3, 2026

   

   donjor-agentBot

   on Sep 3, 2026

   Author

   More actions

   🤖 claude/anthropic claude-fable-5-1 (high)

   Correction to the previous comment

   The triage paragraph above is wrong. It was drafted against an earlier read and posted after a thirty-five minute rate-limit block, during which this issue was retyped and attached.

   Live state as of this comment: type Task 🔨, triage Parent 🔗, Status Ready, parent #445, mission Slice F: Upstream fixes, blocking #447, relates to #182. It is neither untriaged nor parentless, and it already sits in the slice that comment proposed for it.

   Everything above that paragraph stands. The ledger records the partial, the kept remainder is the cwd-keyed Claude probe cache and the slashCommands merge, and the re-entry trigger is unchanged: the next upstream tag the fork carries.

   One inconsistency worth a look: the title marker reads 💡 while the type field reads Task 🔨.
9. donjor-agent commented on Sep 3, 2026

   

   donjor-agentBot

   on Sep 3, 2026

   Author

   More actions

   🤖 claude/anthropic claude-fable-5-1 (high)

   The kept remainder is live at 3d3dd35049

   Both "Done when" conditions hold in the fork stack. Verified at hyprws@3d3dd35049.

   No second implementation

   $ grep -rn "workspaceSkills" apps/server/src
   (no matches)
   

   The RPC, its contract schemas, the client atom family, the chat-view preference, and the Codex pair all came out at the v0.0.39-nightly.20260902.1261 walk.

   Project commands reach a worktree thread

   apps/server/src/provider/Drivers/ClaudeDriver.ts keys the capabilities probe on cwd and merges its slashCommands into upstream's snapshotForCwd:

   const capabilitiesProbeCache = yield* Cache.make({
     capacity: CAPABILITIES_PROBE_CACHE_CAPACITY, // 16
     lookup: (probeCwd: string) => probeClaudeCapabilities(effectiveConfig, processEnv, probeCwd),
   });

   slashCommands: dedupeSlashCommands([
     ...machineSnapshot.slashCommands,
     ...(capabilities?.slashCommands ?? []),
   ]),

   apps/server/src/provider/Layers/ProviderRegistry.ts carries the per-cwd snapshot to the client through upsertProviderWorkspaceSnapshot. Its tests cover the workspace slashCommands path:

   $ vp test run apps/server/src/provider/Layers/ProviderRegistry.test.ts
    Test Files  1 passed (1)
         Tests  41 passed (41)
   

   Ledger

   docs/internals/fork-delta.md records the partial through PR #494 (9876bdf7bc). fix(provider): resolve repo skills per workspace (#188) appears in Retired against pingdotgg/t3code#9210 and in Kept with the remainder named: cwd-keyed probe cache at capacity 16, slashCommands merged beside skills.

   Scope

   The proof above is code and unit level. No browser pass was run for the Claude menu itself. The re-entry trigger from the prior comment stands: if a later upstream tag keys the probe cache on cwd and merges slashCommands, the Kept row moves to Retired.
10. donjor-agent

    closed this as completedon Sep 3, 2026
11. donjor-agent

    unmarked this as blocking on Sep 3, 2026

    • retire-test the five conflicting upstream-fixes commits [✨#865] #447
12. donjor-agent

    removed a parent issue on Sep 16, 2026

    • guard-seam [Strategy] every ledger action, its guard, no recurrence [📡#443] #445
13. donjor-agent

    added a parent issue on Sep 16, 2026

    • hot seams shrink behind fork-owned boundaries [💡#665] #446
14. donjor-agent

    changed the title [-]Claude workspace snapshots still carry machine slash commands [💡#445][/-] [+]Claude workspace snapshots still carry machine slash commands [✨#446][/+] on Sep 16, 2026