<feed xmlns='http://www.w3.org/2005/Atom'>
<title>claude-plugins-official.git/plugins/code-modernization/assets, branch bump/stackhawk-api</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: a rule is tested only if a test that ran backs it</title>
<updated>2026-09-25T18:28:44+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T18:28:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=d49ccb3844876e35262a32f145b7b717646da733'/>
<id>d49ccb3844876e35262a32f145b7b717646da733</id>
<content type='text'>
A rule named only by a skipped or pending test no longer counts as covered. It is listed as "named, not run" and fails the rules check. A test-only folder is listed as tooling and gets no verdict. The verify command tries malformed records only when the person asked for exact behavior, so a proof loop has an end. The report parses rule headings and fields in linear time, and the report and pane show the new status.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
A rule named only by a skipped or pending test no longer counts as covered. It is listed as "named, not run" and fails the rules check. A test-only folder is listed as tooling and gets no verdict. The verify command tries malformed records only when the person asked for exact behavior, so a proof loop has an end. The report parses rule headings and fields in linear time, and the report and pane show the new status.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: an uplift is not proven by a typed baseline or edited tests</title>
<updated>2026-09-25T04:18:46+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T04:18:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=f45794fa4831636e7ae55f8081769c8ebf3f58c6'/>
<id>f45794fa4831636e7ae55f8081769c8ebf3f58c6</id>
<content type='text'>
Three ways a same-technology uplift could come out PROVEN too easily:

- The baseline came from a table someone typed. It now counts as measured
  only when the script can read per-test results (JUnit or TRX XML, a runner
  log with a summary line, or per-test JSON) from analysis/&lt;system&gt;/baseline/
  or a "Recorded:" line of BASELINE.md; a counts-only file is ignored, two
  measured sources that disagree are a gap, and the typed table must match
  what was measured.
- Tests edited during the uplift passed unnoticed. The pack now compares the
  legacy and working-copy test files (by walking files only) and lists what
  was added, removed or changed; a removed file, more than a quarter of the
  files changed, or no legacy tests to compare with is a gap, and it says
  plainly that weakened assertions cannot be detected.
- A silent behavioral change with no test at its site. Each Behavioral-silent
  delta in the catalog must have a test file naming its site file, or the
  module is at most PARTLY PROVEN.

The report's Proof section shows the three new checks, and an uplift pack that
lacks any of them reads as PARTLY PROVEN. 214 script tests pass.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Three ways a same-technology uplift could come out PROVEN too easily:

- The baseline came from a table someone typed. It now counts as measured
  only when the script can read per-test results (JUnit or TRX XML, a runner
  log with a summary line, or per-test JSON) from analysis/&lt;system&gt;/baseline/
  or a "Recorded:" line of BASELINE.md; a counts-only file is ignored, two
  measured sources that disagree are a gap, and the typed table must match
  what was measured.
- Tests edited during the uplift passed unnoticed. The pack now compares the
  legacy and working-copy test files (by walking files only) and lists what
  was added, removed or changed; a removed file, more than a quarter of the
  files changed, or no legacy tests to compare with is a gap, and it says
  plainly that weakened assertions cannot be detected.
- A silent behavioral change with no test at its site. Each Behavioral-silent
  delta in the catalog must have a test file naming its site file, or the
  module is at most PARTLY PROVEN.

The report's Proof section shows the three new checks, and an uplift pack that
lacks any of them reads as PARTLY PROVEN. 214 script tests pass.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: screenshots for the README, and where a person decides</title>
<updated>2026-09-25T04:07:42+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T04:07:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=29c1c6a0d16453427b488e3eca1ad6e8beac0c10'/>
<id>29c1c6a0d16453427b488e3eca1ad6e8beac0c10</id>
<content type='text'>
Adds the pictures the README and the pane docs use: three of the report (the
at-a-glance view when the proof passes, the same view when an independent
check finds a difference the development cases missed, and the proof tab) and
ten of the live pane, drawn by the pane's own code from finished runs. The
report pictures come from real runs; the pane's fleet and x-ray views and its
GIF use scripted agent activity, and the review and sign-off pictures use
sample text, all said so in the pane's README.

The front door names every place a person decides and moves the security scan
first when the person asked for it, and status points a new user to the front
door instead of straight to preflight.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Adds the pictures the README and the pane docs use: three of the report (the
at-a-glance view when the proof passes, the same view when an independent
check finds a difference the development cases missed, and the proof tab) and
ten of the live pane, drawn by the pane's own code from finished runs. The
report pictures come from real runs; the pane's fleet and x-ray views and its
GIF use scripted agent activity, and the review and sign-off pictures use
sample text, all said so in the pane's README.

The front door names every place a person decides and moves the security scan
first when the person asked for it, and status points a new user to the front
door instead of straight to preflight.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: a next step on the report, and tables that keep words whole</title>
<updated>2026-09-25T04:03:17+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T04:03:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=d6af0c04d89ad7b0c75e21b8ae7f15585e805b08'/>
<id>d6af0c04d89ad7b0c75e21b8ae7f15585e805b08</id>
<content type='text'>
The report is the page people open first, but it never said what to do
next. It now shows one command with a copy button and a one-line reason,
decided from which artifacts exist (preflight through brief, a rule review
before the plan when rules look wrong, verify after a build, harden, then
status).

Short words and verdict pills no longer break inside narrow table cells
("sam" and "e", "Calculatio" and "n"): only paths and hashes break anywhere.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The report is the page people open first, but it never said what to do
next. It now shows one command with a copy button and a one-line reason,
decided from which artifacts exist (preflight through brief, a rule review
before the plan when rules look wrong, verify after a build, harden, then
status).

Short words and verdict pills no longer break inside narrow table cells
("sam" and "e", "Calculatio" and "n"): only paths and hashes break anywhere.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: an independent proof step with one verdict per module</title>
<updated>2026-09-25T04:01:25+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T04:01:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=2efd715aeb081a965df3b2c871706c3577210e98'/>
<id>2efd715aeb081a965df3b2c871706c3577210e98</id>
<content type='text'>
/code-modernization:modernize-verify re-checks a finished build instead of
trusting the notes it left behind, and a script (not the model) computes one
verdict per module: PROVEN, PARTLY PROVEN or NOT PROVEN, with the rules
written into the output.

The pack re-reads the tests' own result files or a saved runner log (counts
the command merely reported never count), traces every P0 business rule to a
test that names it, judges the old and new outputs again with compare.py,
then runs at least ten inputs that development did not use on both systems.
It requires a recorded canary that turned tests red, checks that the legacy
source was not touched (by file times: no process runs in the analyzed
tree), and lists every human criterion as waiting for a person. For an
uplift it diffs the fresh results against the recorded baseline. Verdicts
are never carried over from an earlier run.

The report gains a Proof section that recomputes each verdict from the same
checks, and a failed diagram no longer stops the ones after it from drawing.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
/code-modernization:modernize-verify re-checks a finished build instead of
trusting the notes it left behind, and a script (not the model) computes one
verdict per module: PROVEN, PARTLY PROVEN or NOT PROVEN, with the rules
written into the output.

The pack re-reads the tests' own result files or a saved runner log (counts
the command merely reported never count), traces every P0 business rule to a
test that names it, judges the old and new outputs again with compare.py,
then runs at least ten inputs that development did not use on both systems.
It requires a recorded canary that turned tests red, checks that the legacy
source was not touched (by file times: no process runs in the analyzed
tree), and lists every human criterion as waiting for a person. For an
uplift it diffs the fresh results against the recorded baseline. Verdicts
are never carried over from an earlier run.

The report gains a Proof section that recomputes each verdict from the same
checks, and a failed diagram no longer stops the ones after it from drawing.
</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: add topology viewer screenshot to README</title>
<updated>2026-06-09T15:48:04+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-06-08T23:58:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=0c40a74425e01954b8968531f4b5a66f923fcf62'/>
<id>0c40a74425e01954b8968531f4b5a66f923fcf62</id>
<content type='text'>
Rendered from AWS CardDemo (the public mainframe sample app) by running
/modernize-map end to end and capturing the resulting TOPOLOGY.html.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Rendered from AWS CardDemo (the public mainframe sample app) by running
/modernize-map end to end and capturing the resulting TOPOLOGY.html.
</pre>
</div>
</content>
</entry>
</feed>
