onetrace-console 0.1.0__tar.gz

onetrace_console-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

onetrace_console-0.1.0/PKG-INFO

@@ -0,0 +1,91 @@
+Metadata-Version: 2.4
+Name: onetrace-console
+Version: 0.1.0
+Summary: The onetrace console: every run in one place, read from the reports the verifier and the verbs produced.
+Author: Shamik Saha
+License: Apache-2.0
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: onetrace==0.2.0
+Requires-Dist: onetrace-verify[crypto]==0.2.0
+Provides-Extra: test
+Requires-Dist: pytest>=8; extra == "test"
+Dynamic: license-file
+
+# onetrace-console
+
+A local web console for runs recorded with [onetrace](https://oneproof.dev/onetrace/): every run in one place, each one checked by the verifier, and any two compared stage by stage.
+
+The console never computes a verdict of its own. It keeps each run's files exactly as they were written, runs `onetrace-verify` and the SDK's own `diff` over them, and shows what those report. If the console and the run folder ever disagree, the folder is right.
+
+## Install
+
+```
+pip install onetrace-console
+```
+
+It needs Python 3.12 or later. It installs from PyPI alone: `onetrace` 0.2.0 and `onetrace-verify` 0.2.0, with the `[crypto]` extra so signatures and anchors are checked. The pages' viewer ships inside the package.
+
+## See it with the demo's runs
+
+```
+onetrace-console demo
+```
+
+This copies the reference demo's two runs into `onetrace-console-demo/` under the folder you start it from, starts the console, loads both runs, compares them, and prints the pages' addresses. The demo keeps its store and its trust file in that folder too. It runs in local mode, so it refuses to start while `ONETRACE_CONSOLE_CONFIG` is set.
+
+![The overview, with the demo's two runs](https://raw.githubusercontent.com/shamiksaharcciit-oss/onetrace-console/v0.1.0/docs/screenshots/overview.png)
+
+A read-only copy of the demo is hosted at https://demo.oneproof.dev. To try the read-only mode yourself, run `onetrace-console demo --public`.
+
+## Your own runs
+
+```
+onetrace-console <runs folder>
+onetrace-console <runs folder> --compare <run A> <run B>
+onetrace-console <runs folder> --open
+```
+
+- `onetrace-console <runs folder>` loads every run folder in it: every folder holding a `MANIFEST.json`. It compares nothing unless you ask.
+- A run folder is skipped, with the reason, while the others load: a run still being recorded (it holds onetrace's `.lock`), a folder that holds a link, or a folder whose `SHA256SUMS` doesn't match its files.
+- `--compare A B` compares two of them, named by their folder names; A is the baseline.
+- `--open` opens the console in your browser.
+- `--port N` listens on port N, here and for `demo`. The default is 8080.
+
+![One run's page, with the verifier's result](https://raw.githubusercontent.com/shamiksaharcciit-oss/onetrace-console/v0.1.0/docs/screenshots/run.png)
+
+![A comparison of two runs, with the first stage that changed](https://raw.githubusercontent.com/shamiksaharcciit-oss/onetrace-console/v0.1.0/docs/screenshots/comparison.png)
+
+## What it shows
+
+- **Each run:** the verifier's result and every row it reported, the run's stages, and its receipt, including whether it is signed and anchored.
+- **Two runs compared:** the stage-by-stage comparison `onetrace diff` produces, and the text that changed, as the SDK reports them.
+- **Counts:** every number with what it counts, and a link to the exact runs behind it.
+
+## What it does not show
+
+Nothing here says which version is correct, who changed the source, or why.
+
+A run's record does not show:
+
+- that the output or the action was correct;
+- why the model wrote what it wrote;
+- that the signing key wasn't misused (your trust list is what ties a key to a name);
+- that the run was correct at the anchored time (the anchor shows only that the record existed by then).
+
+## Where it runs
+
+Started as above, it listens on 127.0.0.1 only, and makes no network calls; `--open` asks your browser to open the local page. A folder load keeps what it stores in a `store` folder under the folder you start it from, and `demo` keeps it in `onetrace-console-demo/`.
+
+To run it for a team, as a container with sign-in, see [OPERATOR_README.md](https://github.com/shamiksaharcciit-oss/onetrace-console/blob/v0.1.0/OPERATOR_README.md).
+
+## For contributors
+
+On Windows, run the test suite from a short path (for example `C:\src\oc`), or turn on long paths: some of the files the suite writes have paths longer than Windows' 260-character limit.
+
+## Licence
+
+Copyright 2026 Shamik Saha. Licensed under Apache-2.0; see LICENSE.
+
+The bundled IBM Plex fonts are under the SIL Open Font License 1.1.

onetrace_console-0.1.0/PYPI_DESCRIPTION.md

@@ -0,0 +1,76 @@
+# onetrace-console
+
+A local web console for runs recorded with [onetrace](https://oneproof.dev/onetrace/): every run in one place, each one checked by the verifier, and any two compared stage by stage.
+
+The console never computes a verdict of its own. It keeps each run's files exactly as they were written, runs `onetrace-verify` and the SDK's own `diff` over them, and shows what those report. If the console and the run folder ever disagree, the folder is right.
+
+## Install
+
+```
+pip install onetrace-console
+```
+
+It needs Python 3.12 or later. It installs from PyPI alone: `onetrace` 0.2.0 and `onetrace-verify` 0.2.0, with the `[crypto]` extra so signatures and anchors are checked. The pages' viewer ships inside the package.
+
+## See it with the demo's runs
+
+```
+onetrace-console demo
+```
+
+This copies the reference demo's two runs into `onetrace-console-demo/` under the folder you start it from, starts the console, loads both runs, compares them, and prints the pages' addresses. The demo keeps its store and its trust file in that folder too. It runs in local mode, so it refuses to start while `ONETRACE_CONSOLE_CONFIG` is set.
+
+![The overview, with the demo's two runs](https://raw.githubusercontent.com/shamiksaharcciit-oss/onetrace-console/v0.1.0/docs/screenshots/overview.png)
+
+A read-only copy of the demo is hosted at https://demo.oneproof.dev. To try the read-only mode yourself, run `onetrace-console demo --public`.
+
+## Your own runs
+
+```
+onetrace-console <runs folder>
+onetrace-console <runs folder> --compare <run A> <run B>
+onetrace-console <runs folder> --open
+```
+
+- `onetrace-console <runs folder>` loads every run folder in it: every folder holding a `MANIFEST.json`. It compares nothing unless you ask.
+- A run folder is skipped, with the reason, while the others load: a run still being recorded (it holds onetrace's `.lock`), a folder that holds a link, or a folder whose `SHA256SUMS` doesn't match its files.
+- `--compare A B` compares two of them, named by their folder names; A is the baseline.
+- `--open` opens the console in your browser.
+- `--port N` listens on port N, here and for `demo`. The default is 8080.
+
+![One run's page, with the verifier's result](https://raw.githubusercontent.com/shamiksaharcciit-oss/onetrace-console/v0.1.0/docs/screenshots/run.png)
+
+![A comparison of two runs, with the first stage that changed](https://raw.githubusercontent.com/shamiksaharcciit-oss/onetrace-console/v0.1.0/docs/screenshots/comparison.png)
+
+## What it shows
+
+- **Each run:** the verifier's result and every row it reported, the run's stages, and its receipt, including whether it is signed and anchored.
+- **Two runs compared:** the stage-by-stage comparison `onetrace diff` produces, and the text that changed, as the SDK reports them.
+- **Counts:** every number with what it counts, and a link to the exact runs behind it.
+
+## What it does not show
+
+Nothing here says which version is correct, who changed the source, or why.
+
+A run's record does not show:
+
+- that the output or the action was correct;
+- why the model wrote what it wrote;
+- that the signing key wasn't misused (your trust list is what ties a key to a name);
+- that the run was correct at the anchored time (the anchor shows only that the record existed by then).
+
+## Where it runs
+
+Started as above, it listens on 127.0.0.1 only, and makes no network calls; `--open` asks your browser to open the local page. A folder load keeps what it stores in a `store` folder under the folder you start it from, and `demo` keeps it in `onetrace-console-demo/`.
+
+To run it for a team, as a container with sign-in, see [OPERATOR_README.md](https://github.com/shamiksaharcciit-oss/onetrace-console/blob/v0.1.0/OPERATOR_README.md).
+
+## For contributors
+
+On Windows, run the test suite from a short path (for example `C:\src\oc`), or turn on long paths: some of the files the suite writes have paths longer than Windows' 260-character limit.
+
+## Licence
+
+Copyright 2026 Shamik Saha. Licensed under Apache-2.0; see LICENSE.
+
+The bundled IBM Plex fonts are under the SIL Open Font License 1.1.

onetrace_console-0.1.0/README.md

@@ -0,0 +1,76 @@
+# onetrace-console
+
+A local web console for runs recorded with [onetrace](https://oneproof.dev/onetrace/): every run in one place, each one checked by the verifier, and any two compared stage by stage.
+
+The console never computes a verdict of its own. It keeps each run's files exactly as they were written, runs `onetrace-verify` and the SDK's own `diff` over them, and shows what those report. If the console and the run folder ever disagree, the folder is right.
+
+## Install
+
+```
+pip install onetrace-console
+```
+
+It needs Python 3.12 or later. It installs from PyPI alone: `onetrace` 0.2.0 and `onetrace-verify` 0.2.0, with the `[crypto]` extra so signatures and anchors are checked. The pages' viewer ships inside the package.
+
+## See it with the demo's runs
+
+```
+onetrace-console demo
+```
+
+This copies the reference demo's two runs into `onetrace-console-demo/` under the folder you start it from, starts the console, loads both runs, compares them, and prints the pages' addresses. The demo keeps its store and its trust file in that folder too. It runs in local mode, so it refuses to start while `ONETRACE_CONSOLE_CONFIG` is set.
+
+![The overview, with the demo's two runs](docs/screenshots/overview.png)
+
+A read-only copy of the demo is hosted at https://demo.oneproof.dev. To try the read-only mode yourself, run `onetrace-console demo --public`.
+
+## Your own runs
+
+```
+onetrace-console <runs folder>
+onetrace-console <runs folder> --compare <run A> <run B>
+onetrace-console <runs folder> --open
+```
+
+- `onetrace-console <runs folder>` loads every run folder in it: every folder holding a `MANIFEST.json`. It compares nothing unless you ask.
+- A run folder is skipped, with the reason, while the others load: a run still being recorded (it holds onetrace's `.lock`), a folder that holds a link, or a folder whose `SHA256SUMS` doesn't match its files.
+- `--compare A B` compares two of them, named by their folder names; A is the baseline.
+- `--open` opens the console in your browser.
+- `--port N` listens on port N, here and for `demo`. The default is 8080.
+
+![One run's page, with the verifier's result](docs/screenshots/run.png)
+
+![A comparison of two runs, with the first stage that changed](docs/screenshots/comparison.png)
+
+## What it shows
+
+- **Each run:** the verifier's result and every row it reported, the run's stages, and its receipt, including whether it is signed and anchored.
+- **Two runs compared:** the stage-by-stage comparison `onetrace diff` produces, and the text that changed, as the SDK reports them.
+- **Counts:** every number with what it counts, and a link to the exact runs behind it.
+
+## What it does not show
+
+Nothing here says which version is correct, who changed the source, or why.
+
+A run's record does not show:
+
+- that the output or the action was correct;
+- why the model wrote what it wrote;
+- that the signing key wasn't misused (your trust list is what ties a key to a name);
+- that the run was correct at the anchored time (the anchor shows only that the record existed by then).
+
+## Where it runs
+
+Started as above, it listens on 127.0.0.1 only, and makes no network calls; `--open` asks your browser to open the local page. A folder load keeps what it stores in a `store` folder under the folder you start it from, and `demo` keeps it in `onetrace-console-demo/`.
+
+To run it for a team, as a container with sign-in, see [OPERATOR_README.md](OPERATOR_README.md).
+
+## For contributors
+
+On Windows, run the test suite from a short path (for example `C:\src\oc`), or turn on long paths: some of the files the suite writes have paths longer than Windows' 260-character limit.
+
+## Licence
+
+Copyright 2026 Shamik Saha. Licensed under Apache-2.0; see LICENSE.
+
+The bundled IBM Plex fonts are under the SIL Open Font License 1.1.

onetrace_console-0.1.0/pyproject.toml

@@ -0,0 +1,106 @@
+[build-system]
+requires = ["setuptools>=68"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "onetrace-console"
+version = "0.1.0"
+description = "The onetrace console: every run in one place, read from the reports the verifier and the verbs produced."
+readme = "PYPI_DESCRIPTION.md"     # the README with absolute image links: tools/pypi_description.py
+requires-python = ">=3.12"
+license = { text = "Apache-2.0" }
+authors = [{ name = "Shamik Saha" }]
+
+# Abstract here, pinned in requirements.lock. Nothing is vendored.
+#
+# There is no web framework and no database driver, and that is a decision rather than an
+# omission. The console ships as a CONTAINER THE CUSTOMER RUNS -- no shared back end, no
+# assumed network access, no data sent home -- so every dependency is a thing the
+# customer must trust and a thing that must be present with no index reachable. The
+# server is `http.server`, the store is files, the index is `sqlite3`, the tar is
+# `tarfile`, the digests are `hashlib`: all standard library. See DESIGN_GAPS.md.
+dependencies = [
+    "onetrace==0.2.0",                 # the SDK this release was tested with: the verbs
+    "onetrace-verify[crypto]==0.2.0",  # the verifier, with what it needs to check signatures
+]
+
+[project.optional-dependencies]
+test = ["pytest>=8"]
+
+[project.scripts]
+onetrace-console = "onetrace_console.__main__:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+# The console serves IBM Plex itself, so the fonts and their OFL text are
+# package data (the container runs from src/ and carries them either way).
+[tool.setuptools.package-data]
+onetrace_console = ["static/fonts/*.woff2", "static/fonts/OFL.txt", "static/fonts/FONTS.md",
+                    "requirements.lock", "reference_demo/trust.json", "reference_demo/runs/**/*",
+                    "viewer/PROVENANCE.md", "viewer/_vendor/*"]
+
+# ---------------------------------------------------------------------------------
+# E10 layer 2 of 3: exclusion lists
+# ---------------------------------------------------------------------------------
+# Formatters, linters and auto-fixers are byte-rewriting tools. Pointed at a stored run
+# they destroy the evidence they were pointed at, silently, with a green exit code.
+#
+# Layer 1 (`.gitattributes`, `* -text`) stops git from rewriting bytes. THIS layer stops
+# our own tooling. Any tool added later MUST be given the same exclusions in this same
+# place. `store/` is where received bundles land at runtime and is never tracked, but it
+# is named here too: an exclusion that only covers what is committed is an exclusion that
+# stops working the moment someone runs a formatter on a working tree.
+[tool.ruff]
+extend-exclude = ["tests/fixtures", "store", "src/onetrace_console/_received"]
+
+[tool.black]
+extend-exclude = "tests/fixtures|store|src/onetrace_console/_received"
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+python_files = ["test_*.py"]
+
+# `--basetemp` is set here, to a repository-local folder git ignores, so the suite stops
+# depending on pytest's cleanup of the system temp folder.
+#
+# WHAT IT FIXES. pytest's default temp root is `<system temp>/pytest-of-<user>`, and its
+# session teardown cleans that directory -- including `cleanup_dead_symlinks`, which stats
+# a `pytest-current` reparse point. On this machine that reparse point became unreadable,
+# `os.stat` raised `PermissionError [WinError 5]`, the exception escaped the exit stack, and
+# **the terminal summary was never written**. Measured with a deliberately failing test
+# added: no `FAILED`, no " failed", no " passed", exit 1 -- byte-indistinguishable from an
+# all-green run. An instrument that cannot state its measurement fails toward whichever
+# answer the reader already expects.
+#
+# With `--basetemp` set, pytest uses this folder and never constructs or cleans that root,
+# so the fault cannot reach the summary line. The ruling's reasoning is the part worth
+# keeping: the dead reparse point had already come back once, so an elevated `rmdir` is a
+# repair and not a fix.
+#
+# THIS IS A MEASURED MECHANISM, NOT A REPRODUCTION, AND THE LABEL IS OWED AN UPDATE.
+# It was accepted as such: two runs left the user's `pytest-of-<user>` folder unchanged and
+# `pytest-current` was never recreated. What was NOT shown is a run printing its summary
+# while the poisoned reparse point was present -- it had already been removed by hand before
+# the change landed.
+#
+#   **When the old `pytest-current` folder next reappears, run the suite against it and
+#   replace this paragraph with the result.** That is a standing obligation from §3, and it
+#   is written here rather than only in the register because this is where the claim lives
+#   and a reader checking the claim will be reading this file.
+#
+# I ARGUED AGAINST A REPOSITORY-SIDE WORKAROUND and was overruled, correctly. My objection
+# was to a root `conftest.py` setting `PYTEST_DEBUG_TEMPROOT`, which would have hidden one
+# machine's broken temp directory inside the repository as a permanent silence. This is a
+# different thing: it is declared in plain sight in the project's own configuration, it is
+# reproducible for everyone, and it keeps a run's temporaries beside the project that made
+# them. It silences nothing.
+#
+# The path is relative, so it resolves against the directory pytest is invoked from. The
+# gate command is run from the repository root; a run started elsewhere puts the folder
+# elsewhere, which is untidy and harmless.
+#
+# No `-q`: suite commands don't use it, so every result shows its summary line. A `-q` set
+# here and a second on the command line make `-qq`, which prints no tally at all, and counts
+# were once read from runs that reported no total. Not repeated here.
+addopts = "--basetemp=.pytest-basetemp"

onetrace_console-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

onetrace_console-0.1.0/src/onetrace_console/__init__.py

@@ -0,0 +1,10 @@
+"""The onetrace console: every run in one place.
+
+**The run folder is the unit of truth and this package never computes a verdict.** It
+stores the bytes an emitter wrote, keeps the reports the verifier and the verbs produced
+over them, and reads those reports. If the console and the offline file ever disagree,
+the file is right and the console has a defect.
+"""
+__all__ = ["__version__"]
+
+__version__ = "0.1.0"