weightsdb 0.2.0__tar.gz

weightsdb-0.2.0/.editorconfig

@@ -0,0 +1,23 @@
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+indent_style = space
+indent_size = 4
+
+[*.py]
+indent_size = 4
+max_line_length = 100
+
+[*.{toml,yml,yaml,json}]
+indent_size = 2
+
+[*.md]
+trim_trailing_whitespace = false
+max_line_length = off
+
+[Makefile]
+indent_style = tab

weightsdb-0.2.0/.github/workflows/ci.yml

@@ -0,0 +1,164 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  format:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - run: pip install ruff
+      - run: ruff format --check .
+
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - run: pip install ruff
+      - run: ruff check .
+
+  types:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - run: pip install --require-hashes -r requirements/ci.lock
+      - run: pip install . --no-deps
+      - run: mypy src tests
+
+  boundaries:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - run: pip install --require-hashes -r requirements/ci.lock
+      - run: pip install . --no-deps
+      - run: lint-imports
+
+  tests:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "${{ matrix.python-version }}" }
+      - run: pip install --require-hashes -r requirements/ci.lock
+      - run: pip install . --no-deps
+      - run: pytest -m "not live and not performance" --cov --cov-report=xml
+
+  tests-314-early-warning:
+    runs-on: ubuntu-latest
+    continue-on-error: true
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.14" }
+      # Deliberately unpinned: ci.lock is resolved on 3.13, and pinning a version that has no
+      # 3.14 wheels would defeat the purpose of an early warning.
+      - run: pip install -e ".[dev]"
+      - run: pytest -m "not live and not performance"
+
+  db-matrix:
+    name: tests (PostgreSQL)
+    runs-on: ubuntu-latest
+    services:
+      postgres:
+        image: postgres:16
+        # Credentials and database name match `weightsdb.testing`'s documented default URL, so the
+        # service this job starts is the one the package looks for.
+        env:
+          POSTGRES_USER: weightsdb
+          POSTGRES_PASSWORD: weightsdb
+          POSTGRES_DB: weightsdb_test
+        ports: ["5432:5432"]
+        options: >-
+          --health-cmd "pg_isready -U weightsdb -d weightsdb_test" --health-interval 5s --health-timeout 5s --health-retries 10
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - run: pip install --require-hashes -r requirements/ci.lock
+      - run: pip install . --no-deps
+      - run: pytest -m "not live and not performance" tests/integration
+        env:
+          WEIGHTSDB_REQUIRE_POSTGRES: "1"
+          # `temporary_postgres` reads WEIGHTSDB_POSTGRES_URL, not DATABASE_URL. Set explicitly
+          # rather than relying on the default, so the job states which server it is testing.
+          WEIGHTSDB_POSTGRES_URL: postgresql+psycopg://weightsdb:weightsdb@localhost:5432/weightsdb_test
+
+  coverage:
+    needs: [tests]
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - run: pip install --require-hashes -r requirements/ci.lock
+      - run: pip install . --no-deps
+      - run: pytest -m "not live and not performance" --cov --cov-report=term-missing --cov-fail-under=95
+
+  contracts:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - run: pip install --require-hashes -r requirements/ci.lock
+      - run: pip install . --no-deps
+      - run: pytest -m contract
+
+  security:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        # gitleaks scans *history*, and `actions/checkout` fetches a single commit by default.
+        # For a push it is handed `<first-pushed>^..<last-pushed>`, so the parent of the first
+        # pushed commit has to be in the object store; in a depth-1 clone it is not, and git
+        # answers "unknown revision", which the action reports as exit code 1. It fails the same
+        # way whether or not a secret exists, so a green run would not have meant anything either.
+        with: { fetch-depth: 0 }
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - run: pip install pip-audit
+      # Audit the locked sets, not the job's own environment: a bare `pip-audit` here would
+      # inspect an environment containing only pip-audit itself (Security Standards §11).
+      - run: pip-audit --require-hashes -r requirements/ci.lock
+      - run: pip-audit --require-hashes -r requirements/release.lock
+      - uses: gitleaks/gitleaks-action@v2
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - run: pip install --require-hashes -r requirements/release.lock
+      - run: python -m build --no-isolation
+      - run: twine check dist/*
+      - uses: actions/upload-artifact@v4
+        with: { name: dist, path: dist/ }
+
+  install-check:
+    needs: [build]
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - uses: actions/download-artifact@v4
+        with: { name: dist, path: dist/ }
+      - run: pip install dist/*.whl
+      - run: python -c "import weightsdb"

weightsdb-0.2.0/.github/workflows/release.yml

@@ -0,0 +1,57 @@
+name: Release
+
+on:
+  push:
+    tags: ["v*.*.*"]
+  workflow_dispatch:   # manual TestPyPI dry run; see publish-testpypi below
+
+permissions:
+  id-token: write   # required for PyPI Trusted Publishing
+  contents: write   # required to create the GitHub release
+
+jobs:
+  release:
+    # Tag pushes only. Without this, clicking "Run workflow" for the TestPyPI dry run below would
+    # also fire this job and publish to real PyPI — the exact opposite of a dry run.
+    if: github.event_name == 'push'
+    runs-on: ubuntu-latest
+    environment: pypi   # must match the Environment name set on the PyPI trusted publisher
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      # Byte-for-byte the dry run's build chain below. A real release that resolved `build` and
+      # `hatchling` fresh from PyPI would not be the artifact the dry run proved.
+      - run: pip install --require-hashes -r requirements/release.lock
+      - run: python -m build --no-isolation
+      - run: twine check dist/*
+      - run: pip install "dist/$(ls dist | grep .whl)[dev]"
+      - run: pytest -m "not live and not performance"
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+      - name: Create GitHub release
+        uses: softprops/action-gh-release@v2
+        with:
+          generate_release_notes: true
+          files: dist/*
+
+  publish-testpypi:
+    # Manual only, via Actions -> Release -> Run workflow. Packaging and Release Standards §6
+    # requires a successful TestPyPI publish ahead of a package's first real release; 0.2.0 is
+    # this package's first published version, so run this once before tagging v0.2.0. Later
+    # releases may skip it, or use it again as a dry run.
+    if: github.event_name == 'workflow_dispatch'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.12" }
+      - run: pip install --require-hashes -r requirements/release.lock
+      - run: python -m build --no-isolation
+      - run: twine check dist/*
+      - run: pip install "dist/$(ls dist | grep .whl)[dev]"
+      - run: pytest -m "not live and not performance"
+      - name: Publish to TestPyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          repository-url: https://test.pypi.org/legacy/

weightsdb-0.2.0/.gitignore

@@ -0,0 +1,100 @@
+# ---- Python ----
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# ---- Packaging / build backends ----
+pip-wheel-metadata/
+share/python-wheels/
+
+# ---- Testing / coverage ----
+.pytest_cache/
+.cache
+.coverage
+.coverage.*
+coverage.xml
+*.cover
+*.py,cover
+htmlcov/
+nosetests.xml
+.hypothesis/
+
+# ---- Type checking / linting ----
+.mypy_cache/
+.dmypy.json
+dmypy.json
+.ruff_cache/
+.pytype/
+
+# ---- Virtual environments ----
+.venv/
+venv/
+ENV/
+env/
+env.bak/
+venv.bak/
+.python-version
+
+# ---- Distribution / dependency locking ----
+# requirements/*.lock is deliberately NOT ignored. The lock files are committed
+# inputs: CI and release jobs install from them with --require-hashes (Packaging
+# and Release Standards §4, Security Standards §11), so an ignored lock file
+# means a checkout that cannot build.
+
+# ---- Editors / OS ----
+.vscode/
+.idea/
+*.swp
+*.swo
+.DS_Store
+Thumbs.db
+
+# ---- Suite runtime state (this component's local data) ----
+# The application writes to XDG paths at runtime (~/.config, ~/.local/share,
+# ~/.local/state per Master Architecture §1.2), never inside the repository.
+# These entries only guard against a developer pointing XDG_* at the repo
+# during local testing.
+.local/
+.config/
+*.sqlite3
+*.sqlite3-journal
+*.sqlite3-wal
+*.sqlite3-shm
+/data/
+/logs/
+/backups/
+/artifacts/
+/exports/
+
+# ---- Secrets ----
+# Per Security Standards §8: secrets are never committed. Config files may
+# only name where a secret comes from (*_env / *_file), never the value.
+.env
+.env.*
+*.key
+*.pem
+secrets.toml
+
+# ---- Node-free JS assets (MirrorWall consumers may still use a local tool) ----
+node_modules/
+
+# ---- Build artifacts from docs generation ----
+docs/api/openapi-v1.json.tmp

weightsdb-0.2.0/.importlinter

@@ -0,0 +1,21 @@
+[importlinter]
+root_package = weightsdb
+include_external_packages = True
+
+[importlinter:contract:no-application-imports]
+name = WeightsDB must not import applications
+type = forbidden
+source_modules = weightsdb
+forbidden_modules =
+    freeweight
+    loadcoach
+    ideapress
+
+[importlinter:contract:no-sibling-packages]
+name = WeightsDB must not import sibling capability packages
+type = forbidden
+source_modules = weightsdb
+forbidden_modules =
+    modelrack
+    sweatmeter
+    mirrorwall

weightsdb-0.2.0/.pre-commit-config.yaml

@@ -0,0 +1,22 @@
+repos:
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.6.9
+    hooks:
+      - id: ruff
+        args: [--fix]
+      - id: ruff-format
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v4.6.0
+    hooks:
+      - id: trailing-whitespace
+      - id: end-of-file-fixer
+      - id: check-toml
+      - id: check-json
+      - id: check-added-large-files
+      - id: check-merge-conflict
+      - id: mixed-line-ending
+        args: [--fix=lf]
+  - repo: https://github.com/gitleaks/gitleaks
+    rev: v8.18.4
+    hooks:
+      - id: gitleaks

weightsdb-0.2.0/CHANGELOG.md

@@ -0,0 +1,75 @@
+# Changelog
+
+All notable changes to `weightsdb` are documented here.
+Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versioning follows
+[Semantic Versioning](https://semver.org/), pre-1.0 per
+packaging and release standards §3.
+
+## [Unreleased]
+
+### Fixed
+- **Coverage fell below the 95 % floor on Python 3.12 (94.89 %).** The uncovered lines were real
+  gaps, not measurement noise: `upsert`'s documented refusal of a third dialect, the `StorageBusy`
+  translation on a *read-only* `BEGIN`, `temporary_postgres`'s `WEIGHTSDB_REQUIRE_POSTGRES=1`
+  failure path, longest-prefix mount selection against an unsorted mount table, and two backups
+  sharing an mtime. Each now has a test; the floor is met on 3.12, 3.13 and 3.14 with margin.
+
+## [0.2.0] — 2026-08-29
+
+### Added
+- Repository scaffold generated from the suite's development plan (no functional code yet).
+- Phase 1: `create_engine_for`, `session_factory`/`session_scope`/`transaction`, `UtcDateTime`,
+  `PortableJSON`, `ulid_primary_key`, `measurement_columns`, `upsert`, the `DatabaseError` hierarchy,
+  `redact_url`, and `weightsdb.testing.temporary_sqlite`/`temporary_postgres` — extracted from
+  FreeWeight's `infrastructure.db` (ADR-0011).
+- Phase 2: `MigrationRunner` (upgrade/downgrade/stamp/check_parity with automatic pre-migration
+  backup and SQLite restore-on-failure), `backup`/`restore`/`integrity_check` and friends, and
+  `weightsdb.testing.migration_harness`.
+- Phase 3: `database_health()` (dialect/version, revision vs head, journal mode, size, free space,
+  last backup age, integrity, network-filesystem warning, one `status`/`degraded_reasons` verdict),
+  `is_network_filesystem()`, the `py.typed` marker, `docs/quickstart.md` and
+  `docs/adoption-checklist.md` for FreeWeight Phase 12.
+
+### Fixed
+- SQLite lock contention beyond `busy_timeout` now raises the typed `StorageBusy` instead of a raw
+  `sqlalchemy.exc.OperationalError` — a gap in the code this package was extracted from, invisible
+  with one consumer and no test for it.
+- **`psycopg[binary]` is now part of the `dev` extra.** Seventeen tests assert dialect-specific
+  behaviour by building a `postgresql://` engine — no server involved — which SQLAlchemy cannot do
+  without an importable DBAPI. Every environment that installed `[dev]` alone failed them with
+  `ModuleNotFoundError` and landed coverage at 88 % against a 95 % floor; the local `.venv` hid it
+  by having been created with `[dev,postgres]`. The optional `postgres` extra is unchanged, and is
+  still what a consumer installs to talk to a real server.
+- **The `db-matrix` CI job read the wrong environment variable.** It set `DATABASE_URL`, which
+  nothing in this package reads; `weightsdb.testing.temporary_postgres` reads
+  `WEIGHTSDB_POSTGRES_URL` and otherwise falls back to its own default. With
+  `WEIGHTSDB_REQUIRE_POSTGRES=1` the fallback is a hard failure rather than a skip, so the job had
+  never exercised PostgreSQL at all. The service container's user, password and database now match
+  the documented default URL, and the job sets `WEIGHTSDB_POSTGRES_URL` explicitly rather than
+  relying on that default.
+- **The PostgreSQL round-trip no longer fails on client/server version skew.** `pg_restore` exits 1
+  for warnings unrelated to the data — a client newer than the server emits
+  `SET transaction_timeout = 0`, which an older server rejects and reports as "errors ignored on
+  restore" — so the test asserted an exit code where its actual claim is that the rows come back.
+  It now checks the restored rows and attaches `pg_restore`'s stderr when they are wrong. A missing
+  `pg_dump` skips the test the way a missing `pg_restore` already did, instead of failing inside
+  `backup()`.
+- **`test_restore_reports_a_backup_it_cannot_open` skips when running as root.** `chmod 000` does
+  not make a file unreadable to root, so the open succeeds and the corruption branch answers
+  instead — a failure that says nothing about the code. CI runs as an ordinary user; a container
+  run as root no longer reports it as a defect.
+- The `dev` extra moves to `pytest>=9.0.3,<10`, matching BaseAiCore, SetSpec, ModelRack and
+  SweatMeter: PYSEC-2026-1845 affects pytest through 9.0.2 and failed the security job.
+- **The backup tests' table seed was not dialect-portable.** `INSERT INTO t (name) …` relies on
+  SQLite treating `INTEGER PRIMARY KEY` as a rowid alias; PostgreSQL rejects the row with a
+  NOT NULL violation. The id is now supplied explicitly, so the round-trip test can actually run
+  on the dialect it names.
+
+### Changed
+- CI installs from committed, hash-verified lockfiles (`requirements/ci.lock`,
+  `requirements/release.lock`) rather than an editable checkout, per Packaging Standards §4;
+  `pip-audit` audits those locks instead of an empty environment; `release.yml` gains the
+  `pypi` deployment environment, the manual TestPyPI dry run required before a first release, and
+  a build chain pinned byte-for-byte to the one the dry run proves. `[tool.coverage.run] source`
+  now names the importable package rather than `src/weightsdb`, because a non-editable install
+  reports 0 % against a path-based source.

weightsdb-0.2.0/CONTRIBUTING.md

@@ -0,0 +1,50 @@
+# Contributing to WeightsDB
+
+This repository is one component of the Local AI Suite. Before changing anything, read
+`docs/packages/weightsdb/spec.md` and the current
+phase in `development-plan.md` — both are in this repository's `docs/` folder, copied from the suite's
+central documentation set so this repository can be worked on independently.
+
+## Development setup
+
+```bash
+python -m venv .venv
+source .venv/bin/activate
+pip install -e ".[dev]"
+pre-commit install
+```
+
+## Required reading, in order
+
+1. This component's spec — purpose, scope, non-goals, contracts.
+2. `development-plan.md` in the same folder — the phase you are implementing, its acceptance criteria and its tests.
+
+## Rules that apply to every change here
+
+* Follow the architecture's dependency direction.
+  This repository's `.importlinter` enforces it in CI; do not weaken that file to make an import work.
+* No business logic in a route handler or CLI command body — both call one service method and render
+.
+* An unavailable measurement is `Unsupported`, never zero, never `None` used as a substitute
+.
+* Prompts are versioned JSON records, not Python string literals.
+* Every phase's acceptance criteria in `development-plan.md` must be demonstrable, not merely
+  test-covered — the plan states what to run and what a person should see.
+
+## Before opening a pull request
+
+```bash
+ruff format --check .
+ruff check .
+mypy src tests
+lint-imports
+pytest -m "not live and not performance"
+```
+
+All of the above run in CI (`.github/workflows/ci.yml`); a red CI run blocks merge.
+
+## Commit style
+
+Conventional Commits (`feat:`, `fix:`, `docs:`, `refactor:`, `test:`, `chore:`, `perf:`, `build:`,
+`ci:`), with `!` or a `BREAKING CHANGE:` footer for breaking changes. Update `CHANGELOG.md` under
+`## [Unreleased]` for any user-visible change.