<feed xmlns='http://www.w3.org/2005/Atom'>
<title>claude-plugins-official.git/plugins/code-modernization/scripts/uplift_checks.py, branch mhegazy/sg-commit-diff-memory</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: 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>
</feed>
