<feed xmlns='http://www.w3.org/2005/Atom'>
<title>claude-plugins-official.git/plugins/code-modernization/commands/modernize-preflight.md, branch bump/cloud-sql-sqlserver</title>
<subtitle>Official Claude Code plugin directory
</subtitle>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/'/>
<entry>
<title>code-modernization: people's verdicts on rules reach the build, and safer baselines</title>
<updated>2026-09-25T04:01:36+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T04:01:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=0c186cf8c54bdf925cb2572e871ec16d04aa8425'/>
<id>0c186cf8c54bdf925cb2572e871ec16d04aa8425</id>
<content type='text'>
A reviewer's "this rule is wrong" never reached the plan or the rewrite: the
pane wrote a review ledger that no command read, and without the pane there
was no way to write one. /code-modernization:modernize-review asks about the
rules that need judgement (P0 rules with a defect, an SME question or less
than High confidence) in a pop-up, or takes verdicts typed in the request,
and writes the same RULE_REVIEWS.json/.md with an optional note. brief,
transform, reimagine and the test engineer read it: a rule marked wrong is
not an oracle and a P0 rule under discussion blocks.

Running the old system to record a baseline is now limited to the local
machine or a test environment the person named; production or third-party
services, new accounts and real data are off limits unless the approved plan
names them, a token in a recorded response is replaced before anything is
saved, and every command stops the servers it started.

Also: the front door asks in two pop-ups within the four-option limit, every
command points a missing-code user to /modernize &lt;name&gt; --source &lt;path&gt;, the
status inventory and next-step order include review and verify, the
assessment says what Rehost and Replace mean, preflight notes the Windows
python name, and the plugin and marketplace descriptions match what it does.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
A reviewer's "this rule is wrong" never reached the plan or the rewrite: the
pane wrote a review ledger that no command read, and without the pane there
was no way to write one. /code-modernization:modernize-review asks about the
rules that need judgement (P0 rules with a defect, an SME question or less
than High confidence) in a pop-up, or takes verdicts typed in the request,
and writes the same RULE_REVIEWS.json/.md with an optional note. brief,
transform, reimagine and the test engineer read it: a rule marked wrong is
not an oracle and a P0 rule under discussion blocks.

Running the old system to record a baseline is now limited to the local
machine or a test environment the person named; production or third-party
services, new accounts and real data are off limits unless the approved plan
names them, a token in a recorded response is replaced before anything is
saved, and every command stops the servers it started.

Also: the front door asks in two pop-ups within the four-option limit, every
command points a missing-code user to /modernize &lt;name&gt; --source &lt;path&gt;, the
status inventory and next-step order include review and verify, the
assessment says what Rehost and Replace mean, preflight notes the Windows
python name, and the plugin and marketplace descriptions match what it does.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: simpler commands, a source option, a report page and an equivalence check</title>
<updated>2026-09-25T03:14:51+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T03:14:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=cafefb304bde4070c6c0877528ee49c1252eff85'/>
<id>cafefb304bde4070c6c0877528ee49c1252eff85</id>
<content type='text'>
Commands hardcoded legacy/&lt;system&gt;, so code too big to copy, or living at
an absolute path, needed a hand-made symlink. Preflight now takes
--source &lt;path&gt; and makes the legacy/&lt;system&gt; link for you (a junction on
Windows); nothing is copied, and every command says where the link points
before it starts. The harden patch is applied with patch -p1 -d.

Each command ends by naming the next command to run, and the commands are
about a third shorter with no step removed:
- map accepts an existing dependency graph (--graph) or the stack's own
  tooling, maps very large estates in resumable chunks, records reflection
  targets as unresolved instead of dead, asks before describing more than
  40 nodes, and never gives two nodes the same location.
- transform can take its module and target from the brief, counts the
  equivalence cases that executed (zero is a failure and a comparison never
  skips), shows the tests can fail with a deliberate one-line break, and
  hands "same or different" to a script when both systems can run.
- brief writes each phase in one fixed shape: one command, module ids as in
  the map, and criteria written as conditions a build command may tick but
  not reword.
- reimagine reuses the discovery artifacts instead of extracting them again.
- status names the exact command to paste next.

scripts/build_report.py turns whatever the commands wrote into one
self-contained, offline REPORT.html (Mermaid is vendored, all text from the
analysis is escaped, the quarantined secrets file is never read), and
scripts/compare.py decides byte-for-byte whether two outputs match, records
why, and checks it can fail. The shard builder ignores symbolic links and
paths that leave the source, matches a plain name against what lies beneath
it, and falls back to the directory tree when the map's modules share a
location.

The README drops from 275 to about 100 lines; the pane's reference moves to
hooks/README.md.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Commands hardcoded legacy/&lt;system&gt;, so code too big to copy, or living at
an absolute path, needed a hand-made symlink. Preflight now takes
--source &lt;path&gt; and makes the legacy/&lt;system&gt; link for you (a junction on
Windows); nothing is copied, and every command says where the link points
before it starts. The harden patch is applied with patch -p1 -d.

Each command ends by naming the next command to run, and the commands are
about a third shorter with no step removed:
- map accepts an existing dependency graph (--graph) or the stack's own
  tooling, maps very large estates in resumable chunks, records reflection
  targets as unresolved instead of dead, asks before describing more than
  40 nodes, and never gives two nodes the same location.
- transform can take its module and target from the brief, counts the
  equivalence cases that executed (zero is a failure and a comparison never
  skips), shows the tests can fail with a deliberate one-line break, and
  hands "same or different" to a script when both systems can run.
- brief writes each phase in one fixed shape: one command, module ids as in
  the map, and criteria written as conditions a build command may tick but
  not reword.
- reimagine reuses the discovery artifacts instead of extracting them again.
- status names the exact command to paste next.

scripts/build_report.py turns whatever the commands wrote into one
self-contained, offline REPORT.html (Mermaid is vendored, all text from the
analysis is escaped, the quarantined secrets file is never read), and
scripts/compare.py decides byte-for-byte whether two outputs match, records
why, and checks it can fail. The shard builder ignores symbolic links and
paths that leave the source, matches a plain name against what lies beneath
it, and falls back to the directory tree when the map's modules share a
location.

The README drops from 275 to about 100 lines; the pane's reference moves to
hooks/README.md.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: fix contradictions and stale references in existing text</title>
<updated>2026-09-25T00:50:21+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-24T05:32:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=65b0f06f1bd6309b88ca8c3cc92e34d7a4f51f5f'/>
<id>65b0f06f1bd6309b88ca8c3cc92e34d7a4f51f5f</id>
<content type='text'>
Make the text say what the commands and workflows already do: where each build command writes, which commands need earlier output, the approval stop before an uplift fan-out, a version placeholder that named arguments left unusable, a reference to a README section that does not exist, and a few counts and step references. No new steps or options.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Make the text say what the commands and workflows already do: where each build command writes, which commands need earlier output, the approval stop before an uplift fan-out, a version placeholder that named arguments left unusable, a reference to a README section that does not exist, and a few counts and step references. No new steps or options.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: preflight checks that legacy/ is protected from edits</title>
<updated>2026-09-25T00:50:20+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-24T02:20:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=9b4e3c21f27766422e43259da71745b863684784'/>
<id>9b4e3c21f27766422e43259da71745b863684784</id>
<content type='text'>
The commands are written never to edit legacy/, but nothing checked
that anything enforced it. Preflight now has a Check 7 that reads,
without changing anything, the project's .claude/settings.json and
.claude/settings.local.json and the user's settings file, and looks for
an Edit deny rule that covers legacy/. The result is a row in
PREFLIGHT.md with the same status marks as the other checks: a green row
names the file and the rule, and a warning prints the settings snippet
to add. The check never edits a settings file and never suggests
loosening one.

The check also says plainly that a permission rule covers the file tools
and the shell commands the CLI recognizes, not a script that
opens the files itself, so a green row is not a guarantee. A read-only
mount, or a sandbox that blocks writes to legacy/, is. The README no
longer says the settings file enforces the invariant: the commands keep
to it by convention and the rule backs that up.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The commands are written never to edit legacy/, but nothing checked
that anything enforced it. Preflight now has a Check 7 that reads,
without changing anything, the project's .claude/settings.json and
.claude/settings.local.json and the user's settings file, and looks for
an Edit deny rule that covers legacy/. The result is a row in
PREFLIGHT.md with the same status marks as the other checks: a green row
names the file and the rule, and a warning prints the settings snippet
to add. The check never edits a settings file and never suggests
loosening one.

The check also says plainly that a permission rule covers the file tools
and the shell commands the CLI recognizes, not a script that
opens the files itself, so a green row is not a guarantee. A read-only
mount, or a sandbox that blocks writes to legacy/, is. The README no
longer says the settings file enforces the invariant: the commands keep
to it by convention and the rule backs that up.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: preflight asks its questions in a pop-up and proves the target stack</title>
<updated>2026-09-25T00:49:55+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-24T01:58:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=7c4583e465e15becca5568aeaa1c0c733e4dd88c'/>
<id>7c4583e465e15becca5568aeaa1c0c733e4dd88c</id>
<content type='text'>
The five Check 0 questions were left to the model to ask in chat, where
they were easy to skip, paraphrase or answer on the person's behalf.
They are now asked with AskUserQuestion, questions 1-4 in one call and
the fifth in a second, each with a "Don't know" option and room for free
text, and never in chat text. Checks that do not depend on the answers
may run while the pop-up is open, and a question that is never answered
still lands in the report as an open item. Every answer is recorded
verbatim in an Answers section of PREFLIGHT.md, which the brief reads.

The command declared a target_stack argument but never used it. Check 3b
now builds a throwaway project on the target stack (restore, build, one
passing test) so a target that installs but cannot build here is caught
before transform or uplift starts.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The five Check 0 questions were left to the model to ask in chat, where
they were easy to skip, paraphrase or answer on the person's behalf.
They are now asked with AskUserQuestion, questions 1-4 in one call and
the fifth in a second, each with a "Don't know" option and room for free
text, and never in chat text. Checks that do not depend on the answers
may run while the pop-up is open, and a question that is never answered
still lands in the report as an open item. Every answer is recorded
verbatim in an Answers section of PREFLIGHT.md, which the brief reads.

The command declared a target_stack argument but never used it. Check 3b
now builds a throwaway project on the target stack (restore, build, one
passing test) so a target that installs but cannot build here is caught
before transform or uplift starts.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: named arguments and namespaced command names</title>
<updated>2026-09-25T00:49:55+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-15T22:15:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=d4981e86b90f08a5aa029cb5cc1f274f6922cc17'/>
<id>d4981e86b90f08a5aa029cb5cc1f274f6922cc17</id>
<content type='text'>
Positional placeholders are zero-based ($0 is the first argument), but
every command used $1 for the first one, so arguments arrived shifted:
modernize-preflight carddemo java-spring analyzed legacy/java-spring.
Each command now declares its arguments in frontmatter (for example
`arguments: system module target_stack`) and uses the names. A missing
optional argument now expands to an empty string instead of a literal
placeholder.

Plugin commands resolve only by their namespaced name, so the README,
command cross-references, agents, workflow descriptions and the
topology viewer now say /code-modernization:modernize-*.

The extract-rules workflow is renamed modernize-extract-rules-mine. It
shared the command's name, so invoking the command could start the
workflow directly and skip the command's instructions. Commands launch
workflows by script path, so nothing else changes.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Positional placeholders are zero-based ($0 is the first argument), but
every command used $1 for the first one, so arguments arrived shifted:
modernize-preflight carddemo java-spring analyzed legacy/java-spring.
Each command now declares its arguments in frontmatter (for example
`arguments: system module target_stack`) and uses the names. A missing
optional argument now expands to an empty string instead of a literal
placeholder.

Plugin commands resolve only by their namespaced name, so the README,
command cross-references, agents, workflow descriptions and the
topology viewer now say /code-modernization:modernize-*.

The extract-rules workflow is renamed modernize-extract-rules-mine. It
shared the command's name, so invoking the command could start the
workflow directly and skip the command's instructions. Commands launch
workflows by script path, so nothing else changes.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: pilot-first uplift migration, brief-driven execution, deeper preflight</title>
<updated>2026-07-09T01:48:30+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-07-09T01:42:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=96e3e8c6af5f8a01f4d71be69201dfb7a2d5dfc1'/>
<id>96e3e8c6af5f8a01f4d71be69201dfb7a2d5dfc1</id>
<content type='text'>
/modernize-uplift migrates one representative project end-to-end and
writes its lessons to analysis/&lt;system&gt;/PLAYBOOK.md before touching the
rest. The remaining projects then fan out through a new uplift-migrate
workflow, one uplift-migrator agent per project, in dependency-aware
escalating batches behind a per-batch circuit breaker. A recorded
per-test baseline (analysis/&lt;system&gt;/BASELINE.md) gates the migration,
and the delta catalog reports a test framework whose runner does not
support the target as its own highest-blast-radius dependency.

The three execution commands (uplift, transform, reimagine) read
MODERNIZATION_BRIEF.md and treat their phase's scope and entry and exit
criteria as gates, so editing the brief steers execution. For a
same-stack uplift the brief requires the delta catalog and applies the
same ordering overrides the execution command does.

/modernize-preflight opens with a short interview (scope, local build
and test, bespoke build infrastructure, prior attempts, what is off
limits) without blocking on the answers, reads the CI/build definition
for how the system builds, escalates the smoke test to a whole-project
restore and build, and adds a scope-boundary check that enumerates
inbound and outbound dependencies when the system directory is a slice
of a larger repository.

Workflow scripts accept args delivered as either a JSON string or an
object.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
/modernize-uplift migrates one representative project end-to-end and
writes its lessons to analysis/&lt;system&gt;/PLAYBOOK.md before touching the
rest. The remaining projects then fan out through a new uplift-migrate
workflow, one uplift-migrator agent per project, in dependency-aware
escalating batches behind a per-batch circuit breaker. A recorded
per-test baseline (analysis/&lt;system&gt;/BASELINE.md) gates the migration,
and the delta catalog reports a test framework whose runner does not
support the target as its own highest-blast-radius dependency.

The three execution commands (uplift, transform, reimagine) read
MODERNIZATION_BRIEF.md and treat their phase's scope and entry and exit
criteria as gates, so editing the brief steers execution. For a
same-stack uplift the brief requires the delta catalog and applies the
same ordering overrides the execution command does.

/modernize-preflight opens with a short interview (scope, local build
and test, bespoke build infrastructure, prior attempts, what is off
limits) without blocking on the answers, reads the CI/build definition
for how the system builds, escalates the smoke test to a whole-project
restore and build, and adds a scope-boundary check that enumerates
inbound and outbound dependencies when the system directory is a slice
of a larger repository.

Workflow scripts accept args delivered as either a JSON string or an
object.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: add /modernize-uplift for same-stack version migrations</title>
<updated>2026-06-09T23:12:16+00:00</updated>
<author>
<name>Morgan Westlee Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-06-09T23:12:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=4a8250babf1d131c1406b113f3d759d18c55ec48'/>
<id>4a8250babf1d131c1406b113f3d759d18c55ec48</id>
<content type='text'>
Adds a third build method alongside transform (cross-stack rewrite) and
reimagine (greenfield): uplift, for same-stack version bumps (.NET Framework
4.8 -&gt; .NET 8, Spring Boot 2-&gt;3, Python 2-&gt;3) where the right move is to
PRESERVE the code and fix only the version deltas, not extract intent and
rewrite.

- commands/modernize-uplift.md: delta-catalog-driven, dual-target test harness
  (one suite on both runtimes; baseline-on-old is the oracle), leaf-first build
  graph ordering, minimal-diff discipline (architecture-critic flags gratuitous
  divergence), and a 'this is a rewrite, use transform' escape hatch.
- agents/version-delta-analyst.md: finds the source-&gt;target breaking changes
  that THIS code hits; drives the ecosystem migration tool (upgrade-assistant /
  OpenRewrite / pyupgrade / ng update) and owns the residue; read-only.
- workflows/uplift-deltas.js: parallel finder per delta category, each verified
  against the cited code so deltas that don't apply here are dropped.
- Wired into assess (recommended-pattern routing), brief (per-phase command +
  leaf-first ordering), preflight (dual-run + tool readiness), status, README.

Co-Authored-By: Claude Fable 5 &lt;noreply@anthropic.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Adds a third build method alongside transform (cross-stack rewrite) and
reimagine (greenfield): uplift, for same-stack version bumps (.NET Framework
4.8 -&gt; .NET 8, Spring Boot 2-&gt;3, Python 2-&gt;3) where the right move is to
PRESERVE the code and fix only the version deltas, not extract intent and
rewrite.

- commands/modernize-uplift.md: delta-catalog-driven, dual-target test harness
  (one suite on both runtimes; baseline-on-old is the oracle), leaf-first build
  graph ordering, minimal-diff discipline (architecture-critic flags gratuitous
  divergence), and a 'this is a rewrite, use transform' escape hatch.
- agents/version-delta-analyst.md: finds the source-&gt;target breaking changes
  that THIS code hits; drives the ecosystem migration tool (upgrade-assistant /
  OpenRewrite / pyupgrade / ng update) and owns the residue; read-only.
- workflows/uplift-deltas.js: parallel finder per delta category, each verified
  against the cited code so deltas that don't apply here are dropped.
- Wired into assess (recommended-pattern routing), brief (per-phase command +
  leaf-first ordering), preflight (dual-run + tool readiness), status, README.

Co-Authored-By: Claude Fable 5 &lt;noreply@anthropic.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: COCOMO is a complexity index, never a modernization timeline</title>
<updated>2026-06-09T21:21:50+00:00</updated>
<author>
<name>Morgan Westlee Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-06-09T21:21:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=e5939029ecdda7e9b8d30854e95eed2a5ff60062'/>
<id>e5939029ecdda7e9b8d30854e95eed2a5ff60062</id>
<content type='text'>
COCOMO's constants encode human-team productivity; presenting its
person-months as how long an agentic modernization will take (or cost) is
a claim we should not make. Reframe COCOMO everywhere as a RELATIVE
complexity/scale index for ranking and sequencing systems only:

- assess: capture COCOMO as a complexity index; explicitly ignore scc's
  'Estimated Schedule Effort' and cost-in-dollars; ASSESSMENT 'Effort
  Estimation' section becomes 'Relative Scale' with a not-a-timeline note;
  portfolio heat-map column renamed Complexity (COCOMO index).
- brief: phase plan uses relative T-shirt sizing, not person-months/weeks;
  phases render as a dependency flowchart, not a gantt (gantt = calendar).
- portfolio-assess.js: field cocomoPm -&gt; complexityIndex; return label
  carries the not-a-duration caveat.
- README: 'A note on COCOMO' explains the index framing and points at
  better intrinsic-complexity proxies.

Co-Authored-By: Claude Fable 5 &lt;noreply@anthropic.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
COCOMO's constants encode human-team productivity; presenting its
person-months as how long an agentic modernization will take (or cost) is
a claim we should not make. Reframe COCOMO everywhere as a RELATIVE
complexity/scale index for ranking and sequencing systems only:

- assess: capture COCOMO as a complexity index; explicitly ignore scc's
  'Estimated Schedule Effort' and cost-in-dollars; ASSESSMENT 'Effort
  Estimation' section becomes 'Relative Scale' with a not-a-timeline note;
  portfolio heat-map column renamed Complexity (COCOMO index).
- brief: phase plan uses relative T-shirt sizing, not person-months/weeks;
  phases render as a dependency flowchart, not a gantt (gantt = calendar).
- portfolio-assess.js: field cocomoPm -&gt; complexityIndex; return label
  carries the not-a-duration caveat.
- README: 'A note on COCOMO' explains the index framing and points at
  better intrinsic-complexity proxies.

Co-Authored-By: Claude Fable 5 &lt;noreply@anthropic.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: legacy toolchain is advisory, not a transform blocker</title>
<updated>2026-06-09T15:48:05+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-06-09T00:35:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=ecc5139c30dccfec6df8e9801f1ad101140213a4'/>
<id>ecc5139c30dccfec6df8e9801f1ad101140213a4</id>
<content type='text'>
Legacy code often cannot build locally by nature — CICS/IMS programs
have no local translator and the real runtime may be a mainframe the
user doesn't have. Stopping transform on a failed legacy smoke compile
would block exactly those systems.

- transform Step 0a: the target toolchain remains required (its tests
  cannot run without it); a failed or impossible legacy compile no
  longer stops the run — the equivalence strategy switches to recorded
  traces / golden-master fixtures, and that downgrade is stated in the
  plan and in TRANSFORMATION_NOTES.md so reviewers know the strength of
  the proof
- preflight: a red legacy toolchain now yields Ready-with-gaps for
  transform/reimagine instead of Not-ready
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Legacy code often cannot build locally by nature — CICS/IMS programs
have no local translator and the real runtime may be a mainframe the
user doesn't have. Stopping transform on a failed legacy smoke compile
would block exactly those systems.

- transform Step 0a: the target toolchain remains required (its tests
  cannot run without it); a failed or impossible legacy compile no
  longer stops the run — the equivalence strategy switches to recorded
  traces / golden-master fixtures, and that downgrade is stated in the
  plan and in TRANSFORMATION_NOTES.md so reviewers know the strength of
  the proof
- preflight: a red legacy toolchain now yields Ready-with-gaps for
  transform/reimagine instead of Not-ready
</pre>
</div>
</content>
</entry>
</feed>
