<feed xmlns='http://www.w3.org/2005/Atom'>
<title>claude-plugins-official.git/plugins/code-modernization, 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: rename the pane's rule review command to /modernize-review-pane</title>
<updated>2026-09-25T18:28:51+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T18:28:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=28abd83ad92c24a4107803bd03e510387f2014c2'/>
<id>28abd83ad92c24a4107803bd03e510387f2014c2</id>
<content type='text'>
The pane's bare /modernize-review took the name of the plugin's own review command, so typing the short form in a pane-enabled session opened the pane's cards instead of the pop-up review. The pane's version is now /modernize-review-pane, and /modernize-review always runs the plugin command. Both still write the same review file.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The pane's bare /modernize-review took the name of the plugin's own review command, so typing the short form in a pane-enabled session opened the pane's cards instead of the pop-up review. The pane's version is now /modernize-review-pane, and /modernize-review always runs the plugin command. Both still write the same review file.
</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: fold the same rule found in several files into one</title>
<updated>2026-09-25T04:18:31+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T04:18:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=fc8adcf13fab336a810a622e8cf7be86be3a183b'/>
<id>fc8adcf13fab336a810a622e8cf7be86be3a183b</id>
<content type='text'>
A numeric library implemented in C, in a C++ header and in a fixed-point
variant produced three "twiddle factor" rules, two "generic butterfly" rules
and two "factorization" rules, because the referee's duplicate key is the
file plus the rule's name. The plan and the review then carry noise.

After verification, one small agent per 150 rules lists the groups that
describe the same behavior implemented in more than one place, told to merge
only what would be implemented and tested as one thing. The kept rule cites
every place (the renderer shows them as "Also cited") and takes the highest
priority of its group; overlapping, out-of-range or self-merging groups are
ignored, and the rule list is fenced as untrusted data. The count is
reported as stats.consolidated.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
A numeric library implemented in C, in a C++ header and in a fixed-point
variant produced three "twiddle factor" rules, two "generic butterfly" rules
and two "factorization" rules, because the referee's duplicate key is the
file plus the rule's name. The plan and the review then carry noise.

After verification, one small agent per 150 rules lists the groups that
describe the same behavior implemented in more than one place, told to merge
only what would be implemented and tested as one thing. The kept rule cites
every place (the renderer shows them as "Also cited") and takes the highest
priority of its group; overlapping, out-of-range or self-merging groups are
ignored, and the rule list is fenced as untrusted data. The count is
reported as stats.consolidated.
</pre>
</div>
</content>
</entry>
<entry>
<title>code-modernization: safer, more general version uplifts</title>
<updated>2026-09-25T04:10:47+00:00</updated>
<author>
<name>Morgan Lunt</name>
<email>morganl@anthropic.com</email>
</author>
<published>2026-09-25T04:10:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.1991861.xyz/claude-plugins-official.git/commit/?id=6436c5a81d2b163fe5a1c971b96f211d910bd75a'/>
<id>6436c5a81d2b163fe5a1c971b96f211d910bd75a</id>
<content type='text'>
Found by reading the commands as an engineer with a large Java 8 system:

- The baseline suite was run "on legacy/&lt;system&gt;", which writes build output
  into the source. It now runs on a scratch copy, its result files or log are
  kept under analysis/&lt;system&gt;/baseline/ and named in BASELINE.md, and a
  typed table alone no longer counts as a measured baseline.
- The working copy no longer carries the source repository's history, keeps
  files that look like credentials or production settings out of its first
  commit and lists them for a person, and moves that history to its own new
  local repository.
- Migration tools (OpenRewrite and the like) run on a scratch copy, never in
  the source, since a dry run still builds and downloads.
- A move spanning several versions or two things at once (a JDK and a
  framework) is split into hops that each build and test green.
- Tests are not run against a database or service the configuration names
  until the person says it is a local or throwaway instance.
- The silent-behavior hunt now names the usual traps for Java, Python, Node
  and PHP as well as .NET (locale data, default charset, ORM mappings,
  property binding, str/bytes).
- The brief no longer requires business rules for a same-technology uplift:
  the recorded baseline is its behavior contract, so extract-rules can wait.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Found by reading the commands as an engineer with a large Java 8 system:

- The baseline suite was run "on legacy/&lt;system&gt;", which writes build output
  into the source. It now runs on a scratch copy, its result files or log are
  kept under analysis/&lt;system&gt;/baseline/ and named in BASELINE.md, and a
  typed table alone no longer counts as a measured baseline.
- The working copy no longer carries the source repository's history, keeps
  files that look like credentials or production settings out of its first
  commit and lists them for a person, and moves that history to its own new
  local repository.
- Migration tools (OpenRewrite and the like) run on a scratch copy, never in
  the source, since a dry run still builds and downloads.
- A move spanning several versions or two things at once (a JDK and a
  framework) is split into hops that each build and test green.
- Tests are not run against a database or service the configuration names
  until the person says it is a local or throwaway instance.
- The silent-behavior hunt now names the usual traps for Java, Python, Node
  and PHP as well as .NET (locale data, default charset, ORM mappings,
  property binding, str/bytes).
- The brief no longer requires business rules for a same-technology uplift:
  the recorded baseline is its behavior contract, so extract-rules can wait.
</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>
</feed>
