<feed xmlns='http://www.w3.org/2005/Atom'>
<title>claude-plugins-official.git/plugins/code-modernization/scripts/build_report.py, branch bump/snowflake-cortex-code</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: 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>
</feed>
