vector-mtrl 0.2.0__tar.gz

vector_mtrl-0.2.0/.gitignore

@@ -0,0 +1,243 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+.idea/
+
+### macOS ###
+# General
+.DS_Store
+.AppleDouble
+.LSOverride
+
+# Icon must end with two \r
+Icon
+
+
+# Thumbnails
+._*
+
+# Files that might appear in the root of a volume
+.DocumentRevisions-V100
+.fseventsd
+.Spotlight-V100
+.TemporaryItems
+.Trashes
+.VolumeIcon.icns
+.com.apple.timemachine.donotpresent
+
+# Directories potentially created on remote AFP share
+.AppleDB
+.AppleDesktop
+Network Trash Folder
+Temporary Items
+.apdisk
+
+### macOS Patch ###
+# iCloud generated files
+*.icloud
+
+### Linux ###
+*~
+
+# temporary files which can be created if a process still has a handle open of a deleted file
+.fuse_hidden*
+
+# KDE directory preferences
+.directory
+
+# Linux trash folder which might appear on any partition or disk
+.Trash-*
+
+# .nfs files are created when an open file is removed but is still being accessed
+.nfs*
+
+### Windows ###
+# Windows thumbnail cache files
+Thumbs.db
+Thumbs.db:encryptable
+ehthumbs.db
+ehthumbs_vista.db
+
+# Dump file
+*.stackdump
+
+# Folder config file
+[Dd]esktop.ini
+
+# Recycle Bin used on file shares
+$RECYCLE.BIN/
+
+# Windows Installer files
+*.cab
+*.msi
+*.msix
+*.msm
+*.msp
+
+# Windows shortcuts
+*.lnk
+.pi
+
+# Private local TRIOS corpus, native files, exports, and reports.
+/data/tri-corpus/
+
+# Generated project overview and local test corpora.
+/PROJECT_DIRECTORY_OVERVIEW.md
+/tests/data/mtrl/
+/node_modules/

vector_mtrl-0.2.0/CHANGELOG.md

@@ -0,0 +1,162 @@
+# Changelog
+
+All notable changes to the core distribution are documented in this file. Each private suite
+distribution keeps its own changelog in its own repository. Maintainers keep the versioning, tag and publishing
+contract in the repository file `RELEASE.md`.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and each
+distribution uses pre-1.0 Semantic Versioning: while a distribution is `0.x`, a minor bump may
+break, and every breaking change is named in the release entry.
+
+## [Unreleased]
+
+### Changed
+
+- Prepare `0.2.0` as the first public-core release candidate with the interp and tabular
+  capabilities folded into the core as public extras (`interp`, `tabular`, `excel`), per the
+  2026-10-22 owner decision. The two former suite distributions cease: `vector-mtrl-interp`
+  and `vector-mtrl-tabular` no longer exist, and the repository is a single uv project.
+  Breaking changes: the `mtrl.resample.pchip` and `mtrl.resample.cubic` operations restore
+  as core built-ins, so archives recorded under the suite identifiers
+  `vector-mtrl-interp.resample.pchip` and `vector-mtrl-interp.resample.cubic` cannot resolve
+  or rerun on this version; the suite `register(registry)` seam is gone; the `.xlsx` writer
+  registers at import, so a base install without the `excel` extra raises
+  `MissingOptionalDependencyError` naming `vector-mtrl[excel]` instead of
+  `UnsupportedExportFormatError`, and the `.xlsx` suffix is no longer free for a custom
+  writer; the `vector-mtrl-interp.suite/1` capability string is no longer recorded. The
+  base install stays NumPy, Pydantic, and RFC 8785 canonical JSON only. The source-tree
+  version fallback also names `0.2.0` when installed distribution metadata is absent.
+  Uploads still need separate owner approval, and the public enable switch stays off.
+
+- Cut `0.1.4` as the public-core build-only candidate: remove the README section that named
+  the private suite distributions and the authorised-customer boundary, so the package long
+  description carries no private-suite delivery detail. The source-tree version fallback
+  also names `0.1.4` when installed distribution metadata is absent. Uploads still need
+  separate owner approval, and the public enable switch stays off.
+
+- Cut `0.1.3` as the public-core build-only candidate after the `vector-mtrl-v0.1.2` tag
+  was stranded: the tag was pushed before its preparation commits reached `main`, the
+  pull-request merge then rewrote the commit identities, and the immutable tag protection
+  keeps the tag on the off-main commit. The stranded tag's build-only run stayed
+  upload-disabled and its archives were never reviewed for upload. This entry re-cuts the
+  same hardened content as `0.1.3` from the merged `main` commit, with the source-tree
+  version fallback also naming `0.1.3` when installed distribution metadata is absent.
+  Uploads still need separate owner approval, and the public enable switch stays off.
+
+- Prepare `0.1.2` as the public-core candidate cut from the hardened toolchain. The 2026-10-20
+  eMudhra intermediate-certificate compromise left the previous pins (Node.js `22.15.0`,
+  `uv` `0.12.1`) on vulnerable bundled trust stores, so the repository and workflow pins move
+  to Node.js `22.23.4` and `uv` `0.13.4`, and the release build runs with the patched
+  certificate bundles. Keep the earlier unpublished `0.1.0` and `0.1.1` tags and their
+  reviewed files unchanged. Uploads still need separate owner approval, and the public enable
+  switch stays off. The source-tree version fallback also names `0.1.2` when installed
+  distribution metadata is absent.
+
+- Prepare `0.1.1` as a new candidate for the first public-core release, with cleaned documentation.
+  Keep the earlier unpublished `0.1.0` tag and reviewed files unchanged. Uploads still need
+  separate owner approval, and the public enable switch stays off. The source-tree version
+  fallback also names `0.1.1` when installed distribution metadata is absent.
+
+- Separate the concise public README and three shipped user guides from private suite guidance,
+  maintainer runbooks and dated preparation records. Keep executable documentation coverage and
+  the strict public archive boundary. Existing reviewed release files and tags stay unchanged.
+
+- Earlier preparation moved the core version from `0.0.1` to the unpublished `0.1.0`
+  candidate. The two local suite members update their declared core requirement to
+  `vector-mtrl>=0.1.0,<0.2` under the 0.x minor core range rule; their own versions stay at
+  `0.0.1` until their first own release entries. No date is filed and no upload is claimed:
+  the first upload still needs explicit owner approval, and the public enable switch stays
+  off.
+- Public release preparation now permits only core tags. Uploads require an explicit enable
+  switch. An offline gate rejects legacy licence metadata, private suite dependencies, and
+  non-core archive content. The old six-public-package train workflow is disabled.
+- The core distribution is renamed from `mtrl` to `vector-mtrl` in one change: the root
+  project name, the member dependency strings, the wheel manifest key, the README install
+  commands, and the diagnostic install guidance all name `vector-mtrl`. The import package
+  stays `mtrl`, and the stored identity values keep their spelling: the operation
+  identifiers, the capability strings, the format feature names, and the recorded
+  `implementation_package` values, including the core value `mtrl`.
+
+### Added
+
+- Author disclosure: `Mtrl.attach_environment_record` attaches one passive environment record,
+  `Mtrl.attach_source_bundle` binds one passive source bundle to the exact custom output record,
+  `Mtrl.environment_record` and `Mtrl.source_bundles` inspect the attached values, and
+  `Mtrl.export_source_bundle` writes one committed bundle as three fixed files. Attached material
+  is inert: MTRL records the author's claim and never imports, compiles, or executes it. The
+  value types live in `mtrl.disclosure`, and `EnvironmentRecordError` and `SourceBundleError`
+  join the package-root exports.
+- Two core format features, `mtrl.environment-records/1` and `mtrl.source-bundles/1`, gate
+  archives that carry attachment content.
+- `Mtrl.export_execution_plan`: the replay plan of one committed target as a
+  standalone `mtrl-execution-plan/1` document. The document is code-free, holds
+  recorded facts only, and carries no local registration fact, so it never
+  grants execution approval. The loader bounds bytes and depth and rejects every
+  closed-schema violation.
+- `Mtrl.replay_plan`, `Mtrl.capability_view`, and `Mtrl.rerun`: explicit replay of a committed
+  operation chain. The plan and the capability view are read-only and execute nothing; the rerun
+  resolves each step only through the local registry, commits fresh identities in one revision,
+  and reports the recorded versus fresh canonical digests per step. `ReplayPlanError` and
+  `ReplayIneligibleError` join the package-root exports, and the replay types live under
+  `mtrl.replay`.
+- Release safety before the first train: the core sdist carries a deliberate allowlist (`mtrl/`
+  with its `py.typed` marker, `LICENSE`, `NOTICE`, `README.md`, `CHANGELOG.md`, and the three
+  public guides under `docs/user/`) and no tests, because the
+  root test tree is workspace-coupled; `tests/test_packaging_inventory.py` pins the exact
+  top-level inventory of every workspace sdist; CI rebuilds the core wheel from its extracted
+  sdist in an isolated environment and imports `mtrl` from the installed wheel; and
+  `scripts/release_core_range_gate.py` fails closed before any upload when a suite tag's
+  declared core range does not resolve from PyPI.
+
+### Removed
+
+- The `vector-mtrl-spa` and `vector-mtrl-trios` suites leave this workspace. They now live in
+  the private `vectorlabsonline/vector-mtrl-connectors` repository. The development group, the
+  workspace sources, the lockfile, and the CI member steps and wheel rows no longer select them.
+  The core `Mtrl.load_spa` and `Mtrl.load_tri` facades stay and fail closed without the suite.
+- The `vector-mtrl-viz` suite leaves this workspace. It now lives in the private
+  `vectorlabsonline/vector-mtrl-viz` repository. The development group, the workspace
+  sources, and the lockfile no longer select it.
+- The `spa`, `interp`, `tabular`, and `excel` core extras are removed. Development requirements
+  select the private suite members of this workspace; users install authorised suite wheels
+  from the member repositories. Superseded on 2026-10-22: the fold restores the `interp`,
+  `tabular`, and `excel` core extras, and the development group selects them.
+- Legacy archive format support, including the `upgrade_legacy` path and the legacy alias map.
+  The single archive format is current-format-only, and an unknown format fails closed.
+- The `mtrl.ftir.excise-co2-window` and `mtrl.ftir.baseline-airpls` operations and the `ftir`
+  extra.
+- The `mtrl.resample.pchip` and `mtrl.resample.cubic` identifiers. The operations move to the
+  `vector-mtrl-interp` suite under new `vector-mtrl-interp.resample.*` identifiers.
+  Superseded on 2026-10-22: the fold returns both operations to the core as built-ins under
+  their historical identifiers.
+
+### Changed
+
+- `MaterialData` accepts `units=None` as an explicit no-unit declaration: the values carry no unit
+  contract, construction stores an empty units mapping, and no operation invents a unit for
+  undeclared values. Passing `None` raised a pydantic validation error before.
+- The `ReplayPlanError` message for a rerun step with no local implementation now states the
+  registry step as well: the registry in use must have registered the operations of the named
+  package, and installing the package alone registers nothing.
+- Docstrings: `Mtrl.aggregate` reaches the house standard with Args, Returns, and Raises;
+  `Mtrl.save` documents the forced `.mtrl` suffix; and `Mtrl.load` states that the default registry
+  is a fresh built-in registry that holds no suite operations.
+- The core distribution registers `mtrl.environment-records/1` and `mtrl.source-bundles/1` at
+  import, so the supported feature set is no longer empty by default.
+  `clear_supported_features()` still removes every feature; restore the core pair with
+  `register_supported_features(CORE_FORMAT_FEATURES)`.
+- The operations layout is unified under `mtrl/operations/`.
+- Instrument ingestion moves to the suites: the SPA connector to `vector-mtrl-spa` and the native
+  TRIOS connector to `vector-mtrl-trios`.
+- The pandas frame builders, the Excel writer, and the internal table evaluation move to the
+  `vector-mtrl-tabular` suite. Superseded on 2026-10-22: the fold returns them to the core
+  through its public `tabular` and `excel` extras.
+- The demo moves to the `vector-mtrl-viz` suite as its first consumer.
+
+## [0.0.1] - 2026-10-10
+
+Baseline record of the core distribution. The code at this version is the Stage 0-1 modular rework
+branch, `feature/modular-stage0`. It records the approved modular direction and delivers the
+format-feature gate, the frozen manifest, namespace reservation at registration, derived capability
+strings, descriptor-driven validation, and the stdlib CSV writer. This version was not published;
+wheels are CI artefacts only. History before this baseline is not backfilled.