@mean-weasel/lineage 0.1.14 → 0.1.16

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 0.1.16
+
+- Add editable one- or two-word lineage edge summaries with agent/human provenance, optimistic concurrency protection, accessible keyboard editing, and consistent labels across every graph orientation.
+- Add a versioned generation-output manifest that binds each new output to its selected parent and required edge summary while preserving completion of already-planned legacy jobs.
+- Upgrade the node inspector with uncropped media, Branch, Re-roll, and Details actions, focus-scoped B/R/D shortcuts, and modal-safe dismissal in place of the redundant fixed Inspecting card.
+
+## 0.1.15
+
+- Add a subtle root marker that makes the starting point of each lineage tree immediately recognizable.
+- Add full-asset previews on node hover and keyboard focus while preserving double-click for full details and attempt history.
+- Add a browser-local setting to disable hover previews, plus refresh-state safeguards that keep dismissed previews closed during background updates.
+
 ## 0.1.14
 
 - Fix isolated channel installs against npm clients that return registry integrity as a flat `dist.integrity` field, while rejecting missing or conflicting identity metadata.

package/README.md

@@ -19,7 +19,7 @@ lineage-channel install preview
 
 By default the installer writes immutable version/integrity roots beneath
 `~/Library/Application Support/Lineage/runtimes`, plus channel-qualified
-launchers in its `bin` directory. Every launcher is pinned to an absolute
+launchers under `~/.local/bin`. Every launcher is pinned to an absolute
 package root and install receipt; it does not select code from `PATH` at runtime.
 
 The three exact channel meanings are:
@@ -131,6 +131,30 @@ matching legacy identity, but refuses a conflicting identity. An unprofiled
 CLI or service is `legacy-unbound` and read-only; mutating CLI commands and HTTP
 methods fail with a profile-required error instead of creating a database.
 
+Checkout fingerprints intentionally change as tracked or untracked source
+changes. To repin an existing development profile, first stop its managed
+service, then run the guarded checkout-only workflow:
+
+```bash
+make repin-dev LINEAGE_DEV_PROFILE=team-development
+```
+
+The underlying explicit command is:
+
+```bash
+npm run lineage:dev -- profile repin-runtime \
+  --profile team-development --checkout-root "$PWD" --confirm-write --json
+```
+
+Repin accepts only a verified dev checkout whose canonical root equals
+`--checkout-root`, an owner-only development manifest already pinned to
+dev/checkout, and an available profile writer lease. It atomically replaces
+only `expected_runtime`; profile/database identity, paths, environment,
+service origin, and migrations stay unchanged. Production, preview, package,
+wrong-root, unsafe-manifest, unconfirmed, and active-service cases fail closed.
+The command may prepare a new structurally valid development manifest before
+its database and asset root are cloned.
+
 To create a realistic preview or development database without copying a live
 SQLite file directly, define a new non-production target profile whose database
 does not exist, then run:
@@ -263,12 +287,33 @@ Keep the claim fresh and pass it to mutating commands:
 
 ```bash
 lineage agent heartbeat --claim-token "$LINEAGE_CLAIM_TOKEN" --json
-lineage link-child --project demo-project --root <root-asset-id> --child <child-asset-id> --claim-token "$LINEAGE_CLAIM_TOKEN" --confirm-write --json
+lineage link-child --project demo-project --root <root-asset-id> --child <child-asset-id> --summary "Cleaner type" --claim-token "$LINEAGE_CLAIM_TOKEN" --confirm-write --json
 lineage agent release --claim-token "$LINEAGE_CLAIM_TOKEN" --json
 ```
 
 `lineage link-child` creates a new visible descendant in the lineage graph. Do
-not use it for re-rolls.
+not use it for re-rolls. The coordinating agent must supply `--summary` with a
+one- or two-word description of the change from parent to child.
+
+For a coordinated multi-output generation job, plan from the selected lineage
+bases, copy `job.handoff.output_manifest` from the JSON response into a manifest
+file, and fill every output's `file_path` and distinct one- or two-word
+`edge_summary` before import:
+
+```bash
+lineage generate image plan --project demo-project --prompt "Create two variations" --from-lineage-selection --count 2 --json
+lineage generate image inspect --project demo-project --job-id <job-id> --json
+lineage generate image import --project demo-project --job-id <job-id> --manifest .asset-scratch/generation-output-manifest.json --confirm-write --json
+```
+
+Newly planned selection jobs require the versioned manifest and reject mixed
+`--manifest`, `--files`, or `--parent-files` input. Jobs already planned with
+the legacy adapter may still finish with `--files` or `--parent-files`; those
+legacy child edges remain unlabeled. Manifest retries are idempotent only while
+the output mapping, original summary, and current agent provenance still match.
+Asset indexing precedes the receipt transaction, so a later transactional
+failure can leave an indexed asset even though outputs, edges, receipt, job
+status, and selection reset roll back together.
 
 For re-roll work, mark the target, have the agent plan/import one replacement
 attempt, and cancel only when the request should be abandoned:
@@ -321,8 +366,12 @@ npx @mean-weasel/lineage-plugin-installer install --channel latest
 
 The installer verifies the plugin artifact checksum and rejects plugin manifests
 whose version or `lineage.version` does not exactly match the resolved Lineage
-package version. The plugin artifact and installer package are released from
-this public repository.
+package version. It then creates a dedicated marketplace under the active
+`CODEX_HOME`, registers that marketplace with supported `codex plugin`
+commands, installs the plugin, and verifies that Codex reports the exact version
+as installed and enabled. Use `--target-dir <path>` for a files-only install or
+`--dry-run` for a non-mutating activation plan. The plugin artifact and installer
+package are released from this public repository.
 
 Every Lineage release preflights the current operator skill, packs and checksums
 the exact matching plugin, installs that artifact into a temporary Codex plugin
@@ -331,6 +380,12 @@ or dist-tag mutation is allowed. Release status reports the local version lock
 and GitHub assets. The installed skill requires isolated channel launchers,
 named profiles, managed service identity status, and profile-only writes.
 
+The checkout also exposes `.agents/plugins/marketplace.json`, which points only
+at the checkout plugin and marks it installed by default for new development
+tasks. That repo marketplace is separate from the installer-managed marketplace
+under `CODEX_HOME`; restart Codex and use a brand-new task when validating either
+activation path.
+
 ## Local Development
 
 ```bash