@mean-weasel/lineage 0.1.15 → 0.1.16

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # 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.

package/README.md

@@ -287,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: