remove some local pathing to prevent confusion later

OpenJibo/docs/development-plan.md

@@ -98,11 +98,11 @@ Use these sources as evidence, not as code to copy blindly:
 
 - OpenJibo Node oracle: [open-jibo-link.js](../src/Jibo.Cloud/node/open-jibo-link.js)
 - Current hosted `.NET` cloud: [src/Jibo.Cloud/dotnet](../src/Jibo.Cloud/dotnet)
-- Live captures and robot logs: `C:\Projects\JiboExperiments\artifact-output`
-- Original Pegasus cloud source: `C:\Users\JacobDubin\Downloads\jibo\jibo copy\pegasus`
-- Original SDK and skill source snapshot: `C:\Users\JacobDubin\Downloads\jibo\jibo copy\sdk`
-- JiboOS reference tree: `C:\Projects\JiboOS`
-- JiboOS `V3.1` skill snapshot: `C:\Projects\JiboOS\V3.1\build\opt\jibo\Jibo\Skills\@be`
+- Live captures and robot logs: `.\artifact-output`
+- Original Pegasus cloud source: `..\jibo\pegasus`
+- Original SDK and skill source snapshot: `..\jibo\sdk`
+- JiboOS reference tree: `..\JiboOS`
+- JiboOS skill snapshot: `..\JiboOS\opt\jibo\Jibo\Skills\@be`
 
 The Pegasus tree is especially useful for cloud service intent: `packages/hub` documents `/v1/listen`, `/nlu`, and `/asr`; `packages/lasso` documents credential and provider aggregation; `packages/history` and the architecture materials are useful for future memory and proactivity work.
 

OpenJibo/docs/feature-backlog.md

@@ -348,7 +348,7 @@ Current release theme:
 - Questions:
   - whether `surprise me` should enter the top-level surprise router
   - which categories depend on cloud services
-  - whether stock OS `1.9` differs from the `V3.1` source snapshot
+  - whether stock OS `1.9` differs from the `x.x` source snapshot
 
 ### 16. History / Memory Layer
 

OpenJibo/docs/prompts/cloud-deploy-and-jibo-rcm-path.md

@@ -4,7 +4,7 @@ Prepare OpenJibo for a lightweight v1 cloud deployment and the cleanest practica
 
 Current repo context:
 
-- workspace root: `C:\Projects\JiboExperiments\OpenJibo`
+- workspace root: `.\OpenJibo`
 - the current `.NET` cloud is the target runtime
 - the Node server remains a discovery oracle and fallback
 - latest live-test guidance is in:

OpenJibo/docs/prompts/stt-upgrade-path.md

@@ -4,7 +4,7 @@ Improve the OpenJibo `.NET` speech-to-text path for live robot testing.
 
 Current repo context:
 
-- workspace root: `C:\Projects\JiboExperiments\OpenJibo`
+- workspace root: `.\OpenJibo`
 - current live captures from `2026-04-18` showed that some turns succeeded, but many buffered-audio turns failed before producing a usable transcript
 - the current local `.NET` STT path is in:
   - `src/Jibo.Cloud/dotnet/src/Jibo.Cloud.Infrastructure/Audio/LocalWhisperCppBufferedAudioSttStrategy.cs`