TML-2748: migration status overlays applied and pending on the shared migration tree

[wmadden-electric]

At a-glance

Connected database with one migration still to run:

$ prisma-next migration status --no-color
app:
○   3b2d98d                      (contract) (main)
│↑  20260305_add_avatar    73e3abe → 3b2d98d   ⧗ pending
○   73e3abe                      (db)
│✓  20260303_add_phone     ef9de27 → 73e3abe   ✓ applied
○   ef9de27
│✓  20260301_init          ∅ → ef9de27         ✓ applied
○   ∅

1 pending — run `prisma-next migrate --to 3b2d98d`

Hypothetical origin (--from drops applied glyphs and the (db) marker; pending is still the shortest path from that origin to the target):

$ prisma-next migration status --no-color --from ef9de27 --to 3b2d98d
app:
○   3b2d98d                      (contract) (main)
│↑  20260305_add_avatar    73e3abe → 3b2d98d   ⧗ pending
○   73e3abe
│↑  20260303_add_phone     ef9de27 → 73e3abe   ⧗ pending
○   ef9de27
│↑  20260301_init          ∅ → ef9de27
○   ∅

2 pending — run `prisma-next migrate --to 3b2d98d`

(Representative output — same tree renderer and overlay rules exercised in CLI unit tests and integration journeys.)

The decision

migration status now overlays applied and pending state on the shared migration graph tree, giving you one picture of every on-disk migration's relationship to the database. Applied means a ledger row exists for that migration hash (green ✓). Pending means the edge sits on the shortest path from the DB marker (or --from origin) to the app contract and is not yet applied (yellow ⧗). Everything else stays plain — the full on-disk graph, not a pruned subgraph. The old summary-only view and the dagre renderer are deleted; migration graph defaults to this tree (the experimental --tree flag is gone).

How we got here

One tree renderer for the read family

migration graph already renders contract topology as a condensed annotated tree (buildMigrationGraphRows → buildMigrationGraphLayout → renderMigrationGraphTree). list and status are meant to draw that same map with different overlays — package facts vs DB state — not maintain parallel layout code.

status used to look different

Previously, migration status fed a dagre layout and a compact summary that did not match graph or list. Applied edges were inferred from a graph walk from ∅ to the marker instead of the ledger, which could disagree with what actually ran.

Overlay on the shared renderer

Status computation builds edgeAnnotationsByHash (applied / pending) and passes them into the same tree renderer graph uses. The (db) marker reuses the existing dbHash node overlay. Multi-space projects get one tree section per space (with a spaceId: heading when there is more than one), matching list / graph.

--from for hypotheticals

--from <hash> overrides the path origin so you can ask offline: "what if my DB were at this contract?" Applied overlays are suppressed (they only make sense against the real DB); pending still follows the shortest path from the hypothetical origin to the target (--to or the app contract).

Dagre removed; tree is the default

With status on the shared tree, dagre had no remaining consumer. migration graph always renders the tree; --ascii, --legend, --dot, and --json remain. @dagrejs/dagre and its mapper/types/tests are removed.

What this PR does not change

• --json wire shape — still mirrors migration list plus per-migration status, with markerHash / targetHash per space (documented in the slice spec).
• migration list — separate slice (#706); this PR only shares the renderer hook list will populate later.
• migration log — separate slice (#704); flat ledger history, not tree-shaped.

Linked issue

Refs TML-2748 (resolves applied-from-ledger TML-2130).

Testing performed

• pnpm --filter @prisma-next/cli build
• pnpm --filter @prisma-next/cli typecheck
• pnpm --filter @prisma-next/cli test (status overlay, graph default-tree, dagre removal)
• rg 'dagre|graphRenderer|migrationGraphToRenderInput' packages/1-framework/3-tooling/cli/ → empty
• pnpm lint:deps

Checklist

• All commits are signed off (git commit -s)
• I read CONTRIBUTING.md and the change is scoped to one logical concern
• Tests are updated
• PR title is TML-2748: …
• n/a — internal CLI surface; skill update not required for this slice

Alternatives considered

• Keep dagre as a --graph alternative renderer — rejected. Two renderers split the family visually; dagre never matched the tree's information density for branching histories.
• Three states (applied / pending / unreachable) — rejected. Two states cover every real workflow; unreachable edges stay plain on the full list.
• Reimplement layout inside status — rejected. Share graph / list layout via the existing engine and differ only in overlays.

Summary by CodeRabbit

• New Features

  • Added applied/pending status indicators to migration visualizations.

• Bug Fixes

  • Improved migration status output with per-space reporting and clearer status summaries.

• Chores

  • Removed unused dependency.
  • Simplified migration graph rendering pipeline.
  • Removed --tree CLI option; graph now renders in optimized format by default.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: 463bf11b-401f-4754-a279-162ad5878a5c

📥 Commits

Reviewing files that changed from the base of the PR and between 4379813 and 0facf95.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (5)

• packages/1-framework/3-tooling/cli/src/commands/migration-list.ts
• packages/1-framework/3-tooling/cli/src/commands/migration-status.ts
• packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-tree-render.ts
• packages/1-framework/3-tooling/cli/test/utils/formatters/migration-graph-tree-render.test.ts
• packages/1-framework/3-tooling/prisma-next/package.json

💤 Files with no reviewable changes (1)

• packages/1-framework/3-tooling/prisma-next/package.json

🚧 Files skipped from review as they are similar to previous changes (4)

• packages/1-framework/3-tooling/cli/src/commands/migration-list.ts
• packages/1-framework/3-tooling/cli/test/utils/formatters/migration-graph-tree-render.test.ts
• packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-tree-render.ts
• packages/1-framework/3-tooling/cli/src/commands/migration-status.ts

---

📝 Walkthrough

Walkthrough

This PR removes the DAGRE flat-graph renderer, makes migration graph CLI commands render trees only, introduces per-edge applied/pending annotations derived from ledger and marker data, and updates command output types, tests, and e2e helpers to the new per-space JSON shape.

Changes

Per-Space Migration Status with Tree Rendering

Layer / File(s)	Summary
Migration status edge-annotation layer packages/1-framework/3-tooling/cli/src/commands/migration-status-overlay.ts, packages/1-framework/3-tooling/cli/test/commands/migration-status-overlay.test.ts	Adds deriveStatusEdgeAnnotations, appliedHashesFromLedger, and statusForMigrationHash to compute per-edge applied/pending annotations from ledger/marker data.
Migration status command per-space refactor packages/1-framework/3-tooling/cli/src/commands/migration-status.ts, packages/1-framework/3-tooling/cli/test/commands/format-status-summary.test.ts, packages/1-framework/3-tooling/cli/test/commands/migration-invariants.test.ts, packages/1-framework/3-tooling/cli/test/output.json-shapes.test.ts	Rewrites migration status to operate per contract-space: load aggregate, resolve per-space target, optionally read DB markers/ledgers, derive edge annotations, render per-space tree sections, compute pending totals and summary, and emit simplified JSON (ok, spaces, summary, diagnostics, optional missingInvariantsLine).
Tree rendering with status annotations packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-tree-render.ts, packages/1-framework/3-tooling/cli/test/utils/formatters/migration-graph-tree-render.test.ts	Adds MigrationEdgeAnnotation and edgeAnnotationsByHash option; appends colored ✓ applied / ⧗ pending (or ASCII) suffixes to edge output and updates legend snapshots and tests.
Graph command and list utility updates packages/1-framework/3-tooling/cli/src/commands/migration-graph.ts, packages/1-framework/3-tooling/cli/src/commands/migration-list.ts, packages/1-framework/3-tooling/cli/test/commands/migration-graph.test.ts	Removes --tree option and legacy flat-graph rendering imports/branch; migration-graph now always renders trees. Exports listRefsByContractHash. Legend-rendering tests adjusted to check new markers.
Renderer & types removal packages/1-framework/3-tooling/cli/src/utils/formatters/graph-render.ts, packages/1-framework/3-tooling/cli/src/utils/formatters/graph-types.ts, packages/1-framework/3-tooling/cli/src/utils/formatters/graph-migration-mapper.ts	Deletes DAGRE-based renderer, related graph types and mapper; removes their exports and associated tests.
Dependency cleanup and test configuration packages/1-framework/3-tooling/cli/package.json, packages/1-framework/3-tooling/prisma-next/package.json, packages/1-framework/3-tooling/cli/vitest.config.ts	Removes @dagrejs/dagre from package dependencies and updates Vitest coverage exclusions to reflect deleted formatter modules.
Tests, mocks, and e2e helper updates packages/1-framework/3-tooling/cli/test/commands/*, test/integration/test/cli-journeys/*.e2e.test.ts, test/integration/test/utils/journey-test-helpers.ts	Expands family/driver mocks for marker/ledger reads, removes old graph-renderer tests, adds overlay unit tests, and updates many e2e tests to use parseMigrationStatusJson and migrationStatusAppSpace for the new per-space status JSON shape.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Possibly related PRs

• prisma/prisma-next#706: Overlaps on adding/using edgeAnnotationsByHash for tree-edge annotations.
• prisma/prisma-next#258: Related to the DAGRE-based graph-rendering infrastructure that this PR removes.
• prisma/prisma-next#674: Overlaps on migration-graph CLI legend/tree rendering changes.

Suggested reviewers

• wmadden

"🐰
I hopped through trees now simple and neat,
Applied in green, pending in gold,
Ledger paths traced every migration's beat,
Tests updated, old maps turned cold—
A carrot snack for the new status fold."

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 12.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title accurately describes the main change: adding migration status overlays (applied/pending) to the shared migration tree rendering, which is the primary objective of this substantial refactoring.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch tml-2748-migration-status-tree-overlay

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[pkg-pr-new]

Open in StackBlitz

@prisma-next/extension-author-tools

npm i https://pkg.pr.new/@prisma-next/extension-author-tools@705

@prisma-next/mongo-runtime

npm i https://pkg.pr.new/@prisma-next/mongo-runtime@705

@prisma-next/family-mongo

npm i https://pkg.pr.new/@prisma-next/family-mongo@705

@prisma-next/sql-runtime

npm i https://pkg.pr.new/@prisma-next/sql-runtime@705

@prisma-next/family-sql

npm i https://pkg.pr.new/@prisma-next/family-sql@705

@prisma-next/extension-arktype-json

npm i https://pkg.pr.new/@prisma-next/extension-arktype-json@705

@prisma-next/middleware-cache

npm i https://pkg.pr.new/@prisma-next/middleware-cache@705

@prisma-next/mongo

npm i https://pkg.pr.new/@prisma-next/mongo@705

@prisma-next/extension-paradedb

npm i https://pkg.pr.new/@prisma-next/extension-paradedb@705

@prisma-next/extension-pgvector

npm i https://pkg.pr.new/@prisma-next/extension-pgvector@705

@prisma-next/extension-postgis

npm i https://pkg.pr.new/@prisma-next/extension-postgis@705

@prisma-next/postgres

npm i https://pkg.pr.new/@prisma-next/postgres@705

@prisma-next/sql-orm-client

npm i https://pkg.pr.new/@prisma-next/sql-orm-client@705

@prisma-next/sqlite

npm i https://pkg.pr.new/@prisma-next/sqlite@705

@prisma-next/target-mongo

npm i https://pkg.pr.new/@prisma-next/target-mongo@705

@prisma-next/adapter-mongo

npm i https://pkg.pr.new/@prisma-next/adapter-mongo@705

@prisma-next/driver-mongo

npm i https://pkg.pr.new/@prisma-next/driver-mongo@705

@prisma-next/contract

npm i https://pkg.pr.new/@prisma-next/contract@705

@prisma-next/utils

npm i https://pkg.pr.new/@prisma-next/utils@705

@prisma-next/config

npm i https://pkg.pr.new/@prisma-next/config@705

@prisma-next/errors

npm i https://pkg.pr.new/@prisma-next/errors@705

@prisma-next/framework-components

npm i https://pkg.pr.new/@prisma-next/framework-components@705

@prisma-next/operations

npm i https://pkg.pr.new/@prisma-next/operations@705

@prisma-next/ts-render

npm i https://pkg.pr.new/@prisma-next/ts-render@705

@prisma-next/contract-authoring

npm i https://pkg.pr.new/@prisma-next/contract-authoring@705

@prisma-next/ids

npm i https://pkg.pr.new/@prisma-next/ids@705

@prisma-next/psl-parser

npm i https://pkg.pr.new/@prisma-next/psl-parser@705

@prisma-next/psl-printer

npm i https://pkg.pr.new/@prisma-next/psl-printer@705

@prisma-next/cli

npm i https://pkg.pr.new/@prisma-next/cli@705

@prisma-next/cli-telemetry

npm i https://pkg.pr.new/@prisma-next/cli-telemetry@705

@prisma-next/emitter

npm i https://pkg.pr.new/@prisma-next/emitter@705

@prisma-next/migration-tools

npm i https://pkg.pr.new/@prisma-next/migration-tools@705

prisma-next

npm i https://pkg.pr.new/prisma-next@705

@prisma-next/vite-plugin-contract-emit

npm i https://pkg.pr.new/@prisma-next/vite-plugin-contract-emit@705

@prisma-next/mongo-codec

npm i https://pkg.pr.new/@prisma-next/mongo-codec@705

@prisma-next/mongo-contract

npm i https://pkg.pr.new/@prisma-next/mongo-contract@705

@prisma-next/mongo-value

npm i https://pkg.pr.new/@prisma-next/mongo-value@705

@prisma-next/mongo-contract-psl

npm i https://pkg.pr.new/@prisma-next/mongo-contract-psl@705

@prisma-next/mongo-contract-ts

npm i https://pkg.pr.new/@prisma-next/mongo-contract-ts@705

@prisma-next/mongo-emitter

npm i https://pkg.pr.new/@prisma-next/mongo-emitter@705

@prisma-next/mongo-schema-ir

npm i https://pkg.pr.new/@prisma-next/mongo-schema-ir@705

@prisma-next/mongo-query-ast

npm i https://pkg.pr.new/@prisma-next/mongo-query-ast@705

@prisma-next/mongo-orm

npm i https://pkg.pr.new/@prisma-next/mongo-orm@705

@prisma-next/mongo-query-builder

npm i https://pkg.pr.new/@prisma-next/mongo-query-builder@705

@prisma-next/mongo-lowering

npm i https://pkg.pr.new/@prisma-next/mongo-lowering@705

@prisma-next/mongo-wire

npm i https://pkg.pr.new/@prisma-next/mongo-wire@705

@prisma-next/sql-contract

npm i https://pkg.pr.new/@prisma-next/sql-contract@705

@prisma-next/sql-errors

npm i https://pkg.pr.new/@prisma-next/sql-errors@705

@prisma-next/sql-operations

npm i https://pkg.pr.new/@prisma-next/sql-operations@705

@prisma-next/sql-schema-ir

npm i https://pkg.pr.new/@prisma-next/sql-schema-ir@705

@prisma-next/sql-contract-psl

npm i https://pkg.pr.new/@prisma-next/sql-contract-psl@705

@prisma-next/sql-contract-ts

npm i https://pkg.pr.new/@prisma-next/sql-contract-ts@705

@prisma-next/sql-contract-emitter

npm i https://pkg.pr.new/@prisma-next/sql-contract-emitter@705

@prisma-next/sql-lane-query-builder

npm i https://pkg.pr.new/@prisma-next/sql-lane-query-builder@705

@prisma-next/sql-relational-core

npm i https://pkg.pr.new/@prisma-next/sql-relational-core@705

@prisma-next/sql-builder

npm i https://pkg.pr.new/@prisma-next/sql-builder@705

@prisma-next/target-postgres

npm i https://pkg.pr.new/@prisma-next/target-postgres@705

@prisma-next/target-sqlite

npm i https://pkg.pr.new/@prisma-next/target-sqlite@705

@prisma-next/adapter-postgres

npm i https://pkg.pr.new/@prisma-next/adapter-postgres@705

@prisma-next/adapter-sqlite

npm i https://pkg.pr.new/@prisma-next/adapter-sqlite@705

@prisma-next/driver-postgres

npm i https://pkg.pr.new/@prisma-next/driver-postgres@705

@prisma-next/driver-sqlite

npm i https://pkg.pr.new/@prisma-next/driver-sqlite@705

commit: 0facf95

[github-actions]

size-limit report 📦

Path	Size
postgres / no-emit	137.37 KB (0%)
postgres / emit	108.83 KB (0%)
mongo / no-emit	75.85 KB (0%)
mongo / emit	70.78 KB (0%)
cf-worker / no-emit	166.35 KB (0%)
cf-worker / emit	134.51 KB (0%)

[coderabbitai]

Actionable comments posted: 3

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-tree-render.ts (1)

781-790: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Legend status colors should respect opts.colorize
renderMigrationGraphLegend uses colorette’s top-level green/yellow helpers for the ✓/⧗ status line, which follow colorette’s ambient color detection instead of opts.colorize, so ANSI can appear even with --no-color.

Suggested fix

 export function renderMigrationGraphLegend(opts: RenderMigrationGraphLegendOptions): string {
   const palette = paletteFor(opts.glyphMode ?? 'unicode');
   const style = createAnsiMigrationListStyler({ useColor: opts.colorize });
+  const statusColors = createColors({ useColor: opts.colorize });
   const node = palette.node.trimEnd();
   const sampleArrow = `${style.sourceHash('aaaaaa')} ${style.glyph(palette.forwardArrow)} ${style.destHash('bbbbbb')}`;
   return [
     'Legend:',
     `  ${style.kind(node)} contract   ${style.kind(palette.edgeArrow.forward)} forward   ${style.kind(palette.edgeArrow.rollback)} rollback`,
     `  ${style.kind(palette.edgeArrow.self)} migration without schema change`,
-    `  ${green('✓')} applied   ${yellow('⧗')} pending`,
+    `  ${statusColors.green('✓')} applied   ${statusColors.yellow('⧗')} pending`,
     `  ${style.glyph(palette.emptySource)} empty database (baseline)`,
     `  ${style.refs(['refs'])} ${DB_MARKER_NAME} / ${CONTRACT_MARKER_NAME} markers`,
     `  ${sampleArrow}   migration from contract aaaaaa to bbbbbb`,
   ].join('\n');
 }

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-tree-render.ts`
around lines 781 - 790, renderMigrationGraphLegend currently uses colorette's
top-level green/yellow which ignore opts.colorize; change the status symbols to
use the ANSI styler created by createAnsiMigrationListStyler so they respect
opts.colorize — replace green('✓') and yellow('⧗') with the styler methods (e.g.
style.success('✓') and style.pending('⧗') or add equivalent methods to the
styler) so the check and pending glyphs are colored only when opts.colorize is
true.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@packages/1-framework/3-tooling/cli/src/commands/migration-status.ts`:
- Around line 444-465: The code is overwriting headlineTargetHash for every
space in scopedSpaces so the final suggested "migrate --to" hint points to the
last space rather than the app-level target; change the assignment in the loop
(where aggregate.space(...), member.graph(), resolveTargetHashForSpace(...) are
used) to only set headlineTargetHash if it is not already set (i.e. set it once
when headlineTargetHash is undefined) so the footer remains pinned to the
first/app target; apply the same guard to the other occurrence around the
resolveTargetHashForSpace block at lines ~566-573.
- Around line 452-463: In the targetHash === undefined branch inside
migration-status.ts, you currently push a MIGRATION.DIVERGED diagnostic and
continue, but you must also mark that this space is not up-to-date so the footer
doesn't report success; after pushing the diagnostic (in the same block where
targetHash is undefined) increment the shared totalPending counter (or set the
per-space pending flag that contributes to totalPending) so the overall summary
reflects unresolved targets; apply the same change to the analogous branch
around the later block (lines ~565-593) where a non-unique target is detected.

In
`@packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-tree-render.ts`:
- Around line 527-543: formatEdgeStatusSuffix currently hardcodes Unicode glyphs
(✓ / ⧗); change it to honor the CLI ascii flag on the options object (e.g.
opts.ascii or similar) by selecting ASCII alternatives when that flag is true:
read the overlay annotation via opts.edgeAnnotationsByHash.get(migrationHash) as
now, then compute glyph = status === 'applied' ? (opts.ascii ? 'v' : '✓') :
(opts.ascii ? '>' : '⧗'); keep the existing colorization code (styler =
green/yellow and opts.colorize) and return the same padded string but using the
chosen glyph so both migration graph and migration status respect --ascii.

---

Outside diff comments:
In
`@packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-tree-render.ts`:
- Around line 781-790: renderMigrationGraphLegend currently uses colorette's
top-level green/yellow which ignore opts.colorize; change the status symbols to
use the ANSI styler created by createAnsiMigrationListStyler so they respect
opts.colorize — replace green('✓') and yellow('⧗') with the styler methods (e.g.
style.success('✓') and style.pending('⧗') or add equivalent methods to the
styler) so the check and pending glyphs are colored only when opts.colorize is
true.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: 0ce66516-0943-411c-a219-d56524147fc6

📥 Commits

Reviewing files that changed from the base of the PR and between 27d8631 and 4379813.

⛔ Files ignored due to path filters (2)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
• projects/migration-graph-rendering/slices/status-db-overlay/spec.md is excluded by !projects/**

📒 Files selected for processing (35)

• packages/1-framework/3-tooling/cli/package.json
• packages/1-framework/3-tooling/cli/src/commands/migration-graph.ts
• packages/1-framework/3-tooling/cli/src/commands/migration-list.ts
• packages/1-framework/3-tooling/cli/src/commands/migration-status-overlay.ts
• packages/1-framework/3-tooling/cli/src/commands/migration-status.ts
• packages/1-framework/3-tooling/cli/src/utils/formatters/graph-migration-mapper.ts
• packages/1-framework/3-tooling/cli/src/utils/formatters/graph-render.ts
• packages/1-framework/3-tooling/cli/src/utils/formatters/graph-types.ts
• packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-tree-render.ts
• packages/1-framework/3-tooling/cli/test/commands/cross-consumer-integrity.test.ts
• packages/1-framework/3-tooling/cli/test/commands/derive-edge-statuses.test.ts
• packages/1-framework/3-tooling/cli/test/commands/format-status-summary.test.ts
• packages/1-framework/3-tooling/cli/test/commands/migration-graph.test.ts
• packages/1-framework/3-tooling/cli/test/commands/migration-invariants.test.ts
• packages/1-framework/3-tooling/cli/test/commands/migration-status-aggregate-spaces.test.ts
• packages/1-framework/3-tooling/cli/test/commands/migration-status-overlay.test.ts
• packages/1-framework/3-tooling/cli/test/commands/migration-tamper.test.ts
• packages/1-framework/3-tooling/cli/test/output.json-shapes.test.ts
• packages/1-framework/3-tooling/cli/test/utils/formatters/graph-migration-mapper.test.ts
• packages/1-framework/3-tooling/cli/test/utils/formatters/graph-render.test.ts
• packages/1-framework/3-tooling/cli/test/utils/formatters/migration-graph-tree-render.test.ts
• packages/1-framework/3-tooling/cli/test/utils/formatters/test-graphs.ts
• packages/1-framework/3-tooling/cli/vitest.config.ts
• test/integration/test/cli-journeys/adopt-migrations.e2e.test.ts
• test/integration/test/cli-journeys/diamond-convergence.e2e.test.ts
• test/integration/test/cli-journeys/divergence-and-refs.e2e.test.ts
• test/integration/test/cli-journeys/drift-deleted-root.e2e.test.ts
• test/integration/test/cli-journeys/interleaved-db-update.e2e.test.ts
• test/integration/test/cli-journeys/invariant-routing.e2e.test.ts
• test/integration/test/cli-journeys/invariant-routing.mongo.e2e.test.ts
• test/integration/test/cli-journeys/migration-status-diagnostics.e2e.test.ts
• test/integration/test/cli-journeys/plan-to-rollback.e2e.test.ts
• test/integration/test/cli-journeys/ref-routing.e2e.test.ts
• test/integration/test/cli-journeys/schema-evolution-migrations.e2e.test.ts
• test/integration/test/utils/journey-test-helpers.ts

💤 Files with no reviewable changes (10)

• packages/1-framework/3-tooling/cli/test/commands/derive-edge-statuses.test.ts
• packages/1-framework/3-tooling/cli/test/utils/formatters/graph-render.test.ts
• packages/1-framework/3-tooling/cli/src/utils/formatters/graph-types.ts
• packages/1-framework/3-tooling/cli/package.json
• packages/1-framework/3-tooling/cli/test/commands/migration-status-aggregate-spaces.test.ts
• packages/1-framework/3-tooling/cli/src/utils/formatters/graph-migration-mapper.ts
• packages/1-framework/3-tooling/cli/vitest.config.ts
• packages/1-framework/3-tooling/cli/src/utils/formatters/graph-render.ts
• packages/1-framework/3-tooling/cli/test/utils/formatters/graph-migration-mapper.test.ts
• packages/1-framework/3-tooling/cli/test/utils/formatters/test-graphs.ts