Extract merge/recompute specs into ADRs and knowledge docs

Merged
GM
4mo ago
+393-3

Why

The three merge/recompute specs are complete, but their durable decisions lived
only inside the spec directories. This runs the spec extraction: it lifts the
decisions into ADRs and knowledge docs so they outlive the specs, then archives
the specs.

Specs extracted:

  • ifc-2761-coalesce-merge-recompute
  • ifc-2761-merge-recompute-profile
  • ifc-2804-selective-recompute

What changed

Documentation only, no code changes.

  • Add ADRs 0011-0014:
    • 0011 node-mutation origin label that suppresses the coalesced families'
      per-node triggers on merge/rebase.
    • 0012 coalesced deduplicated recompute pass on merge and rebase, replacing
      the per-node fan-out.
    • 0013 static kind-scoped lifecycle triggers for Python-transform recompute.
    • 0014 transform lifecycle flow owns node-input automation reconciliation
      (delete does real teardown).
  • Knowledge docs: add the display-label / HFID derivers to
    merge-recompute.md Key Files, and document the event and workflow test
    adapters (MemoryInfrahubEvent, WorkflowRecorder) in testing.md.
  • Archive the three specs under dev/specs/archive/, mark each spec.md as
    Extracted, and add an EXTRACTED.md record per spec.
  • Update the dev/README.md and dev/adr/README.md indexes.

Every extracted claim was checked against the current tree (deriver modules,
test adapters, the origin enum, and NodeMutatedEvent.get_messages()), so the
docs describe what exists, not the specs' original plans.

How to review

  1. Read the four new ADRs in dev/adr/.
  2. Skim the two knowledge diffs: dev/knowledge/backend/merge-recompute.md and
    dev/knowledge/backend/testing.md.
  3. The rest of the diff is a pure git mv of the spec directories into
    archive/ (no content change) plus the two index updates.

How to test

Docs only, nothing to run. The markdown lint job targets docs/docs/**, not
dev/, so these files are not gated by it.

Impact & rollout

  • Backward compatibility: no code, schema, or API changes.
  • Deployment notes: safe, documentation only.
  • No changelog fragment: internal dev/ docs only, no user-facing change.