<feed xmlns='http://www.w3.org/2005/Atom'>
<title>claude-plugins-official.git/plugins/code-modernization/commands/modernize-map.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: rate rules by what the system is for, and make live runs finish</title>
<updated>2026-09-25T03:15:45+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T03:15:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=696904602b2bdf3e0ddd07ae1221f9eb3e3b8e62'/>
<id>696904602b2bdf3e0ddd07ae1221f9eb3e3b8e62</id>
<content type='text'>
Two problems from running the commands on real repositories:

- The P0 definition was money- and regulation-shaped, so a music-library
  tool got no P0 rules and its behavior contract came out empty. P0 now
  means the system's core purpose depends on the rule, or a wrong result is
  costly or irreversible (money, legal, data integrity, security or safety,
  or the central calculation or decision the system exists to perform).
- Citations came back as lists of ranges, and the rule renderer numbered
  RULE-NNN in a different order from the document. Each rule now cites one
  range and the numbers read in sequence.

Commands that start subagents now say to run them in the foreground and
wait, because a headless session ends when the model stops talking even if
it said it was waiting for a background agent.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Two problems from running the commands on real repositories:

- The P0 definition was money- and regulation-shaped, so a music-library
  tool got no P0 rules and its behavior contract came out empty. P0 now
  means the system's core purpose depends on the rule, or a wrong result is
  costly or irreversible (money, legal, data integrity, security or safety,
  or the central calculation or decision the system exists to perform).
- Citations came back as lists of ranges, and the rule renderer numbered
  RULE-NNN in a different order from the document. Each rule now cites one
  range and the numbers read in sequence.

Commands that start subagents now say to run them in the foreground and
wait, because a headless session ends when the model stops talking even if
it said it was waiting for a background agent.
</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: describe each node on the topology map</title>
<updated>2026-09-25T00:49:55+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-24T02:03:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=2ce9d0dace1239bec65379ecd3834258574c9073'/>
<id>2ce9d0dace1239bec65379ecd3834258574c9073</id>
<content type='text'>
After topology.json is built, map now writes one paragraph (55 to 90
words) per node into a description field: what the node does in
business terms, then what it calls, reads, writes or is called by.
Each writer gets only that node's source excerpt, header comment and
connections from the map, is told every name and number must come from
that data, and says so in one sentence when the data is thin. The
session checks the paragraphs against those packets before merging
them, and writers never write files. Writers run in parallel batches of
about 8, and --no-describe skips the step.

The viewer's sidebar shows the description under the size and language
line with a muted caption, inserted as text rather than markup because
it is derived from analyzed source. Nodes without a description, and
topology.json files written before this change, render exactly as
before.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
After topology.json is built, map now writes one paragraph (55 to 90
words) per node into a description field: what the node does in
business terms, then what it calls, reads, writes or is called by.
Each writer gets only that node's source excerpt, header comment and
connections from the map, is told every name and number must come from
that data, and says so in one sentence when the data is thin. The
session checks the paragraphs against those packets before merging
them, and writers never write files. Writers run in parallel batches of
about 8, and --no-describe skips the step.

The viewer's sidebar shows the description under the size and language
line with a muted caption, inserted as text rather than markup because
it is derived from analyzed source. Nodes without a description, and
topology.json files written before this change, render exactly as
before.
</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: fix findings from adversarial audit</title>
<updated>2026-06-09T23:31:52+00:00</updated>
<author>
<name>Morgan Westlee Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-06-09T23:31:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=3b9df6160068f836214bfae942a2ca2530489c84'/>
<id>3b9df6160068f836214bfae942a2ca2530489c84</id>
<content type='text'>
Code/security:
- extract-rules.js: guard null agent() verdicts in the verify + P0 loops
  (a skipped/dead referee made {rule,v:null} survive .filter(Boolean) and
  then crashed on v.injectionSuspected / v.every) — sibling scripts already
  had the guard.
- topology viewer XSS: the map injector embedded untrusted JSON (node names
  from filenames, etc.) into a &lt;script&gt; island unescaped — a name containing
  &lt;/script&gt; executed on open. Escape &lt; &gt; &amp; in the injected data and add a CSP
  to the template.
- Second-order injection: citation/identifier fields (source / cwe /
  source_site / correctedSource) were interpolated UNFENCED into the verifier
  prompts that are supposed to be the trust anchor. Fence them in
  extract-rules, harden-scan, uplift-deltas.

uplift design (audit of the new feature):
- Working-copy model: copy the WHOLE solution to modernized/ once and edit in
  place (relative project refs survive; result is a reviewable git diff) —
  the incremental per-project copy broke multi-project builds.
- Dual-run honesty: reframed as 'if both runtimes run here' (net48 needs
  Windows; JUnit/pytest don't multi-target); dummy-test gate now binds a real
  SUT under both targets; per-stack harness notes.
- Tooling honesty: present/runnable/actually-ran distinction; never fold in a
  tool that couldn't run; apiport/2to3 demoted; py2-&gt;3 removed from 'preserve'
  examples.
- Delta classes: name the high-blast-radius landmines (JPMS strong
  encapsulation, .NET trimming/AOT, ICU globalization, hosting/runtime-config,
  analyzer/nullable) in the finder briefs + agent.
- Rewrite-vs-uplift signal: weigh by touched sites (siteCount), not delta-card
  count; judgment-share demoted to secondary.

Docs/consistency: brief reads topology.json (not TOPOLOGY.html); README
'five commands'; credential-masking claim split (analysts mask+cite vs
code-writers substitute fakes); read-only/write-scope claims softened to
match enforcement (Bash retained -&gt; discipline, not tool-lock); reimagine
nested blockers/pendingRuleIds; status splits transform vs reimagine markers;
portfolio enumeration basenames; plugin.json description updated.

Co-Authored-By: Claude Fable 5 &lt;noreply@anthropic.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Code/security:
- extract-rules.js: guard null agent() verdicts in the verify + P0 loops
  (a skipped/dead referee made {rule,v:null} survive .filter(Boolean) and
  then crashed on v.injectionSuspected / v.every) — sibling scripts already
  had the guard.
- topology viewer XSS: the map injector embedded untrusted JSON (node names
  from filenames, etc.) into a &lt;script&gt; island unescaped — a name containing
  &lt;/script&gt; executed on open. Escape &lt; &gt; &amp; in the injected data and add a CSP
  to the template.
- Second-order injection: citation/identifier fields (source / cwe /
  source_site / correctedSource) were interpolated UNFENCED into the verifier
  prompts that are supposed to be the trust anchor. Fence them in
  extract-rules, harden-scan, uplift-deltas.

uplift design (audit of the new feature):
- Working-copy model: copy the WHOLE solution to modernized/ once and edit in
  place (relative project refs survive; result is a reviewable git diff) —
  the incremental per-project copy broke multi-project builds.
- Dual-run honesty: reframed as 'if both runtimes run here' (net48 needs
  Windows; JUnit/pytest don't multi-target); dummy-test gate now binds a real
  SUT under both targets; per-stack harness notes.
- Tooling honesty: present/runnable/actually-ran distinction; never fold in a
  tool that couldn't run; apiport/2to3 demoted; py2-&gt;3 removed from 'preserve'
  examples.
- Delta classes: name the high-blast-radius landmines (JPMS strong
  encapsulation, .NET trimming/AOT, ICU globalization, hosting/runtime-config,
  analyzer/nullable) in the finder briefs + agent.
- Rewrite-vs-uplift signal: weigh by touched sites (siteCount), not delta-card
  count; judgment-share demoted to secondary.

Docs/consistency: brief reads topology.json (not TOPOLOGY.html); README
'five commands'; credential-masking claim split (analysts mask+cite vs
code-writers substitute fakes); read-only/write-scope claims softened to
match enforcement (Bash retained -&gt; discipline, not tool-lock); reimagine
nested blockers/pendingRuleIds; status splits transform vs reimagine markers;
portfolio enumeration basenames; plugin.json description updated.

Co-Authored-By: Claude Fable 5 &lt;noreply@anthropic.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: vendor d3, viewer robustness, status command, pipeline fixes</title>
<updated>2026-06-09T15:48:04+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-06-08T22:36:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=bec8d7c93ae523e1cb3204eb061c801eaff017e5'/>
<id>bec8d7c93ae523e1cb3204eb061c801eaff017e5</id>
<content type='text'>
Viewer (assets/topology-viewer.html):
- inline a minified d3 subset (hierarchy/pack, zoom, selection,
  interpolateZoom, ease; ISC license) instead of loading from a CDN —
  the page is now fully self-contained and works on air-gapped networks
- handle duplicate node ids (unique-suffix; edges bind to the first
  occurrence) and store parent references directly, fixing
  level-of-detail and selection corruption with messy generated data
- share one reveal rule between drawing, edge culling, and hit-testing
  so edges no longer draw into collapsed containers
- pre-bucket edges by kind and keep a per-node adjacency map; the
  hover/selection pass no longer scans every edge each frame
- cancel in-flight fly-to animations when a new one starts; clamp
  fly-to zoom to the zoom extent; derive max zoom from the smallest
  leaf so deep estates stay reachable
- render dead-end candidates (new deadEnds field) with a dashed
  outline and a sidebar badge
- clicking a node during a flow walkthrough exits the walkthrough;
  search results clear on selection and Escape; surrogate-safe label
  truncation; clearer stats line; explicit empty-topology message

Commands:
- new /modernize-status: read-only progress report — artifact inventory
  with timestamps, staleness flags, secrets-hygiene checks, next step
- map: deadEnds in the topology schema; datastore names must be logical
  identifiers with credentials stripped from URLs/DSNs
- brief: read topology.json + .mmd files (not the interactive HTML);
  staleness check against inputs; effort unit aligned to person-months
- transform: secret-safe characterization-test prompt; diff -y fallback
  when delta is missing; credential-safe diff selection
- reimagine: target vision is everything after the first argument (was
  silently truncated to one word); masking rules in spec/scaffold/
  handoff prompts
- brief/transform/reimagine: human-approval gates phrased as explicit
  stop-and-wait instead of 'enter plan mode'
- preflight: delta in the tool table; brief added to the verdict list
- README: preflight/status in the workflow; legacy/ deny list also
  covers Write; plugin + marketplace descriptions updated
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Viewer (assets/topology-viewer.html):
- inline a minified d3 subset (hierarchy/pack, zoom, selection,
  interpolateZoom, ease; ISC license) instead of loading from a CDN —
  the page is now fully self-contained and works on air-gapped networks
- handle duplicate node ids (unique-suffix; edges bind to the first
  occurrence) and store parent references directly, fixing
  level-of-detail and selection corruption with messy generated data
- share one reveal rule between drawing, edge culling, and hit-testing
  so edges no longer draw into collapsed containers
- pre-bucket edges by kind and keep a per-node adjacency map; the
  hover/selection pass no longer scans every edge each frame
- cancel in-flight fly-to animations when a new one starts; clamp
  fly-to zoom to the zoom extent; derive max zoom from the smallest
  leaf so deep estates stay reachable
- render dead-end candidates (new deadEnds field) with a dashed
  outline and a sidebar badge
- clicking a node during a flow walkthrough exits the walkthrough;
  search results clear on selection and Escape; surrogate-safe label
  truncation; clearer stats line; explicit empty-topology message

Commands:
- new /modernize-status: read-only progress report — artifact inventory
  with timestamps, staleness flags, secrets-hygiene checks, next step
- map: deadEnds in the topology schema; datastore names must be logical
  identifiers with credentials stripped from URLs/DSNs
- brief: read topology.json + .mmd files (not the interactive HTML);
  staleness check against inputs; effort unit aligned to person-months
- transform: secret-safe characterization-test prompt; diff -y fallback
  when delta is missing; credential-safe diff selection
- reimagine: target vision is everything after the first argument (was
  silently truncated to one word); masking rules in spec/scaffold/
  handoff prompts
- brief/transform/reimagine: human-approval gates phrased as explicit
  stop-and-wait instead of 'enter plan mode'
- preflight: delta in the tool table; brief added to the verdict list
- README: preflight/status in the workflow; legacy/ deny list also
  covers Write; plugin + marketplace descriptions updated
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: harden topology viewer and template injection</title>
<updated>2026-06-09T15:48:04+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-06-08T22:03:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=874596818685794ad06efcf5db115acaf938da68'/>
<id>874596818685794ad06efcf5db115acaf938da68</id>
<content type='text'>
Fixes from an adversarial review of the new viewer:

- pin d3 to 7.9.0 and load it via dynamic import with an explicit
  error panel when the CDN is unreachable (previously a blocked CDN
  produced a silent dark page — a real concern for restricted networks)
- coerce ids/names/loc at intake: a single missing name or non-numeric
  loc previously threw inside the render loop or propagated NaN through
  the pack layout, blanking the canvas with no error
- normalize flows/steps/edges defensively (null entries, missing steps,
  numeric ids vs string lookups)
- mirror the level-of-detail reveal rule in the hit test so clicks
  can't select nodes that aren't drawn
- scope the Escape shortcut so clearing the search box doesn't reset
  the viewport; set zoom clickDistance(4) so trackpad jitter doesn't
  swallow selection clicks
- round canvas backing-store size (fractional devicePixelRatio caused
  a reallocation every frame on 125%/150% display scaling)
- modernize-map: use braced ${CLAUDE_PLUGIN_ROOT} so substitution
  actually happens, assert the injection marker exists in the template,
  and correct the documented failure mode
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Fixes from an adversarial review of the new viewer:

- pin d3 to 7.9.0 and load it via dynamic import with an explicit
  error panel when the CDN is unreachable (previously a blocked CDN
  produced a silent dark page — a real concern for restricted networks)
- coerce ids/names/loc at intake: a single missing name or non-numeric
  loc previously threw inside the render loop or propagated NaN through
  the pack layout, blanking the canvas with no error
- normalize flows/steps/edges defensively (null entries, missing steps,
  numeric ids vs string lookups)
- mirror the level-of-detail reveal rule in the hit test so clicks
  can't select nodes that aren't drawn
- scope the Escape shortcut so clearing the search box doesn't reset
  the viewport; set zoom clickDistance(4) so trackpad jitter doesn't
  swallow selection clicks
- round canvas backing-store size (fractional devicePixelRatio caused
  a reallocation every frame on 125%/150% display scaling)
- modernize-map: use braced ${CLAUDE_PLUGIN_ROOT} so substitution
  actually happens, assert the injection marker exists in the template,
  and correct the documented failure mode
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: interactive topology map, preflight command, persona flows</title>
<updated>2026-06-09T15:48:04+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-06-08T21:54:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=1c4a5cfded2cb2e4c8c5420ebd2f3974eb3fdd51'/>
<id>1c4a5cfded2cb2e4c8c5420ebd2f3974eb3fdd51</id>
<content type='text'>
modernize-map previously rendered the call graph and data lineage as
static Mermaid diagrams, which become unreadable once a node has ~10+
edges — exactly the shape of real legacy systems. It now builds an
interactive viewer from a shipped template (assets/topology-viewer.html):
a zoomable circle-pack of domains/modules sized by LOC, rendered to
canvas with level-of-detail reveal, dependency edges with per-kind
toggles, search with fly-to, a per-node detail sidebar, and a flow
walkthrough mode. Small domain-level .mmd exports remain for docs.

- topology.json now has a documented schema (hierarchy + edges + entry
  points + observations + flows) consumed by the viewer
- map traces 2-4 business flows anchored to personas (claimant,
  operator, auditor), each step in plain business language mapped to
  the modules that implement it; the viewer plays them as numbered
  paths
- brief gains a Business Walkthroughs section connecting each persona
  flow to the phase that replaces it
- new modernize-preflight command: detects the stack, checks analysis
  tooling, smoke-compiles a real source file with the legacy toolchain,
  inventories missing copybooks/descriptors/binary-only artifacts, and
  writes a per-command readiness verdict
- transform now verifies legacy + target toolchains before its plan
  gate instead of failing at test time
- README: commands updated, optional-tooling section reframed as 'what
  to give Claude'
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
modernize-map previously rendered the call graph and data lineage as
static Mermaid diagrams, which become unreadable once a node has ~10+
edges — exactly the shape of real legacy systems. It now builds an
interactive viewer from a shipped template (assets/topology-viewer.html):
a zoomable circle-pack of domains/modules sized by LOC, rendered to
canvas with level-of-detail reveal, dependency edges with per-kind
toggles, search with fly-to, a per-node detail sidebar, and a flow
walkthrough mode. Small domain-level .mmd exports remain for docs.

- topology.json now has a documented schema (hierarchy + edges + entry
  points + observations + flows) consumed by the viewer
- map traces 2-4 business flows anchored to personas (claimant,
  operator, auditor), each step in plain business language mapped to
  the modules that implement it; the viewer plays them as numbered
  paths
- brief gains a Business Walkthroughs section connecting each persona
  flow to the phase that replaces it
- new modernize-preflight command: detects the stack, checks analysis
  tooling, smoke-compiles a real source file with the legacy toolchain,
  inventories missing copybooks/descriptors/binary-only artifacts, and
  writes a per-command readiness verdict
- transform now verifies legacy + target toolchains before its plan
  gate instead of failing at test time
- README: commands updated, optional-tooling section reframed as 'what
  to give Claude'
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: harden writes a patch instead of editing legacy; make map/security guidance language-agnostic</title>
<updated>2026-05-11T23:46:03+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-05-11T23:46:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=5e4a45001d608ce34437181d96340faa1f5899c9'/>
<id>5e4a45001d608ce34437181d96340faa1f5899c9</id>
<content type='text'>
- modernize-harden: never edits legacy/ anymore. Writes findings plus a
  reviewed unified diff to analysis/&lt;system&gt;/security_remediation.patch.
  A second security-auditor pass reviews each hunk (RESOLVES / PARTIAL /
  INTRODUCES-RISK) before presenting. The user reviews and applies the
  patch deliberately, then re-runs to verify. This makes every command
  consistent with the recommended deny Edit(legacy/**) workspace setting,
  so the README's exception note is gone.
- modernize-map: restructure the parse-target list around three stack-
  agnostic principles (dispatcher targets are variables; code-storage
  joins live in config; entry points live in deployment descriptors), with
  COBOL/Java/web/CLI examples on equal footing rather than COBOL-dominant.
  Same protections against false dead-code findings, less stack-specific.
- security-auditor agent: rephrase coverage items in stack-neutral terms
  (record layouts/temp datasets, resource ACLs, deployment scripts/job
  definitions, batch input records) so the checklist reads naturally for
  COBOL, Java EE, .NET, and web targets alike.
- README: drop the harden exception note; describe the patch workflow.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
- modernize-harden: never edits legacy/ anymore. Writes findings plus a
  reviewed unified diff to analysis/&lt;system&gt;/security_remediation.patch.
  A second security-auditor pass reviews each hunk (RESOLVES / PARTIAL /
  INTRODUCES-RISK) before presenting. The user reviews and applies the
  patch deliberately, then re-runs to verify. This makes every command
  consistent with the recommended deny Edit(legacy/**) workspace setting,
  so the README's exception note is gone.
- modernize-map: restructure the parse-target list around three stack-
  agnostic principles (dispatcher targets are variables; code-storage
  joins live in config; entry points live in deployment descriptors), with
  COBOL/Java/web/CLI examples on equal footing rather than COBOL-dominant.
  Same protections against false dead-code findings, less stack-specific.
- security-auditor agent: rephrase coverage items in stack-neutral terms
  (record layouts/temp datasets, resource ACLs, deployment scripts/job
  definitions, batch input records) so the checklist reads naturally for
  COBOL, Java EE, .NET, and web targets alike.
- README: drop the harden exception note; describe the patch workflow.
</pre>
</div>
</content>
</entry>
</feed>
