proximo (0.20.0-1) UNRELEASED; urgency=medium

  * Track upstream 0.20.0 (minor — the receipts release: every safety claim is now
    paired with a command that proves it. No tool-count change (still 365). Adds
    VERIFY.md (each claim + its runnable check), THREAT_MODEL.md (assets/boundaries/
    adversaries/residuals), a CycloneDX SBOM for the published wheel attached to the
    GitHub release, an OpenSSF Scorecard badge, and scripts/mutation_smoke.py (4/4
    trust-core tamper-detection mutants killed). No packaging changes from 0.19.1-1 —
    same dh-virtualenv build, man page, and autopkgtest. Not distributed; build-your-own
    from debian/.

 -- John Broadway <271895126+john-broadway@users.noreply.github.com>  Fri, 10 Jul 2026 15:00:00 +0000

proximo (0.19.1-1) UNRELEASED; urgency=medium

  * Track upstream 0.19.1 (patch — self-audit release: 23 findings from a multi-agent
    audit of 0.19.0, all fixed, no tool-count change (still 365). Headline: _check_volid
    accepts PBS archive volids (RFC3339 snapshot times carry colons) so restore/prune
    from PBS work again; the freshness fence parses sub-daily schedules and degrades a
    stale verdict to unknown on an unreadable storage; pbs_realm_sync uses the hyphenated
    PBS field names; prune-job runs are rated HIGH; the PDM plane is honestly labeled
    reads + governed control. No packaging changes from 0.19.0-1 — same dh-virtualenv
    build, man page, and autopkgtest. Not distributed; build-your-own from debian/.

 -- John Broadway <271895126+john-broadway@users.noreply.github.com>  Fri, 10 Jul 2026 06:18:14 +0000

proximo (0.19.0-1) UNRELEASED; urgency=medium

  * Track upstream 0.19.0 (minor — new tool pve_backup_freshness, the backup-freshness
    fence: walks actual backup archives per guest against what enabled jobs promise;
    task-OK is never treated as evidence a backup exists. Includes the token-sight guard
    (PVE hides backup volumes from tokens lacking VM.Backup + Datastore.AllocateSpace,
    200 + empty) and guests_visible population honesty (the guest list itself is
    permission-filtered). +1 tool -> 365. No packaging changes from 0.18.1-1 — same
    dh-virtualenv build, man page, and autopkgtest. Not distributed; build-your-own
    from debian/.

 -- John Broadway <271895126+john-broadway@users.noreply.github.com>  Thu, 09 Jul 2026 23:53:28 +0000

proximo (0.18.1-1) UNRELEASED; urgency=medium

  * Track upstream 0.18.1 (patch — the anonymous door is now a plain text box; one-click
    VS Code/Cursor install deeplinks that prompt for the token PATH, never the secret;
    field-hardened tool-description caveats for pve_tasks_list/pve_backup_list; copy-gate
    and Cursor-deeplink fixes). Docs + copy + tool-description only — no new tools, no API
    change. No packaging changes from 0.18.0-1 — same dh-virtualenv build, man page, and
    autopkgtest. Not distributed; build-your-own from debian/.

 -- John Broadway <271895126+john-broadway@users.noreply.github.com>  Thu, 09 Jul 2026 11:00:25 -0500

proximo (0.18.0-1) UNRELEASED; urgency=medium

  * Track upstream 0.18.0 (the Open Door — AGENTS.md agent front door, the public Agent
    Guestbook, and the print-only `proximo hello` subcommand; no telemetry, invite-only,
    never receives). No packaging changes from 0.17.0-1 — same dh-virtualenv build, man
    page, and autopkgtest. Not distributed; build-your-own from debian/.

 -- John Broadway <271895126+john-broadway@users.noreply.github.com>  Tue, 07 Jul 2026 00:50:00 -0500

proximo (0.17.0-1) UNRELEASED; urgency=medium

  * Track upstream 0.17.0 (PDM fleet control — governed guest lifecycle through the
    Datacenter Manager proxy, incl. live-proven cross-remote datacenter-to-datacenter
    migrate; the `proximo mint` onboarding-recipe subcommand; multi-target + typed-API
    fixes). No packaging changes from 0.16.0-1 — same dh-virtualenv build, man page, and
    autopkgtest. Not distributed; build-your-own from debian/.

 -- John Broadway <271895126+john-broadway@users.noreply.github.com>  Mon, 06 Jul 2026 15:51:04 -0500

proximo (0.16.0-1) UNRELEASED; urgency=medium

  * Track upstream 0.16.0 (five safe-runbook MCP prompts; live-proven online
    live-migration + softdog HA fencing; storage 'shared' fix). No packaging
    changes from 0.15.0-1 — same dh-virtualenv build, man page, and autopkgtest.
    Not distributed; build-your-own from debian/.

 -- John Broadway <271895126+john-broadway@users.noreply.github.com>  Sun, 05 Jul 2026 17:02:08 -0500

proximo (0.15.0-1) UNRELEASED; urgency=medium

  * Track upstream 0.15.0 (cert-fingerprint pinning across all four Proxmox
    surfaces). No packaging changes from 0.14.1-1 — same dh-virtualenv build,
    man page, and autopkgtest. Not distributed; build-your-own from debian/.

 -- John Broadway <271895126+john-broadway@users.noreply.github.com>  Sat, 04 Jul 2026 14:29:06 -0500

proximo (0.14.1-1) UNRELEASED; urgency=medium

  * First working build: the dh-virtualenv step landed. debian/rules now
    drives `dh $@ --with python-virtualenv --buildsystem=pybuild` with an
    override_dh_virtualenv calling `dh_virtualenv --builtin-venv
    --python=/usr/bin/python3` -- this bundles a private venv at
    /opt/venvs/proximo (via `pip install .`, build-isolated so pip also
    fetches the hatchling backend) carrying the mcp and httpx runtime deps
    that Debian doesn't package. debian/control's Depends dropped the
    ${python3:Depends} substvar (no dh-python addon runs now) in favor of
    a plain `python3 (>= 3.12)` dependency, and gained
    Build-Depends: dh-virtualenv, python3-venv.
  * debian/proximo.links symlinks /usr/bin/proximo -> the venv's bundled
    `proximo` console script (the MCP stdio entry point).
  * Fixed two build-time gotchas specific to `--builtin-venv`, both
    verified by extracting the built .deb and grepping for leak shapes:
    dh-virtualenv's own fix_activate_path() only matches the classic
    `virtualenv` tool's activate-script format, so with `--builtin-venv`
    the build-tree's absolute path (pyvenv.cfg, bin/activate,
    direct_url.json, every .pyc's co_filename) silently leaked through
    unfixed; override_dh_virtualenv now sed-replaces it to the final
    /opt/venvs/proximo path and strips the .pyc caches (recompiled
    lazily, harmlessly, on first import) and direct_url.json by hand.
  * Architecture: all -> any. The venv bundles arch-specific compiled
    wheels (pydantic-core, rpds-py, cryptography, cffi); shipping them
    under Architecture: all silently skipped dh_strip/dh_shlibdeps
    (debhelper only runs those for arch-dependent packages), so the first
    `all` build had unstripped binaries and no libc6 dependency -- lintian
    caught both. `any` fixes both and gained ${shlibs:Depends} in Depends.
  * debian/proximo.postrm added: since we ship without .pyc caches,
    Python recompiles them at runtime into untracked __pycache__ dirs;
    without a cleanup hook `dpkg -r`/`apt remove` warned "directory not
    empty" and left /opt/venvs/proximo behind. Now unconditionally
    removed on remove/purge. Verified with a real install -> `proximo
    doctor` -> remove cycle: no leftover files, no dpkg record.
  * debian/proximo.lintian-overrides added for three tags that are
    expected on *any* dh-virtualenv package, not defects here: files
    under /opt, console-scripts shebanging to the venv's bare `python`,
    and two non-executable files vendored inside pip itself. Also
    dropped pip's own console-script wrappers (bin/pip, bin/pip3,
    bin/pip3.*) from the shipped venv -- nobody should be installing into
    this frozen production venv at runtime, and it silenced three
    wrong-path-for-interpreter tags. Full `lintian` pass is now clean
    except no-manual-page and three debug-file-with-no-debug-symbols
    warnings on the auto-generated -dbgsym package (the bundled
    manylinux wheels are pre-stripped, no DWARF info to extract) -- both
    documented in debian/README.Debian "still rough", neither a defect.
  * Version tracks upstream (0.14.1) now that the package actually builds
    and installs; still UNRELEASED/no real distribution/urgency is a
    placeholder -- this is a packaging milestone, not a Debian archive
    upload, and there's been no separate audit of this artifact for
    publication (see debian/README.Debian "still rough").
  * The A2A extra (a2a-sdk, uvicorn, starlette, cryptography) is
    deliberately NOT bundled into the venv -- matches upstream's opt-in
    design; only the base mcp+httpx surface ships. Anyone wanting
    proximo-a2a installs the extra by hand into the venv.
  * Kept the prior scaffold entry below verbatim for the historical record
    of what was blocking (now resolved) and what stays a permanent design
    decision (the on-demand stdio transport, not a blocker).

 -- John Broadway <271895126+john-broadway@users.noreply.github.com>  Sat, 04 Jul 2026 00:00:00 +0000

proximo (0.1.0) UNRELEASED; urgency=medium

  * Initial packaging scaffold for the foundation release ("Spaniard").
  * Two backends (REST API + ssh->pct), full MCP tool surface, audit log,
    confirm-gated mutations, fail-closed CTID allowlist.
  * STATUS (still UNRELEASED, still a scaffold, not a working build): this
    entry is intentionally pinned at 0.1.0 while upstream proximo has moved
    on to 0.12.0+ on PyPI/GitHub/GHCR. The Debian package version tracks
    the packaging's own readiness, not upstream's release cadence -- it
    will be bumped (and a real distribution + urgency set) only once
    `dpkg-buildpackage` actually produces an installable .deb, not per
    upstream tag.
  * Two blockers tracked (see debian/README.Debian for the full writeup):
    - Python runtime deps (mcp, httpx) are not packaged for Debian.
      DECIDED direction: bundle a self-contained venv via dh-virtualenv
      (sovereign, no host clutter) so debian/control's Depends can stay
      stdlib+ssh-only. Not yet implemented -- debian/rules still drives
      plain dh/pybuild, which will fail to resolve those imports at build
      or run time until the dh-virtualenv step is written.
    - Transport is DECIDED (stdio, on-demand, no always-on daemon; see the
      optional packaging/optional-daemon-mode.service.example for anyone
      who wants a daemon anyway) -- this one is resolved, not a blocker.
  * Net: do not build/upload this package expecting a working .deb yet --
    it is scaffold-only until the dh-virtualenv bundling lands.

 -- John Broadway <271895126+john-broadway@users.noreply.github.com>  Wed, 01 Jul 2026 12:00:00 +0000
