b38cfac760
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).
59 lines
1.4 KiB
Markdown
59 lines
1.4 KiB
Markdown
# Woodpecker CI Tool Suite
|
|
|
|
Interact with Woodpecker CI pipelines (list builds, check status, trigger builds).
|
|
|
|
## Prerequisites
|
|
|
|
- `jq` and `curl` installed
|
|
- Woodpecker credentials in `~/src/jarvis-brain/credentials.json`
|
|
|
|
## Setup
|
|
|
|
A Woodpecker API token is required. To configure:
|
|
|
|
1. Go to Woodpecker CI → User Settings → API
|
|
2. Generate a personal token
|
|
3. Add to `credentials.json`:
|
|
|
|
```json
|
|
{
|
|
"woodpecker": {
|
|
"url": "https://ci.mosaicstack.dev",
|
|
"token": "YOUR_TOKEN_HERE"
|
|
}
|
|
}
|
|
```
|
|
|
|
## Scripts
|
|
|
|
| Script | Purpose |
|
|
| --------------------- | ------------------------------------------- |
|
|
| `pipeline-list.sh` | List recent pipelines for a repo |
|
|
| `pipeline-status.sh` | Get status of a specific or latest pipeline |
|
|
| `pipeline-trigger.sh` | Trigger a new pipeline build |
|
|
|
|
## Common Options
|
|
|
|
- `-r owner/repo` — Repository (auto-detected from git remote if omitted)
|
|
- `-f json` — JSON output (default: table)
|
|
- `-h` — Show help
|
|
|
|
## API Reference
|
|
|
|
- Base URL: `https://ci.mosaicstack.dev`
|
|
- API prefix: `/api/`
|
|
- Auth: Bearer token in `Authorization` header
|
|
|
|
## Examples
|
|
|
|
```bash
|
|
# List recent builds
|
|
~/.config/mosaic/tools/woodpecker/pipeline-list.sh
|
|
|
|
# Check latest build status
|
|
~/.config/mosaic/tools/woodpecker/pipeline-status.sh
|
|
|
|
# Trigger a build on a specific branch
|
|
~/.config/mosaic/tools/woodpecker/pipeline-trigger.sh -b feature/my-branch
|
|
```
|