docs: describe the real defaults/add-ons/packs model in CONTRIBUTING
WHY THIS MATTERS CONTRIBUTING.md still told workflow contributors to set metadata.mike-availability to "system" to publish a system workflow. That contract died in the workflows restructure: a contributor following the docs would see their workflow silently ship as an add-on instead, with no error anywhere. Stale contributor docs are how an open-source project burns its first-time contributors. WHAT THE DOCS NOW SAY Five defaults are hardcoded in DEFAULT_WORKFLOW_IDS (backend/src/lib/workflowCatalog.ts) and install once per user as editable, deletable copies; every other repository workflow ships in the Add-ons catalog and imports as an independent copy; packs come from pack.yaml, which must list exactly the workflow directories it contains; mike-availability is deprecated and ignored; CI regenerates the catalog from the stamped source commit and fails on drift. Found by review of PR #309. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E4PXCdenNH5Mqhm5Sre9Zs
| Repository | open-legal-products/mike |
|---|---|
| Author | Amal <mamalanand3@gmail.com> |
| Authored | |
| Committed | |
| Parents | 0ca6c460 |
| Stats | 1 file changed , +27 , -3 |
| Part of | Refactor workflows into defaults, add-ons, and quick actions |
Capture this commit into my fork
Download a Markdown prompt that tells Claude how to port this
exact commit into your working tree. Run it via
claude -p < capture-commit-3a4480f2.md
from inside the repo you want the change in.