Implement qxctl lifecycle profiles and observation reports

README.md

@@ -37,7 +37,7 @@ The repository contains proposal-only Contract Quad seeds for `node-troll`, `bus
 
 ## Current Integration Boundary
 
-SSIAG submits only typed, security-relevant safe metadata to the STAV append authority and never writes ledger files. qxctl authenticates the exact configured SSIAG and STAV endpoints before application exchange and performs no canonical mutation. It implements exact user-default engine selection, durable reconciliation, SSIAG-authorized session operations, and explicit host-event session convergence. For SKVI, SCLV, SACV, SODV, and SSFV, qxctl validates an exact inactive-undocked installation before invoking its bounded local process. The coordinator implements report-only lifecycle planning over complete caller-supplied desired/observed evidence, but qxctl lifecycle grammar, desired-profile persistence, configured-root observation, lifecycle journaling/recovery, package installation/uninstall, activation, Maestro docking, desired-state apply, and canonical apply are not implemented. SSFV coverage is explicitly partial and does not claim every implemented capability has been cataloged. The macOS provider reports metadata only. SACV's canonical registry remains empty: no remote HTTP API, SDK, live playground, or published OpenAPI description is currently claimed. SODV release observation remains caller-supplied: the engine does not contact Git hosts or package providers.
+SSIAG submits only typed, security-relevant safe metadata to the STAV append authority and never writes ledger files. qxctl authenticates the exact configured SSIAG and STAV endpoints before application exchange and performs no canonical mutation. It implements exact user-default engine selection, durable reconciliation, SSIAG-authorized session operations, explicit host-event session convergence, protected per-TOPS lifecycle profiles, fixed-layout receipt observation, and fresh report-only lifecycle planning through the exact bound coordinator. For SKVI, SCLV, SACV, SODV, and SSFV, qxctl validates an exact inactive-undocked installation before invoking its bounded local process. Lifecycle boot journaling/recovery, package installation/uninstall, activation, Maestro docking, desired-state apply, and canonical apply are not implemented. SSFV coverage is explicitly partial and does not claim every implemented capability has been cataloged. The macOS provider reports metadata only. SACV's canonical registry remains empty: no remote HTTP API, SDK, live playground, or published OpenAPI description is currently claimed. SODV release observation remains caller-supplied: the engine does not contact Git hosts or package providers.
 
 ## Releases and Documentation
 

knowledge/INTENT.md

@@ -50,14 +50,14 @@ Module contracts (`MANIFEST.md`, etc.) are distinct domains. SKV maps them but d
 The checked-in `tools/symphony-validator/` implementation produces deterministic, read-only evidence. It currently checks required Knowledge Vector contract anchors, SKVI structure, SKVI coverage and paths, SCLV record shape and continuity, SACV registry structure, SODV local release-record relationships, and bounded repository doctrine. It does not create canonical truth, inspect external publication state, publish documentation, or remediate files.
 
 ### Relationship to qxctl
-qxctl is the Go administrative surface for the ratified vector-engine family. `qxctl knowledge ...` owns cross-vector engine binding, worktree reconciliation, authenticated-session administration and explicit host-event convergence, later desired-state lifecycle administration, proposal coordination, and later apply coordination. `qxctl skvi|sclv|sacv|sodv|ssfv ...` owns vector-specific grammar. The implemented user-scope `knowledge engines` surface binds exact inactive-undocked installations into one noncanonical default profile, `knowledge reconcile` administers durable noncanonical worktree contexts through the exact bound coordinator, and `knowledge session transition` composes freshly authorized status/recover/begin/checkpoint/close calls for stable login, refresh, and logout events. qxctl implements these contracts but does not own vector semantics or canonical knowledge truth.
+qxctl is the Go administrative surface for the ratified vector-engine family. `qxctl knowledge ...` owns cross-vector engine binding, worktree reconciliation, authenticated-session administration, explicit host-event convergence, desired-profile administration, fixed-layout lifecycle observation, report-only planning invocation, proposal coordination, and later apply coordination. `qxctl skvi|sclv|sacv|sodv|ssfv ...` owns vector-specific grammar. The implemented user-scope `knowledge engines` surface binds exact inactive-undocked installations into one noncanonical default profile, `knowledge reconcile` administers durable noncanonical worktree contexts through the exact bound coordinator, `knowledge session transition` composes freshly authorized calls for stable login/refresh/logout events, and `knowledge lifecycle` maintains protected per-TOPS profiles, inventories configured receipt roots, and requests fresh dynamic reports. qxctl implements these contracts but does not own vector semantics or canonical knowledge truth.
 
 ### Vector Engine Foundation
 Each active application-level vector may have an independently installable, out-of-process C++ engine. Shared authority-free C++ mechanics may live under `libraries/`; a separate C++ coordinator owns authenticated-session and worktree-reconciliation mechanics. Engines inspect, validate, project, and propose within vector-owned contracts. They do not acquire authority merely by generating content.
 
-The implemented `0.1.0-dev` foundation and coordinator slice provides strict local process framing, read-only inspect/snapshot checking, explicit compatibility negotiation, durable user-scope worktree reconciliation, SSIAG-authorized noncanonical authority epochs, and deterministic report-only lifecycle planning over fully supplied desired/observed evidence. Independent C++ slices implement SKVI inspect/check/propose/project, SCLV inspect/check/propose/recover/project with provider-neutral evidence adapters, SACV inspect/check/diff/propose/project with bounded OpenAPI 3.2.0 JSON validation, SODV inspect/check/verify/propose/recover/project, and SSFV inspect/check/diff/propose/graph with content-addressed semantic freshness. qxctl invokes each only from an exact inactive-undocked installation and may record one exact version per role in its protected user-default binding profile. SSFV's three-record partial bootstrap demonstrates root and distributed feature ownership without asserting complete coverage. Binding, reconciliation, authenticated-session coordination, or a lifecycle plan does not alter an install receipt, dock with Maestro, invoke vector semantics, or mutate canonical knowledge.
+The implemented `0.1.0-dev` foundation and coordinator slice provides strict local process framing, read-only inspect/snapshot checking, explicit compatibility negotiation, durable user-scope worktree reconciliation, SSIAG-authorized noncanonical authority epochs, and deterministic report-only lifecycle planning over fully supplied desired/observed evidence. Independent C++ slices implement SKVI inspect/check/propose/project, SCLV inspect/check/propose/recover/project with provider-neutral evidence adapters, SACV inspect/check/diff/propose/project with bounded OpenAPI 3.2.0 JSON validation, SODV inspect/check/verify/propose/recover/project, and SSFV inspect/check/diff/propose/graph with content-addressed semantic freshness. qxctl invokes each only from an exact inactive-undocked installation, may record one exact version per role in its protected user-default binding profile, and now supplies the lifecycle coordinator with freshly observed content-addressed receipt evidence from administrator-selected roots. SSFV's three-record partial bootstrap demonstrates root and distributed feature ownership without asserting complete coverage. Binding, reconciliation, authenticated-session coordination, profile persistence, observation, or a lifecycle plan does not alter an install receipt, dock with Maestro, invoke vector semantics, or mutate canonical knowledge.
 
-The common lifecycle schema family now defines desired, observed, report-only plan commands, dependency-driven plans, applied state, durable boot transactions, and immutable receipt-v2 truth. The coordinator dynamically recomputes component action order from explicit readiness in either supported migration direction, while authorization, compare-and-swap, integrity, verification, and audit boundaries remain fixed. Desired-profile persistence, configured-root observation, lifecycle journaling/recovery, qxctl administration, and application remain future implementation gates.
+The common lifecycle schema family now defines declarative profile input, protected profiles, desired and observed evidence, report-only plan commands, dependency-driven plans, applied state, durable boot transactions, and immutable receipt-v2 truth. qxctl implements the profile, observation, authorization, and report-administration boundary. The coordinator dynamically recomputes component action order from explicit readiness in either supported migration direction, while authorization, compare-and-swap, integrity, verification, and audit boundaries remain fixed. Lifecycle boot journaling/recovery and action application remain future implementation gates.
 
 Initial vector-engine releases are read/query/validate/propose only. Programmatic canonical apply remains disabled until its SSIAG permission verification, expected-state transaction, qxctl safeguard, STAV event, recovery, and negative-test contracts are implemented and verified. `knowledge/SPEC.md` owns the common boundary; each vector Contract Quad owns its domain operations.
 
@@ -91,4 +91,4 @@ SODV governs publication truth.
 Published documentation is a derived public projection.
 
 ### Non-authorization Statement
-This canonical surface recognizes SACV and SSFV governance and the common lifecycle contract family but authorizes no endpoint, lifecycle mutation runtime, or additional feature record by itself. It authorizes the bounded vector-engine architecture, the implemented read-only/proposal development slices, the report-only coordinator planner, the ratified three-record SSFV partial bootstrap, derived projections, and qxctl grammar defined by `knowledge/MANIFEST.md` and `knowledge/SPEC.md`. It does not authorize lifecycle observation/persistence/apply, canonical apply, an additional SSFV feature record, a repository-completeness claim, a network API, Mintlify configuration, NotebookLM automation, general publication pipeline, database authority, direct STAV mutation, hot/warm-path participation, or any capability outside a vector's own Contract Quad.
+This canonical surface recognizes SACV and SSFV governance and the common lifecycle contract family but authorizes no endpoint, lifecycle action execution, or additional feature record by itself. It authorizes the bounded vector-engine architecture, the implemented read-only/proposal development slices, protected lifecycle profile/observation/report administration, the report-only coordinator planner, the ratified three-record SSFV partial bootstrap, derived projections, and qxctl grammar defined by `knowledge/MANIFEST.md` and `knowledge/SPEC.md`. It does not authorize lifecycle boot journaling or apply, canonical apply, an additional SSFV feature record, a repository-completeness claim, a network API, Mintlify configuration, NotebookLM automation, general publication pipeline, database authority, direct STAV mutation, hot/warm-path participation, or any capability outside a vector's own Contract Quad.