mosaicstack/stack

Fork 0

Files

History

Jason Woltje 6ad96c37cd

ci/woodpecker/pr/ci Pipeline was successful

Details

ci/woodpecker/push/ci Pipeline was successful

Details

feat(framework): P1+P2 — public sanitization + blocking CI gate

Adds tools/quality/scripts/verify-sanitized.sh (two-class, self-tested) wired
blocking in .woodpecker/ci.yml; sanitizes operator identity from the public
framework package so the gate is green.

- purge jarvis/jason/woltje/PDA across 26 files -> generic
- delete jarvis-loop.json overlay; add neutral examples/{personas,overlays}
- relocate maintainer AUDIT to docs/audits/; delete 2 jarvis-brain rule blocks
- neutralize SOUL persona; strip "(Policy: Jason ...)" keeping universal rule
- test fixtures jason.woltje -> ci-bot (both git tests pass)

Deferred (tracked): private third-party host (uscllc) genericization.

Refs #542, closes #571

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-20 20:57:08 -05:00

_lib.sh

fix(framework/tools): wrapper hardening — TLS validation, cred-path fallback, no-CI fast-exit (#551 )

2026-06-20 10:16:38 +00:00

ci-wait.sh

feat(framework/tools): orchestration helpers — lane-brief.sh + ci-wait.sh (#547 )

2026-06-18 22:08:40 +00:00

pipeline-list.sh

fix(framework/tools): wrapper hardening — TLS validation, cred-path fallback, no-CI fast-exit (#551 )

2026-06-20 10:16:38 +00:00

pipeline-status.sh

fix(framework/tools): wrapper hardening — TLS validation, cred-path fallback, no-CI fast-exit (#551 )

2026-06-20 10:16:38 +00:00

pipeline-trigger.sh

fix(framework/tools): wrapper hardening — TLS validation, cred-path fallback, no-CI fast-exit (#551 )

2026-06-20 10:16:38 +00:00

README.md

feat(framework): P1+P2 — public sanitization + blocking CI gate

2026-06-20 20:57:08 -05:00

test-ci-wait-exit-matrix.sh

feat(framework/tools): orchestration helpers — lane-brief.sh + ci-wait.sh (#547 )

2026-06-18 22:08:40 +00:00

README.md

Woodpecker CI Tool Suite

Interact with Woodpecker CI pipelines (list builds, check status, trigger builds).

Prerequisites

jq and curl installed
Woodpecker credentials in ~/.config/mosaic/credentials.json

Setup

A Woodpecker API token is required. To configure:

Go to Woodpecker CI → User Settings → API
Generate a personal token
Add to credentials.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
`ci-wait.sh`	Block until pipeline(s) reach terminal state

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

# 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

# Block until one or more pipelines finish (event-driven CI wait)
~/.config/mosaic/tools/woodpecker/ci-wait.sh -r usc/uconnect -n 3917 -n 3918