ithrl 0.2.0__tar.gz → 0.4.0__tar.gz

{ithrl-0.2.0 → ithrl-0.4.0}/.gitignore

@@ -10,6 +10,7 @@ __pycache__/
 .coverage
 .coverage.*
 htmlcov/
+/.benchmarks/
 
 # Build artifacts
 build/

ithrl-0.4.0/CHANGELOG.md

@@ -0,0 +1,82 @@
+# CHANGELOG
+
+## v0.4.0 (2026-11-14)
+
+### Features
+
+- Inspect recorded operations across compaction ([#69](https://github.com/eberkut/ithrl/pull/69), [`3594d32`](https://github.com/eberkut/ithrl/commit/3594d3212b6dbc92276223f373908529e95a5e9e))
+- Prepare native reduction experiments offline ([#66](https://github.com/eberkut/ithrl/pull/66), [`13c9626`](https://github.com/eberkut/ithrl/commit/13c96260335982a3a3ce52ea9c73b327f649efce))
+- Qualify passive compaction inspection ([#70](https://github.com/eberkut/ithrl/pull/70), [`3b43a1b`](https://github.com/eberkut/ithrl/commit/3b43a1b8ef0c02bfd0182650460e4efed1c13076))
+
+### Performance Improvements
+
+- Reduce workflow overhead and track performance ([#71](https://github.com/eberkut/ithrl/pull/71), [`ae0c8cd`](https://github.com/eberkut/ithrl/commit/ae0c8cd238eff742ec51076a1054007580c9c0db))
+
+## v0.3.0 (2026-11-10)
+
+### Features
+
+- Add finer final-response reduction ([#52](https://github.com/eberkut/ithrl/pull/52), [`562124a`](https://github.com/eberkut/ithrl/commit/562124ab071788a52e0d50dd538048ee67de464b))
+- Define source-bound text-section removal ([#51](https://github.com/eberkut/ithrl/pull/51), [`56c9e6c`](https://github.com/eberkut/ithrl/commit/56c9e6cfb24a83dc32573232b447e574cb0f616f))
+- Inspect retained context without provider calls ([#49](https://github.com/eberkut/ithrl/pull/49), [`5604688`](https://github.com/eberkut/ithrl/commit/5604688e269543305fe4b7b253a703dc404c1139))
+- **reduce**: Qualify paragraph removal on ordinary sessions ([#58](https://github.com/eberkut/ithrl/pull/58), [`5c6ae26`](https://github.com/eberkut/ithrl/commit/5c6ae26760ea7bd94b406ebf9ba3214e5c4ce64c))
+
+### Refactoring
+
+- Simplify experiment workflows and test fixtures ([#50](https://github.com/eberkut/ithrl/pull/50), [`782bfa2`](https://github.com/eberkut/ithrl/commit/782bfa2692a49a5bb2a4f555801abda23cde6fda))
+
+## v0.2.0 (2026-11-02)
+
+### Bug Fixes
+
+- **codex**: Bound and account for physical provider requests ([#33](https://github.com/eberkut/ithrl/pull/33), [`88529d6`](https://github.com/eberkut/ithrl/commit/88529d6f8b930dbcc546a0011f085c67d0bef1ac))
+- **copilot**: Recover catalogue connections and qualify fuzzing ([#37](https://github.com/eberkut/ithrl/pull/37), [`ff6cf63`](https://github.com/eberkut/ithrl/commit/ff6cf6324325f7f6dad8f8c9c80ea58bfe4e249a))
+- **copilot**: Restore native session prefixes through the CLI ([#34](https://github.com/eberkut/ithrl/pull/34), [`36845dd`](https://github.com/eberkut/ithrl/commit/36845ddb8239c0a488552297aaa70e6211979e59))
+- **fuzz**: Preserve accounting and validate campaign recovery ([#25](https://github.com/eberkut/ithrl/pull/25), [`f1f4793`](https://github.com/eberkut/ithrl/commit/f1f479318fe914f3033667b65381f7101bd3aaea))
+- **sampling**: Enforce calibration budgets and report durable progress ([#32](https://github.com/eberkut/ithrl/pull/32), [`bd40577`](https://github.com/eberkut/ithrl/commit/bd40577c734d70b36e59a9e6d3babafa1502bfd3))
+
+### Features
+
+- **extract**: Support literal predicates for native decisions ([#31](https://github.com/eberkut/ithrl/pull/31), [`3b18c2b`](https://github.com/eberkut/ithrl/commit/3b18c2bdd814c4e4c3bf79825a8cab77eb433661))
+- **fuzz**: Add mutation and sampled comparison services ([`56ee8b8`](https://github.com/eberkut/ithrl/commit/56ee8b8c5e1370b91db6c9c952eb8ceec19c95ae))
+- **fuzz**: Expose inspectable campaigns and saved results ([#24](https://github.com/eberkut/ithrl/pull/24), [`e60e472`](https://github.com/eberkut/ithrl/commit/e60e47230b99e50ff42de7cd8fb89b3769e6d6e2))
+- **fuzz**: Persist campaigns and recover interrupted execution ([#22](https://github.com/eberkut/ithrl/pull/22), [`806667f`](https://github.com/eberkut/ithrl/commit/806667f47e8bae1ccbf9b32fadc511ca559675d0))
+- **fuzz**: Qualify native Codex text appends ([#28](https://github.com/eberkut/ithrl/pull/28), [`a5b880b`](https://github.com/eberkut/ithrl/commit/a5b880b60ef9834bb57b2c4950e18cd17ff0b275))
+
+### Performance Improvements
+
+- Streamline local workflows and harden result publication ([#36](https://github.com/eberkut/ithrl/pull/36), [`43b9d81`](https://github.com/eberkut/ithrl/commit/43b9d81d0dcff85708da5c914986a68bbe8141db))
+
+## v0.1.0 (2026-10-23)
+
+### Bug Fixes
+
+- **adapters**: Detect saved session formats structurally ([`c8256b9`](https://github.com/eberkut/ithrl/commit/c8256b93ce79fb9c3f025e2b92a970f336497218))
+- **reduce**: Validate native candidates before sampled dispatch ([`90d4c0d`](https://github.com/eberkut/ithrl/commit/90d4c0d11a206389d44c6a59991df53c19802514))
+- **runner**: Clarify Codex isolation prerequisites ([`4a409c1`](https://github.com/eberkut/ithrl/commit/4a409c1f37caf301a00cfbd20d3a95cf15844eb9))
+
+### Features
+
+- Establish credential-free context reduction core ([`c517409`](https://github.com/eberkut/ithrl/commit/c517409c06e40c92b24a8b990685abd4acc9a9ba))
+- **adapters**: Parse Codex and Copilot session evidence ([`3b81c26`](https://github.com/eberkut/ithrl/commit/3b81c2607397d884bcfb1b19dbf995f66ccb0107))
+- **calibration**: Add bounded sampled runner calibration ([`f9db180`](https://github.com/eberkut/ithrl/commit/f9db18012565badc2cf2a3a4a6158487d4c5fb70))
+- **case**: Preserve immutable native source evidence ([`d108b96`](https://github.com/eberkut/ithrl/commit/d108b96487ccb69f6b36642ae331d36272038722))
+- **cli**: Add an installed example and focused public guides ([`1efc2ff`](https://github.com/eberkut/ithrl/commit/1efc2ffb03c734b666b1d1da9b5610ad62970267))
+- **cli**: Add guarded native calibration ([`06d2bfb`](https://github.com/eberkut/ithrl/commit/06d2bfb3f4d34f4dc845d9d6877257e4e79f9120))
+- **cli**: Integrate sampled reduction and exact resume ([`40be766`](https://github.com/eberkut/ithrl/commit/40be7664ba90ac5341d93fb5a725dbfa0efd48d3))
+- **extract**: Support ordinary Codex and Copilot sessions ([`3cd0c10`](https://github.com/eberkut/ithrl/commit/3cd0c1092aeb3669b86fdae07e887d28ba9d685f))
+- **reduce**: Add sampled contracts and durable progress ([`650252d`](https://github.com/eberkut/ithrl/commit/650252d76e8d7d72f3f5715ecaf488e752dc18b1))
+- **reduce**: Integrate sampled candidate search ([`72958d8`](https://github.com/eberkut/ithrl/commit/72958d8d6ae0307ca2d090a2a10d02606bafdea6))
+- **runner**: Add Codex final-response execution ([`ad30a9a`](https://github.com/eberkut/ithrl/commit/ad30a9a17b0e665056eca9b415cbf4e2770a7bf7))
+- **runner**: Add controlled Copilot execution ([`c9d1bb2`](https://github.com/eberkut/ithrl/commit/c9d1bb23bfdd98bb022fd0b62ca9b8a81021fe4b))
+- **runner**: Add isolated execution runtime ([`17d2224`](https://github.com/eberkut/ithrl/commit/17d22240414cdb32d4464f16e7b2621d99729ca0))
+- **runner**: Add shared execution foundation ([`89536e9`](https://github.com/eberkut/ithrl/commit/89536e919730fc0abf680a2928a89761c78339f5))
+- **runner**: Validate isolated native calibration ([`b0cd438`](https://github.com/eberkut/ithrl/commit/b0cd438d1fa280f0ddafa39d23653a7ac926da1b))
+- **sampling**: Collect bounded fresh-baseline blocks ([`16abf30`](https://github.com/eberkut/ithrl/commit/16abf30b964eae299177d1e1dade6f545ffbda31))
+- **sampling**: Support paced execution and safe overload replacement ([`5d70fbd`](https://github.com/eberkut/ithrl/commit/5d70fbd26901a0574883e07fd4055644c8515e80))
+- **statistics**: Add fixed-sample candidate classification ([`fb26fca`](https://github.com/eberkut/ithrl/commit/fb26fcaf7c064f49ac7d63b4e2ceb1ab3d6dcdb5))
+- **workflow**: Confirm sampled reductions with fresh evidence ([`ee291e4`](https://github.com/eberkut/ithrl/commit/ee291e4d906394452da61640989cef594f62caf7))
+
+### Refactoring
+
+- Simplify execution paths and avoid redundant context copies ([`34ab361`](https://github.com/eberkut/ithrl/commit/34ab36165fed08678a80679b3f1753e6f26f63f8))

{ithrl-0.2.0 → ithrl-0.4.0}/CONTRIBUTING.md

@@ -26,8 +26,9 @@ For task-specific instructions, see [documentation](#documentation),
 
 ## Development setup
 
-Use [uv](https://docs.astral.sh/uv/) and Python 3.12, 3.13 or 3.14. Python 3.14 is the primary
-development version. From the repository root:
+Use [uv](https://docs.astral.sh/uv/) at the version required by `tool.uv.required-version` in
+`pyproject.toml`, and Python 3.12, 3.13 or 3.14. CI reads the same uv pin through `setup-uv`'s
+`version-file` input. Python 3.14 is the primary development version. From the repository root:
 
 ```bash
 uv sync --locked --all-groups --all-extras
@@ -71,16 +72,73 @@ Install the local hooks with `uv run pre-commit install`; run them on the whole
 `uv run pre-commit run --all-files`. Ruff and rumdl format files in place. CI checks formatting
 without modifying files.
 
-Recognized Markdown-only PRs skip Python linting, typing, unit-test matrices and dependency audits.
-They retain Markdown formatting/linting, documentation tests, the strict site build, workflow and
-dependency review, and all package build/install checks. Mixed changes, unknown paths, configuration
-changes and PRs with 3,000 or more changed files run full validation. Rename detection considers
-both paths; deletions participate. Failed path detection fails the required Workflows check.
-Main-branch, scheduled, manual and release runs always perform full validation.
+Markdown-only PRs skip Python linting, typing, unit tests and dependency audits. They still run
+Markdown, documentation, strict site, workflow, dependency-review and package checks. Mixed changes,
+unknown paths, configuration changes or 3,000 or more changed files require full validation;
+classification includes deleted files and both sides of renames. Failed detection fails Workflows.
+Main, scheduled, manual and release runs always validate fully. The required `Python tests` summary
+accepts a skipped matrix only after successful Markdown-only classification; missing decisions,
+failures and unexpected skips fail it.
+
+The logo sources, usage rules and regeneration commands are in [branding](docs/branding/README.md).
+
+## Performance and maintainability
+
+Measure the affected workflow before optimizing it. Keep sanitized input generation and setup
+outside timings; record the revision, locked environment, input size, repeats and noise. Measure
+allocations separately from elapsed time. Include index/cache construction and retained memory,
+then repeat the same workload after the change. Provider latency and local implementation overhead
+are separate measurements.
+
+- Choose collections for their operations: a set for repeated membership, a dictionary for keyed
+  lookup, and a sequence for authoritative order. For example, fuzz proposal membership can use a
+  local set while seeded traversal retains the original sequence. Measure scaling near admitted
+  limits as well as small inputs; Radon scores alone do not justify a refactor.
+- Keep reusable derived facts with the owner of their immutable inputs. Define copy/invalidation
+  behavior and memory bounds before adding a cache. A frozen model can still copy stale derived
+  state. Do not expose mutable internal indexes or borrow mutable native records across owners.
+- Bound both output and examined work. Count rejected and duplicate proposals where the work cap
+  requires it. Avoid repeated whole-input scans when the required operation is a keyed lookup.
+  Release large temporary buffers before processing the next item.
+- Batch fresh persistence reads where their consistency contract permits it. Preserve schema,
+  identity, chronology and corruption checks, locks, durable dispatch and accounting. Persisted
+  files and external state need fresh validation; an in-memory cache is not their authority. Reuse
+  validated facts within one synchronous operation; refresh after callbacks, waits or execution.
+- Test configurable limits with small inputs at the exact boundary and one beyond; assert policy
+  defaults separately when needed. Use sparse files for size-only filesystem checks. Share completed
+  immutable fixture data, not mutable cases or stores. Retain real process, SQLite and distribution
+  checks when they establish lifecycle, recovery or artifact behavior.
+- Share an existing mechanism only when its ownership, errors and side effects fit. Require a
+  concrete maintenance benefit from abstractions; keep different harness and statistical rules
+  explicit. Compare behavior, failure paths and recovery as well as performance.
+
+### Benchmarks
+
+The permanent [pytest-benchmark](https://pytest-benchmark.readthedocs.io/en/latest/) workloads
+live in `tests/benchmarks/`. They use sanitized inputs and no native harness or provider.
+Ordinary test runs skip them. From the repository root, save a baseline before changing code:
 
-The required `Python tests` check summarizes the test matrix. It accepts a skipped matrix only
-after successful Markdown-only classification. Failed classification, missing decisions, test
-failures and unexpected skips fail this check.
+```bash
+uv run pytest tests/benchmarks --benchmark-only --no-cov --benchmark-save=before
+```
+
+After the change, compare against that saved run:
+
+```bash
+uv run pytest tests/benchmarks --benchmark-only --no-cov --benchmark-compare=0001 --benchmark-save=after
+```
+
+Replace `0001` with the baseline ID printed by the first command. The plugin keeps saved runs
+under the ignored `.benchmarks/` directory. Compare identical workloads on the same interpreter
+and machine with low competing load. Check the distributions and memory tradeoffs; do not infer
+a regression from a small noisy difference. Keep setup outside the measured call and assert
+outcomes. Stateful workloads need equivalent starting state for every round.
+
+CI runs the benchmarks on Python 3.14 in the existing Quality job. Non-PR runs retain the generated
+JSON as `benchmarks-python-3.14` artifacts for 90 days. Download comparable runs and inspect them
+with `uv run pytest-benchmark compare FIRST.json SECOND.json`. There is no elapsed-time failure
+threshold; benchmark assertions still fail on incorrect behavior. Saved JSON contains machine and
+commit metadata; raw profiles and private-workflow inputs do not belong in these artifacts.
 
 ## Workflow and dependency checks
 
@@ -103,14 +161,11 @@ uv export --locked --all-groups --all-extras --no-emit-project --format requirem
   uv run --locked --group audit pip-audit --strict --disable-pip --require-hashes -r /dev/stdin
 ```
 
-The hashed export is temporary pipeline input. The audit queries PyPI's vulnerability service for
-package names and versions without installing those packages, resolving alternatives or applying
-fixes. CI evaluates markers on each supported Python version. This covers locked versions rather
-than every version permitted by package dependency ranges.
-
-For dependency changes, run the lockfile audit above on each supported Python version. GitHub's
-dependency graph may omit packages from `uv.lock`, so Dependabot and Dependency Review cannot
-replace that audit.
+The audit sends locked package names and versions to PyPI's vulnerability service. It installs
+nothing, resolves no alternatives and applies no fixes. It covers locked versions, not entire
+dependency ranges. For dependency changes, run it on each supported Python version to evaluate
+markers. Dependabot and Dependency Review cannot replace it: GitHub's dependency graph may omit
+lockfile packages.
 
 The PR dependency-review job rejects newly introduced known vulnerabilities at any severity across
 runtime, development and unknown scopes. It uses a read-only token and does not check out or execute
@@ -128,13 +183,49 @@ Use `uv run rumdl fmt .` to format Markdown, then `uv run rumdl check .` to lint
 version and `pyproject.toml` configuration apply to pre-commit and CI. Prose wraps at 100
 characters; commands and tables retain their layout. MkDocs syntax is recognized within `docs/`. The
 generated CLI reference has narrow exceptions for Typer's prompts, option alignment and wrapping;
-its byte-for-byte generation check remains enforced. The generated changelog is checked under the
-shared rules.
+its byte-for-byte generation check remains enforced. The generated changelog keeps each entry on
+one source line, with a line-length exception.
 
 Keep installation and first-use instructions in README, and detailed user guides and reference in
 `docs/`. Support, security and conduct policies live at the repository root. Keep private sessions,
 cases and credentials out of documentation and generated output.
 
+### Writing and review
+
+Start with the reader's task. Use [Diátaxis](https://diataxis.fr/start-here/) to distinguish a
+guided learning example, a task-specific how-to, reference facts and explanation. A README can
+combine orientation and first use; do not split pages just to fill those categories.
+
+- Put prerequisites before commands, conditions before dependent actions and the expected result
+  after a step that needs verification. Use numbered steps for a sequence and tables for
+  comparisons.
+- State what the reader can do or conclude. Prefer concrete verbs and established terms; remove
+  filler, promotional claims, rhetorical contrasts and sentences that repeat their heading.
+  For example, replace “It is important to note that execution requires explicit acknowledgement”
+  with “After reviewing the plan, pass `--acknowledge-model-execution` to allow provider calls.”
+- Give each topic one owner. Keep options in the generated CLI reference, procedures in user guides,
+  measurements in `docs/measurements.md`, rationale in decisions and methods in research. Link to
+  detail instead of repeating it. Keep essential safety conditions beside the affected action.
+- Shorten without widening claims. Preserve tested profiles, statistical conditions, costs,
+  uncertainty, failed outcomes and historical context. “The screen passed” does not mean
+  “preservation is confirmed.” Check commands against the current CLI and qualify future work.
+- Follow [W3C's writing guidance](https://www.w3.org/WAI/tips/writing/): use descriptive link text,
+  ordered headings and useful image alternatives. Do not rely on color alone. Keep code blocks
+  executable or identify placeholders before the command.
+
+Before review, check: can the intended reader find the task, run its steps and interpret the
+result? Does each paragraph add information? Are terms, claims, links and generated content current?
+Check the [documentation commands](#building-and-checking-documentation) below after edits.
+
+For additional guidance, consult the
+[Google developer documentation style guide](https://developers.google.com/style) and
+[Microsoft Writing Style Guide](https://learn.microsoft.com/en-us/style-guide/welcome/).
+Follow this project's conventions where they differ.
+Use judgment rather than word-count targets; explanations and research need enough detail to support
+their conclusions.
+
+### Documentation ownership
+
 [ROADMAP.md](ROADMAP.md) describes future direction. GitHub issues own actionable scope,
 dependencies, acceptance criteria and status; release milestones group scope and the public
 [Project](https://github.com/users/eberkut/projects/1/views/4) provides views of those same issues.
@@ -151,12 +242,12 @@ Before evaluating a new study, declare its tested domain, criteria, seeds, budge
 claims. Report costs across complete workflows, including failed and incomplete work, and document
 the alternatives and limitations needed to interpret the results.
 
-The optional `docs` dependency group pins MkDocs and the shadcn theme. Search runs in the browser;
-fonts and scripts are served with the site. GitHub star-count requests and raw Markdown copying
-are disabled. A local hook admits only the packaged theme assets used by this configuration.
-When changing the theme or enabled extensions, check that asset list and the
-[third-party notices](docs/third-party-notices.txt) alongside the rendered site.
-To preview the site locally:
+### Building and checking documentation
+
+The `docs` group pins MkDocs and the shadcn theme. Search runs in the browser; the site bundles
+fonts and scripts. GitHub star-count requests and raw Markdown copying are disabled. When changing
+the theme or extensions, review the asset allowlist in `scripts/docs_theme.py`, the
+[third-party notices](docs/third-party-notices.txt) and the rendered site. To preview:
 
 ```bash
 uv sync --locked --all-groups --all-extras
@@ -292,16 +383,18 @@ CodeRabbit's optional planning and code-generation features are configured in
 
 ## Preparing a release
 
-The release procedures below are for maintainers with repository and package-publishing access.
-
-For every feature, aim for parity across supported harnesses. Any exception must be clearly
-justified and documented before release.
+Maintainers need repository and package-publishing access. Before release, justify and document
+any feature-parity exception between supported harnesses.
 
 Python Semantic Release, pinned in the `release` dependency group, calculates versions from
 Conventional Commits. `pyproject.toml` is the version source; installed CLI and Codex client
 metadata read that distribution version. The tool generates `CHANGELOG.md` from the full release
-history, omitting routine build, CI, documentation, style and test commits. Do not edit the
-generated changelog by hand; review its contents before approving a release.
+history, omitting routine build, CI, documentation, style and test commits. Its
+[template](.github/changelog/CHANGELOG.md.j2) keeps lists compact, with one entry per source line.
+Change the template to adjust formatting; do not edit generated entries by hand.
+
+Review and merge generated version/notes changes through a PR. CI tests the prepared version;
+publication builds that committed version.
 
 Use `main` with complete history and all existing release tags available. Preview the next version
 without changing files, the index, commits, tags or remote state:
@@ -339,9 +432,9 @@ ownership and the following repository/index settings:
 
 - PyPI and TestPyPI Trusted Publishers bind `eberkut/ithrl`, `release.yml` and their respective
   `pypi` / `testpypi` environments. Publishing uses OIDC, without a stored PyPI API token.
-- Both environments admit only `main`. `pypi` requires the maintainer's approval, permits
-  self-review and disallows administrative approval bypass. Environment declarations in YAML
-  do not configure these protections; verify the actual settings before dispatch.
+- Both environments admit only `main`, require the maintainer's approval, permit self-review and
+  disallow administrative approval bypass. Environment declarations in YAML do not configure these
+  protections; verify the actual settings before dispatch.
 - Release-tag rules permit the maintainer's signed-tag creation and prevent unapproved tag
   replacement or deletion. The workflow never creates a tag.
 
@@ -353,10 +446,12 @@ gh workflow run release.yml --repo eberkut/ithrl --ref main \
   -f version=X.Y.Z -f source-sha=FULL_APPROVED_COMMIT_SHA
 ```
 
-1. Inspect that run's checks and successful **Publish TestPyPI rehearsal** job. Its summary records
+1. After source verification and validation pass, approve the `testpypi` deployment on the run's
+   GitHub page. This authorizes the public TestPyPI upload.
+2. Inspect the successful **Publish TestPyPI rehearsal** job. Its summary records
    the source, version, immutable artifact ID and checksum-manifest digest. The production job
    waits at the `pypi` environment. TestPyPI files, logs and artifacts are public.
-2. Download that run's `release-distributions` artifact into a new review directory. For example:
+3. Download that run's `release-distributions` artifact into a new review directory. For example:
 
    ```bash
    gh run download RUN_ID --repo eberkut/ithrl \
@@ -367,7 +462,7 @@ gh workflow run release.yml --repo eberkut/ithrl --ref main \
    from the review directory. Inspect the release notes and confirm TestPyPI serves the same
    distribution hashes. Complete a clean TestPyPI installation/example rehearsal before approval;
    resolve dependencies only from the normal PyPI index, without mixing indexes.
-3. After the rehearsal passes and tag creation is approved, create and verify the signed tag at
+4. After the rehearsal passes and tag creation is approved, create and verify the signed tag at
    the frozen source commit, then push only that tag through the permitted tag-rules path:
 
    ```bash
@@ -376,19 +471,19 @@ gh workflow run release.yml --repo eberkut/ithrl --ref main \
    git push origin refs/tags/vX.Y.Z
    ```
 
-4. Review and approve the `pypi` deployment on the run's GitHub page. The job verifies the existing
+5. Review and approve the `pypi` deployment on the run's GitHub page. The job verifies the existing
    annotated tag targets the frozen source, rechecks the files, and uploads to PyPI. The final job
    rechecks the tag/files and creates the GitHub Release with those distributions, notes and
    checksums. Signature verification belongs to the preceding maintainer tag check; the workflow
    checks the tag object and target commit.
-5. Verify the published versions, hashes, attestations and installed example. A successful upload
+6. Verify the published versions, hashes, attestations and installed example. A successful upload
    alone does not complete release acceptance.
 
-Complete review within 30 days: release artifacts are retained for 30 days, and GitHub limits the
-total workflow lifetime, including approval waits. Start only one release at a time; concurrency
-preserves the active run but GitHub may replace an older pending run when another is queued.
-Do not rerun the whole workflow to promote a completed rehearsal or cancel a run during upload.
-For failure or partial publication, inspect the index and existing release first; preserve the
-original files and hashes. Any recovery upload needs explicit approval and must use identical
-missing files. Never rebuild and overwrite a published version or suppress conflicts with
-`skip-existing`.
+Complete review within the 30-day artifact retention and GitHub workflow lifetime, including
+approval waits. Start one release at a time: a new queued run may replace an older pending run,
+though the active run is preserved. Do not rerun the workflow to promote a completed rehearsal or
+cancel during upload.
+
+After failure or partial publication, inspect the index and release before recovery. Preserve
+the original files and hashes; uploading identical missing files requires explicit approval.
+Never overwrite a published version with rebuilt files or suppress conflicts with `skip-existing`.

{ithrl-0.2.0 → ithrl-0.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: ithrl
-Version: 0.2.0
+Version: 0.4.0
 Summary: Find smaller agent contexts that preserve a selected model behavior
 Project-URL: Source, https://github.com/eberkut/ithrl
 Project-URL: Issues, https://github.com/eberkut/ithrl/issues
@@ -31,7 +31,15 @@ Provides-Extra: fuzz
 Requires-Dist: scipy>=1.18; extra == 'fuzz'
 Description-Content-Type: text/markdown
 
-# ithrl
+<!-- rumdl-disable MD033 -->
+<h1>
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/eberkut/ithrl/main/docs/branding/ithrl-logo-dark.svg">
+    <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/eberkut/ithrl/main/docs/branding/ithrl-logo-light.svg">
+    <img src="https://raw.githubusercontent.com/eberkut/ithrl/main/docs/branding/ithrl-logo.png" alt="ithrl" width="320" height="158">
+  </picture>
+</h1>
+<!-- rumdl-enable MD033 -->
 
 [![PyPI](https://img.shields.io/pypi/v/ithrl.svg)](https://pypi.org/project/ithrl/)
 [![CI](https://github.com/eberkut/ithrl/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/eberkut/ithrl/actions/workflows/ci.yml)
@@ -87,7 +95,18 @@ Use a new directory to repeat the example; extraction refuses to overwrite an ex
 ## Commands
 
 - `ithrl extract` browses saved sessions and creates a case from a selected decision.
+- `ithrl prepare CASE` generates a private reduction configuration from a preflight receipt and
+  statistical settings. Follow the
+  [preparation procedure](https://github.com/eberkut/ithrl/blob/main/docs/reduction.md).
 - `ithrl shrink CASE` searches for context removals that preserve the selected behavior.
+- `ithrl inspect sections CASE` lists editable text fields and paragraph boundaries without
+  displaying text or requiring a reduction result.
+- `ithrl inspect reacquire SESSION` compares recorded operations and captured results across
+  compaction. See
+  [passive inspection](https://github.com/eberkut/ithrl/blob/main/docs/results.md#inspect-recorded-compaction).
+- `ithrl inspect retained CASE --result RESULT` explains retained units and recorded removal trials
+  from a saved reduction without model access. See
+  [results and privacy](https://github.com/eberkut/ithrl/blob/main/docs/results.md#inspect-retained-context).
 - `ithrl fuzz CASE --config PRIVATE_TOML` searches for and simplifies text appends that decrease how
   often the selected behavior occurs, with independent confirmation.
 
@@ -104,30 +123,40 @@ Returned actions are observed and denied. Cases contain copied session content;
 
 ## Supported inputs
 
-| Input | Extracted decisions | Reduction | Fuzzing |
-| --- | --- | --- | --- |
-| Bundled synthetic example | Synthetic tool request | Deterministic local runner | Local fake runner |
-| Codex CLI rollouts | Final responses | Experimental native runner | Experimental prior-user text appends |
-| Copilot CLI session events | Final responses and shell requests | Experimental final-response and denied `bash` runner | Experimental prior-user text appends for final-response targets |
-
-Native Codex and Copilot final-response fuzzing supports appending text to eligible prior user
-input while preserving the fixed triggering input. The
-[fuzzing walkthrough](https://github.com/eberkut/ithrl/blob/main/docs/native-runs.md#context-fuzzing)
-starts with a local example and covers native execution.
-
-[Saved-session measurements](https://github.com/eberkut/ithrl/blob/main/docs/measurements.md#saved-session-experiments)
-include a confirmed reduction for one Codex session and its chosen predicate: 50.17% lower mean
-input tokens per confirmation observation, using a 20-percentage-point preservation margin.
-The measurements report resource usage and unsuccessful outcomes alongside completed runs. Check
+| Input | Extracted decisions | Reduction | Fuzzing | Passive inspection |
+| --- | --- | --- | --- | --- |
+| Bundled synthetic example | Synthetic tool request | Deterministic local runner | Local fake runner | — |
+| Codex CLI rollouts | Final responses | Experimental native runner; [paragraph-removal measurements](https://github.com/eberkut/ithrl/blob/main/docs/measurements.md#ordinary-session-paragraph-removal) | Experimental prior-user text appends | Exact recorded-operation and captured-result comparisons across compaction |
+| Copilot CLI session events | Final responses and shell requests | Experimental final-response paragraph removal and denied `bash` runner | Experimental prior-user text appends for final-response targets | Exact recorded-operation and captured-result comparisons across compaction |
+
+Passive inspection reads saved evidence without a harness or model access. The
+[worked investigation](https://github.com/eberkut/ithrl/blob/main/docs/research/passive-compaction-investigation.md)
+records the qualified native profiles, ordinary examples and interpretation limits.
+
+Native fuzzing appends text to eligible prior user input while preserving the fixed triggering
+input. The
+[fuzzing walkthrough](https://github.com/eberkut/ithrl/blob/main/docs/fuzzing.md)
+covers a local example and native execution.
+
+Ordinary Codex and Copilot paragraph-removal experiments passed fresh confirmation at a
+20-percentage-point preservation margin. See the
+[measurements](https://github.com/eberkut/ithrl/blob/main/docs/measurements.md#saved-session-experiments)
+for completed and unsuccessful outcomes, costs and qualification limits, and the
+[worked investigation](https://github.com/eberkut/ithrl/blob/main/docs/research/ordinary-session-investigation.md)
+for a developer's interpretation. Check
 [native compatibility](https://github.com/eberkut/ithrl/blob/main/docs/native-runs.md#compatibility-and-measurements)
-for the installed harness's requirements.
+before using an installed harness.
 
 ## Documentation
 
 Read the [documentation site](https://eberkut.github.io/ithrl/) or browse the guides below.
 
 - [Native runs](https://github.com/eberkut/ithrl/blob/main/docs/native-runs.md): session selection,
-  experiment configuration, preflight, model execution and measured resource usage.
+  shared prerequisites and compatibility.
+- [Native reduction](https://github.com/eberkut/ithrl/blob/main/docs/reduction.md): prepare,
+  inspect and execute a context-removal experiment.
+- [Context fuzzing](https://github.com/eberkut/ithrl/blob/main/docs/fuzzing.md): try the local
+  example and run a native text-append campaign.
 - [Results and privacy](https://github.com/eberkut/ithrl/blob/main/docs/results.md): saved files,
   result interpretation, budgets, resume and sensitive data.
 - [Contributing](https://github.com/eberkut/ithrl/blob/main/CONTRIBUTING.md): issue-first

{ithrl-0.2.0 → ithrl-0.4.0}/README.md

@@ -1,4 +1,12 @@
-# ithrl
+<!-- rumdl-disable MD033 -->
+<h1>
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/eberkut/ithrl/main/docs/branding/ithrl-logo-dark.svg">
+    <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/eberkut/ithrl/main/docs/branding/ithrl-logo-light.svg">
+    <img src="https://raw.githubusercontent.com/eberkut/ithrl/main/docs/branding/ithrl-logo.png" alt="ithrl" width="320" height="158">
+  </picture>
+</h1>
+<!-- rumdl-enable MD033 -->
 
 [![PyPI](https://img.shields.io/pypi/v/ithrl.svg)](https://pypi.org/project/ithrl/)
 [![CI](https://github.com/eberkut/ithrl/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/eberkut/ithrl/actions/workflows/ci.yml)
@@ -54,7 +62,18 @@ Use a new directory to repeat the example; extraction refuses to overwrite an ex
 ## Commands
 
 - `ithrl extract` browses saved sessions and creates a case from a selected decision.
+- `ithrl prepare CASE` generates a private reduction configuration from a preflight receipt and
+  statistical settings. Follow the
+  [preparation procedure](https://github.com/eberkut/ithrl/blob/main/docs/reduction.md).
 - `ithrl shrink CASE` searches for context removals that preserve the selected behavior.
+- `ithrl inspect sections CASE` lists editable text fields and paragraph boundaries without
+  displaying text or requiring a reduction result.
+- `ithrl inspect reacquire SESSION` compares recorded operations and captured results across
+  compaction. See
+  [passive inspection](https://github.com/eberkut/ithrl/blob/main/docs/results.md#inspect-recorded-compaction).
+- `ithrl inspect retained CASE --result RESULT` explains retained units and recorded removal trials
+  from a saved reduction without model access. See
+  [results and privacy](https://github.com/eberkut/ithrl/blob/main/docs/results.md#inspect-retained-context).
 - `ithrl fuzz CASE --config PRIVATE_TOML` searches for and simplifies text appends that decrease how
   often the selected behavior occurs, with independent confirmation.
 
@@ -71,30 +90,40 @@ Returned actions are observed and denied. Cases contain copied session content;
 
 ## Supported inputs
 
-| Input | Extracted decisions | Reduction | Fuzzing |
-| --- | --- | --- | --- |
-| Bundled synthetic example | Synthetic tool request | Deterministic local runner | Local fake runner |
-| Codex CLI rollouts | Final responses | Experimental native runner | Experimental prior-user text appends |
-| Copilot CLI session events | Final responses and shell requests | Experimental final-response and denied `bash` runner | Experimental prior-user text appends for final-response targets |
-
-Native Codex and Copilot final-response fuzzing supports appending text to eligible prior user
-input while preserving the fixed triggering input. The
-[fuzzing walkthrough](https://github.com/eberkut/ithrl/blob/main/docs/native-runs.md#context-fuzzing)
-starts with a local example and covers native execution.
-
-[Saved-session measurements](https://github.com/eberkut/ithrl/blob/main/docs/measurements.md#saved-session-experiments)
-include a confirmed reduction for one Codex session and its chosen predicate: 50.17% lower mean
-input tokens per confirmation observation, using a 20-percentage-point preservation margin.
-The measurements report resource usage and unsuccessful outcomes alongside completed runs. Check
+| Input | Extracted decisions | Reduction | Fuzzing | Passive inspection |
+| --- | --- | --- | --- | --- |
+| Bundled synthetic example | Synthetic tool request | Deterministic local runner | Local fake runner | — |
+| Codex CLI rollouts | Final responses | Experimental native runner; [paragraph-removal measurements](https://github.com/eberkut/ithrl/blob/main/docs/measurements.md#ordinary-session-paragraph-removal) | Experimental prior-user text appends | Exact recorded-operation and captured-result comparisons across compaction |
+| Copilot CLI session events | Final responses and shell requests | Experimental final-response paragraph removal and denied `bash` runner | Experimental prior-user text appends for final-response targets | Exact recorded-operation and captured-result comparisons across compaction |
+
+Passive inspection reads saved evidence without a harness or model access. The
+[worked investigation](https://github.com/eberkut/ithrl/blob/main/docs/research/passive-compaction-investigation.md)
+records the qualified native profiles, ordinary examples and interpretation limits.
+
+Native fuzzing appends text to eligible prior user input while preserving the fixed triggering
+input. The
+[fuzzing walkthrough](https://github.com/eberkut/ithrl/blob/main/docs/fuzzing.md)
+covers a local example and native execution.
+
+Ordinary Codex and Copilot paragraph-removal experiments passed fresh confirmation at a
+20-percentage-point preservation margin. See the
+[measurements](https://github.com/eberkut/ithrl/blob/main/docs/measurements.md#saved-session-experiments)
+for completed and unsuccessful outcomes, costs and qualification limits, and the
+[worked investigation](https://github.com/eberkut/ithrl/blob/main/docs/research/ordinary-session-investigation.md)
+for a developer's interpretation. Check
 [native compatibility](https://github.com/eberkut/ithrl/blob/main/docs/native-runs.md#compatibility-and-measurements)
-for the installed harness's requirements.
+before using an installed harness.
 
 ## Documentation
 
 Read the [documentation site](https://eberkut.github.io/ithrl/) or browse the guides below.
 
 - [Native runs](https://github.com/eberkut/ithrl/blob/main/docs/native-runs.md): session selection,
-  experiment configuration, preflight, model execution and measured resource usage.
+  shared prerequisites and compatibility.
+- [Native reduction](https://github.com/eberkut/ithrl/blob/main/docs/reduction.md): prepare,
+  inspect and execute a context-removal experiment.
+- [Context fuzzing](https://github.com/eberkut/ithrl/blob/main/docs/fuzzing.md): try the local
+  example and run a native text-append campaign.
 - [Results and privacy](https://github.com/eberkut/ithrl/blob/main/docs/results.md): saved files,
   result interpretation, budgets, resume and sensitive data.
 - [Contributing](https://github.com/eberkut/ithrl/blob/main/CONTRIBUTING.md): issue-first