feat: integrate framework files into monorepo under packages/mosaic/framework/
Moves all Mosaic framework runtime files from the separate bootstrap repo into the monorepo as canonical source. The @mosaic/mosaic npm package now ships the complete framework — bin scripts, runtime configs, tools, and templates — enabling standalone installation via npm install. Structure: packages/mosaic/framework/ ├── bin/ 28 CLI scripts (mosaic, mosaic-doctor, mosaic-sync-skills, etc.) ├── runtime/ Runtime adapters (claude, codex, opencode, pi, mcp) ├── tools/ Shell tooling (git, prdy, orchestrator, quality, etc.) ├── templates/ Agent and repo templates ├── defaults/ Default identity files (AGENTS.md, STANDARDS.md, SOUL.md, etc.) ├── install.sh Legacy bash installer └── remote-install.sh One-liner remote installer Key files with Pi support and recent fixes: - bin/mosaic: launch_pi() with skills-local loop - bin/mosaic-doctor: --fix auto-wiring for all 4 harnesses - bin/mosaic-sync-skills: Pi as 4th link target, symlink-aware find - bin/mosaic-link-runtime-assets: Pi settings.json patching - bin/mosaic-migrate-local-skills: Pi skill roots, symlink find - runtime/pi/RUNTIME.md + mosaic-extension.ts Package ships 251 framework files in the npm tarball (278KB compressed).
This commit is contained in:
@@ -0,0 +1,52 @@
|
||||
# Adapter Contract
|
||||
|
||||
Runtime adapters translate task commands into concrete worker invocations.
|
||||
|
||||
## Minimal Contract
|
||||
|
||||
Each task should define either:
|
||||
|
||||
1. `command` directly in `tasks.json`, or
|
||||
2. controller-level `worker.command_template` in `.mosaic/orchestrator/config.json`
|
||||
|
||||
`command_template` may use:
|
||||
|
||||
- `{task_id}`
|
||||
- `{task_title}`
|
||||
- `{task_file}`
|
||||
|
||||
## Examples
|
||||
|
||||
Codex:
|
||||
|
||||
```json
|
||||
{
|
||||
"worker": {
|
||||
"command_template": "codex \"run task {task_id}: {task_title}\""
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
Claude:
|
||||
|
||||
```json
|
||||
{
|
||||
"worker": {
|
||||
"command_template": "claude -p \"Execute task {task_id}: {task_title}\""
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
OpenCode:
|
||||
|
||||
```json
|
||||
{
|
||||
"worker": {
|
||||
"command_template": "opencode \"execute task {task_id}: {task_title}\""
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
## Recommendation
|
||||
|
||||
Prefer explicit per-task `command` for deterministic execution and auditability.
|
||||
Reference in New Issue
Block a user