Hydrate and cache remote skill repositories #118

New issue

Closed

opened 2026-07-28 19:09:48 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-07-28 19:09:48 +00:00

Member

Outcome

Allow host configuration to declare remote Git repositories that contain ordinary skill catalogs, then project those skills through the same native load-point path used for local eligible repositories.

Contract

Each remote skill source declares a clone URL, optional ref, optional relative skill path, and optional harness allowlist.
Agent-compose stores a bare mirror plus a working checkout under its own state directory.
A fresh cache does no network work. A stale cache refreshes once under a per-source lock.
A failed stale refresh serves the last verified checkout and warns. A first hydration failure fails before native skill links change.
Full commit pins already present in the mirror skip refresh because their content is immutable.
Cache identities derive from the complete remote locator so repositories and refs cannot collide.
Remote skills obey the existing local overlay order and foreign-entry preservation rules.
Code, docs, and diagnostics describe this as agent-compose behavior without naming another product as its source.

Acceptance

Tests prove first hydration, TTL reuse, stale refresh, offline reuse, ref checkout, collision-safe cache keys, and first-use failure safety.
Convergence tests prove remote and local skill repositories share the existing precedence and ownership behavior.
docs/FEATURES.md and the cascade configuration walkthrough describe the shipped surface.
ward exec test and ward exec smoke pass.
The implementation lands on canonical main and closes this issue.

## Outcome Allow host configuration to declare remote Git repositories that contain ordinary skill catalogs, then project those skills through the same native load-point path used for local eligible repositories. ## Contract * Each remote skill source declares a clone URL, optional ref, optional relative skill path, and optional harness allowlist. * Agent-compose stores a bare mirror plus a working checkout under its own state directory. * A fresh cache does no network work. A stale cache refreshes once under a per-source lock. * A failed stale refresh serves the last verified checkout and warns. A first hydration failure fails before native skill links change. * Full commit pins already present in the mirror skip refresh because their content is immutable. * Cache identities derive from the complete remote locator so repositories and refs cannot collide. * Remote skills obey the existing local overlay order and foreign-entry preservation rules. * Code, docs, and diagnostics describe this as agent-compose behavior without naming another product as its source. ## Acceptance * Tests prove first hydration, TTL reuse, stale refresh, offline reuse, ref checkout, collision-safe cache keys, and first-use failure safety. * Convergence tests prove remote and local skill repositories share the existing precedence and ownership behavior. * docs/FEATURES.md and the cascade configuration walkthrough describe the shipped surface. * `ward exec test` and `ward exec smoke` pass. * The implementation lands on canonical main and closes this issue.

coilyco-ops referenced this issue from a commit

2026-07-28 19:22:24 +00:00

feat: hydrate remote skill catalogs

coilyco-ops commented

2026-07-28 19:25:29 +00:00

Author

Member

Implemented and landed on canonical main as feat: hydrate remote skill catalogs. Full repository validation, isolated host-convergence smoke, and cross-platform release builds pass. The automatic release event did not appear after the post-push window, so the operator-only release recovery is tracked separately in #119.

Implemented and landed on canonical `main` as `feat: hydrate remote skill catalogs`. Full repository validation, isolated host-convergence smoke, and cross-platform release builds pass. The automatic release event did not appear after the post-push window, so the operator-only release recovery is tracked separately in #119.

coilyco-ops closed this issue

2026-07-28 19:25:33 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-flight-deck/agent-compose#118

No description provided.

Rows
Columns