<feed xmlns='http://www.w3.org/2005/Atom'>
<title>claude-plugins-official.git/plugins/code-modernization/scripts/tests, branch bump/hyperframes</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: count failures and the machine's python, once per version</title>
<updated>2026-09-25T19:06:43+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T19:06:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=c8874f5ad883e26428f483ffa4d537cc81489e64'/>
<id>c8874f5ad883e26428f483ffa4d537cc81489e64</id>
<content type='text'>
Usage counts now say what the plugin runs on (system, python status and version, path problems) and which kind of failure happens: a missing or placeholder python, a permission block, a model error, or an error in the plugin's own script. Failures are classified on the machine into a fixed list and only the code is sent, once per kind per session. A session-start ping, once per plugin version, counts machines where nobody gets as far as typing a command. When python cannot run, the shell wrapper reports that itself, and on Windows it falls back to python or the py launcher.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Usage counts now say what the plugin runs on (system, python status and version, path problems) and which kind of failure happens: a missing or placeholder python, a permission block, a model error, or an error in the plugin's own script. Failures are classified on the machine into a fixed list and only the code is sent, once per kind per session. A session-start ping, once per plugin version, counts machines where nobody gets as far as typing a command. When python cannot run, the shell wrapper reports that itself, and on Windows it falls back to python or the py launcher.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: version 1.0.0, usage counts and a README results table</title>
<updated>2026-09-25T18:29:00+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T18:29:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=363af43603ecdb1bdbed7303764b6daeeec7c37f'/>
<id>363af43603ecdb1bdbed7303764b6daeeec7c37f</id>
<content type='text'>
The plugin now has a version and a changelog. Two hooks record whole-number usage counts (which command ran, how far a system got, how many rules and proofs) through the CLI's own telemetry: counts from 100 up are rounded, nothing is sent when the plugin is not in use, and any of three switches turns it off. The README documents every key and lists what the plugin was tried on, checked against the run files.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The plugin now has a version and a changelog. Two hooks record whole-number usage counts (which command ran, how far a system got, how many rules and proofs) through the CLI's own telemetry: counts from 100 up are rounded, nothing is sent when the plugin is not in use, and any of three switches turns it off. The README documents every key and lists what the plugin was tried on, checked against the run files.
</pre>
</div>
</content>
</entry>
<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: approve a difference once per input</title>
<updated>2026-09-25T04:27:42+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T04:27:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=d3a40f72165764888f9a57a3e93db86e88f8e063'/>
<id>d3a40f72165764888f9a57a3e93db86e88f8e063</id>
<content type='text'>
An independent check of a rewritten batch job found differences on two new
inputs of one family (a blank numeric field the rewrite rejects on purpose
and the old program reads as zero). Each input has several output files, so
accepting the deviation meant three or four hand-written entries per input.

A top-level "approvedInputs": {"F23": "reason"} in a cases file now approves
every case that shares that input label. A reason is still required (blank
approves nothing), a case's own reason wins, a missing file is never turned
into a pass, and the result still lists the difference as approved.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
An independent check of a rewritten batch job found differences on two new
inputs of one family (a blank numeric field the rewrite rejects on purpose
and the old program reads as zero). Each input has several output files, so
accepting the deviation meant three or four hand-written entries per input.

A top-level "approvedInputs": {"F23": "reason"} in a cases file now approves
every case that shares that input label. A reason is still required (blank
approves nothing), a case's own reason wins, a missing file is never turned
into a pass, and the result still lists the difference as approved.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: make rule consolidation auditable and injection-safe</title>
<updated>2026-09-25T04:22:06+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T04:22:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=ff833bd7231262a8521ab3728c5625dc6c4f4a1d'/>
<id>ff833bd7231262a8521ab3728c5625dc6c4f4a1d</id>
<content type='text'>
Follow-ups from review of the consolidation pass:

- The agent is a restricted type with the same read-only wording as its
  siblings, and every field on its numbered list is a single bounded line, so
  a rule name containing a newline cannot fake another entry.
- A group with any number out of range or not an integer is rejected whole
  instead of being coerced into a different merge.
- A merge keeps the most conservative review state: the highest priority, the
  lowest confidence, and every suspected defect and SME question of the folded
  rules.
- Every folded rule is returned with the rule it went into, and the rules
  document lists them under "Rules folded into another", so nothing disappears
  untraceably. Extra citations show as "Also cited" without the joining word.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Follow-ups from review of the consolidation pass:

- The agent is a restricted type with the same read-only wording as its
  siblings, and every field on its numbered list is a single bounded line, so
  a rule name containing a newline cannot fake another entry.
- A group with any number out of range or not an integer is rejected whole
  instead of being coerced into a different merge.
- A merge keeps the most conservative review state: the highest priority, the
  lowest confidence, and every suspected defect and SME question of the folded
  rules.
- Every folded rule is returned with the rule it went into, and the rules
  document lists them under "Rules folded into another", so nothing disappears
  untraceably. Extra citations show as "Also cited" without the joining word.
</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: harden the numeric tolerance and say what Rehost and Replace mean</title>
<updated>2026-09-25T03:34:21+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T03:34:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=5b8ec4b30f45b5e8b4c8a6efd63719730cf1a5ad'/>
<id>5b8ec4b30f45b5e8b4c8a6efd63719730cf1a5ad</id>
<content type='text'>
Follow-ups from review of the tolerance check: an absolute tolerance above
1e-6 is refused like a relative one above 1%, numbers are compared as exact
decimals rather than doubles, dotted runs such as 1.2.3 or 10.0.0.1 are text
that must match exactly, and the self-check now changes the leading digit of
every sampled number to prove the tolerance cannot hide a real change.

The business-rules header says how many rules there were at extraction, since
later steps add rules. The assessment says what to do when it recommends
Rehost or Replace, which change no code and so have no build command.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Follow-ups from review of the tolerance check: an absolute tolerance above
1e-6 is refused like a relative one above 1%, numbers are compared as exact
decimals rather than doubles, dotted runs such as 1.2.3 or 10.0.0.1 are text
that must match exactly, and the self-check now changes the leading digit of
every sampled number to prove the tolerance cannot hide a real change.

The business-rules header says how many rules there were at extraction, since
later steps add rules. The assessment says what to do when it recommends
Rehost or Replace, which change no code and so have no build command.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: compare floating-point output within a declared tolerance</title>
<updated>2026-09-25T03:31:54+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T03:31:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=4672eac1e36ff37394189376217bdc6f2b2e2e4a'/>
<id>4672eac1e36ff37394189376217bdc6f2b2e2e4a</id>
<content type='text'>
The equivalence check compared bytes only, which cannot pass for numeric
code (Fortran, C, scientific and financial results) whose last digits differ
between compilers and math libraries, so those cases pushed people to mask
the numbers away. A case can now declare a tolerance, relative or absolute,
with a required reason. Only numbers written with a decimal point or an
exponent may differ within it; integers and every other byte must match, a
relative tolerance above 1% is refused, and the tolerance and the largest
difference are recorded in the result. The self-check also fails when a
tolerance is loose enough to hide a change to the leading digit of a number.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The equivalence check compared bytes only, which cannot pass for numeric
code (Fortran, C, scientific and financial results) whose last digits differ
between compilers and math libraries, so those cases pushed people to mask
the numbers away. A case can now declare a tolerance, relative or absolute,
with a required reason. Only numbers written with a decimal point or an
exponent may differ within it; integers and every other byte must match, a
relative tolerance above 1% is refused, and the tolerance and the largest
difference are recorded in the result. The self-check also fails when a
tolerance is loose enough to hide a change to the leading digit of a number.
</pre>
</div>
</content>
</entry>
</feed>
