Releases: Dom-303/patternpilot
v0.4.0 — Robustness Bundle
Headline: User-visible operational hygiene
Closes OQ-007 + OQ-008 by integrating existing infrastructure into the user-facing flows that matter.
Stale-data visibility (OQ-007)
When you run intake or on-demand and stale entries exist in your queue, you now see a clear banner:
╭── Stale data notice ──────────────────────────
│ 5 stale entries in project 'demo'
│ drift reasons: rules_fingerprint_drift (3), fallback_decision_data (2)
│ - https://github.com/a/b
│ - https://github.com/c/d
│ - https://github.com/e/f
│
│ Refresh with: npm run re-evaluate -- --project demo --stale-only
╰────────────────────────────────────────────
Plus: every re-evaluate run is now logged to state/re-evaluate-history.json for audit.
Webhook alert channel (OQ-008)
New webhook channel type alongside the existing four (file, github-summary, command, stdout). POSTs JSON to a configurable URL. Slack, Discord, Teams compatible.
{
"type": "webhook",
"name": "team-slack",
"url": "https://hooks.slack.com/services/X/Y/Z",
"minDeliveryPriority": "elevated"
}Auto-resume for stuck jobs (OQ-008)
Automation jobs locked longer than 6h are auto-released when automation-jobs runs. Configurable per job:
{ "name": "nightly-discovery", "autoResumeMinutes": 720 }Set autoResumeMinutes: 0 to opt out.
Internals
- 14 new tests
- Full suite: 864 / 864 passing
- Zero new dependencies, no architecture changes
v0.3.0 — Interactive Onboarding Wizard
Headline: patternpilot init
The new interactive 5-step setup wizard replaces the static getting-started text-print and resolves OQ-006.
What you get
patternpilot init— 5 steps, ≤ 90 seconds at default answers, produces a working setuppatternpilot init --print— non-interactive fallback (byte-identical to legacygetting-startedfor CI)patternpilot init --reconfigure— re-run flow with action menu (add project / re-auth / set default)- Auto-trigger — any patternpilot command without configured projects in TTY prompts to start setup
getting-startedandfirst-runstill work as aliases (zero breaking change)
What's inside
Step 1 — Target detection: auto-scan parents/home for git repos, top 3 by mtime
Step 2 — Context confirm: label/language/files derived; watchlist seed pulled from package.json#dependencies via npm registry
Step 3 — GitHub auth: gh CLI (recommended) or PAT (4-step guided creation with prefilled scopes) or skip
Step 4 — Discovery profile: balanced or focused
Step 5 — First action: nothing / intake / discover / problem (creates landscape)
Bug fixes since v0.2.0
- Wizard now actually creates the project — v0.2.0 (PR #1) shipped a UI walkthrough that didn't call
runBootstrap - First-action and re-run-menu intents are now actually dispatched
- Prompter handles Ctrl+D / EOF cleanly
- Token file enforces 0o600 mode on overwrite
- WSL2 browser-open via
wslview
Internals
- 73+ new tests (foundation, detection, steps, perform-modules, integration)
- Zero new dependencies
- Cross-platform (macOS, Linux, WSL2, Windows)
- Full suite: 849 / 849 passing
Spec / Plan
patternpilot v0.2.0 - first public open-source release
Release Notes v0.2.0
patternpilot v0.2.0 ist die erste oeffentlich publizierte Open-Source-Freigabe des Produkts.
Was neu ist
- lokales Repo-Intelligence-Produkt mit Zielprojekt-Bindung
- gefuehrtes Onboarding mit
getting-started,bootstrapund GitHub-Token-Setup - klare Trennung zwischen
bindings/,projects/,runs/undstate/ - Intake-, Watchlist-, Review- und Readiness-Flow als zusammenhaengender Produktpfad
- visuelle Produkt- und Onboarding-Oberflaeche mit aktualisierten PNG-Assets
- neutrale Beispieloberflaeche statt aktiver Dogfood-Defaults
- dokumentierter Produktstatus mit erfolgreich validiertem Fremdprojekt-Pilot
- npm-Paket-Guardrails, damit lokale Workspace-Daten nicht veroeffentlicht werden
Fuer wen diese Version gedacht ist
Diese Version ist fuer Menschen und Teams, die:
- fremde GitHub-Repositories relativ zum eigenen Produkt bewerten wollen
- einen lokalen, nachvollziehbaren Review- und Intake-Prozess wollen
- ein Open-Source-Tool suchen, das bewusst zwischen Produktcode und lokalem Betriebszustand trennt
Wichtige Produktmerkmale
- lokal-first
- Open Source unter MIT
- nutzbar ohne GitHub App
- stabiler mit verifiziertem GitHub-Token
Schnellster Start
npm install
npm run getting-started
npm run bootstrap -- --project my-project --target ../my-project --label "My Project"Bekannte ehrliche Restpunkte
- der Kern ist
v1-nah, aber Launch-/Distribution-Entscheidungen bleiben bewusst offen - tiefere GitHub-App- und Runtime-Automation sind vorhanden, aber nicht noetig fuer den ersten produktiven Start
- direkte Git-Transportpfade koennen je nach lokaler Umgebung anders robust sein als die GitHub-API selbst