Lineage v0.3.0
·
190 commits
to develop
since this release
Minor release: the one-command non-coder receiver path lands.
Added
lineage add <ref> [--yes](#77): fetches a published package, shows what it contains (skills, workflows, agents, policies, declared capabilities), asks permission, then enables it - three commands (package pull,package inspect,enable) collapsed into one.docs/bootstrap-prompt.md(#98): the canonical copy-paste prompt for non-coder receivers, now embedded per-package on the website's/packages/<name>pages. Written and reviewed for the prompt-injection boundary on paper; adversarial testing against a real hostile package is tracked separately and not yet done - see the issue before treating this as a hardened security boundary.- Grouped, per-subcommand CLI help (
lineage <cmd> -hnow works correctly instead of misreading-has a positional argument) andlineage version/--version.
Also included
- ADR 0012 synced: decision 4/5 corrected (curl installer, not npx), Verified In Production section, stale issue-number fix.
Still pre-V1. Open before the full "Enable distribution" milestone closes: unified local/pulled artifact processing (#71), the package setup playbook (#72), and #98's adversarial hardening pass and real end-to-end verification.