Repository navigation
Spike: memory-sync Skill delivery mechanism on the running Host #188
Description
Parent
What to build
Verified go/no-go answers for how the memory-sync Skill reaches the Orchestrator, with running-Host evidence — no product code changes. Probe against the pinned DSH: skills-service injectability by a plugin; runtime registration at Orchestrator agent scope following the existing agent-scoped pattern; /memory-sync user-token injection behavior; skill-tool availability to the Orchestrator; confirmation-tool availability; any interaction with slash-command parsing. Record the evidence plus the decision: runtime registration, or the documented prompt-section fallback.
Acceptance criteria
- Each mechanism question answered with running-Host evidence, not docs quotes.
- Go/no-go recorded, with the fallback choice if no-go.
- No product-code changes; spike probes removed afterwards.
- Delta versus the older-DSH community docs noted.
Blocked by
- None (can start immediately).
Activity
DoodleBears commentedon Sep 28, 2026
Superseded by #398 via #187: the first-party Sync Skill is declined, so there is no Skill-delivery mechanism to verify. The one mechanism question worth keeping is recorded in #398 as a known unknown (Orchestrator shell Git credentials). Closing as not planned.