# Changelog ## 0.5.0: Lean Symbiont Lifecycle - [Identity] Keep every local symbiont under its original `-delivery` name, use `fss: true` as its sufficient marker, and express lifecycle only through root `status`. - [Adaptation] Move between `draft`, `stable`, and temporary `deprecated` status without maturity modes, percentages, sibling skills, or rename cycles. - [Apoptosis] Self-remove when verified host self-sufficiency reaches `0.9` confidence while unresolved work, unique guidance, missing truth ownership, or unsafe cleanup blocks deletion. - [Opt-Out] Disable all repository FSS activity through top-level `fss: false` in `.agents/skills/settings.json` or `settings.toml`; disabling wins across formats, malformed settings fail closed, and existing symbionts remain untouched. - [Progressive Disclosure] Reduce the always-loaded root to one tested executable kernel and route canonical-work, knowledge, and OKF detail through packaged conditional references. ## 0.4.0: Cohesive Symbiont Loop - [Protocol] Establish one explicit operating path from host discovery and feature identification through coupling, bounded routing, gated work, reconciliation, and evidence-led evolution. - [Integrity] Add a close-the-loop invariant so every guided change reconciles canonical work, affected knowledge, declared evidence, and current lifecycle pressure. - [Identity] Clarify that one feature receives one continuous local support skill, while the packaged portable protocol remains its owner rather than creating a nested symbiont for itself. - [Clarity] Align the package description and human-facing symbiogenesis loop with the executable skill contract. ## 0.3.0: Feature Symbiogenesis - [Rename] Adopt `pi-feature-symbiont` and FSS as the single public identity, with a portable protocol that creates project-local feature symbionts. - [Symbiosis] Couple each local FSS to its host's canonical work, documentation, validation, and knowledge systems; grow local structure only for missing functions. - [Control Plane] Make the root FSS `SKILL.md` both the feature operating protocol and the meta-index constitution for concept admission, grammar, routing, validation, and lifecycle. - [OKF] Resolve the latest published Open Knowledge Format specification at execution time instead of pinning a minor version; migrate affected bundles coherently and keep FSS metadata namespaced. - [Knowledge] Absorb the useful repomap invariants into an OKF FSS bundle: one responsibility per concept, domain links before source anchors, compact progressive disclosure, and evidence-backed freshness. - [Priorities] Separate authority, retrieval, maintenance, and verification into independent knowledge axes without leaking them into product or roadmap priority. - [Indexing] Define typed domain, interface, invariant, procedure, decision, failure-mode, and evidence concepts plus task-specific retrieval and source-change invalidation. - [Canonical State] Preserve `SKILL.md` plus source concepts as canonical and treat every generated index as a disposable, reconstructible projection. - [Scope] Grow the knowledge topology only under recurring reconstruction pressure; keep small features compact and forbid automatic empty trees or nested index files. - [Layout] Keep typed knowledge directories at the feature-skill root; omit the redundant `concepts/` namespace to shorten OKF IDs and links. - [Documentation] Infer documentation ownership automatically: extend living host documentation when established, otherwise grow feature-local OKF knowledge, and migrate coherently when ownership changes. ## 0.2.0: Feature Symbiont Symbiogenesis - [FSS] Reframe a feature symbiont as one continuous project-local support skill whose delivery and knowledge emphasis follows feature reality. - [Maturity] Let a stabilized symbiont preserve `fss: true`, adopt the shortest natural feature name, consolidate insights into durable knowledge, and remove stale task routing without retiring. - [Regrowth] Let the same mature feature skill regain delivery guidance and canonical open work when refactoring, migration, redesign, or a new version creates renewed pressure. - [Boundaries] Keep symbiogenesis contextual and evidence-driven rather than encoding percentages, modes, transition tables, runtime state, or sibling-symbiont churn. - [Composition] Preserve neutral work-surface declarations only while actionable feature work exists, guard the portable FSS protocol against named execution or continuation dependencies, and define deterministic project, local, portfolio, external, stale, and missing-surface behavior. - [CI] Validate tests, types, extension import, and package contents on pull requests and `main` pushes. - [Registry] Preserve the pre-1.0 package lineage while preparing the first public release under the `@llblab/pi-feature-symbiont` name. ## 0.1.0: Feature Symbiont Genesis - [Extension] Register the bundled FSS skill from source checkouts through the `resources_discover` lifecycle. - [Skills] Package FSS as an auto-activating project-local feature-symbiont generator and gardener. - [FSS] Allow a feature symbiont to own a co-located canonical `BACKLOG.md` only when no suitable project work surface exists. - [Composition] Define the neutral `Canonical open work: ` declaration so independent delivery protocols can discover feature work without understanding FSS. - [Lifecycle] Keep mutable work outside `SKILL.md`, preserve project truth ownership, and retire completed symbionts after reconciling durable evidence. - [Package] Ship the public package with an explicit MIT license and source-checkout registration metadata.