release-v0.7.3

[sbusch305]

Two-Key 0.7.3

Beta (pre-1.0). The first release of new code since 0.7.0: PyPI's 0.7.1 and 0.7.2 were the 0.7.0 code, repackaged.

Install
pip install "two-key[yaml]==0.7.3"
pip install "two-key[mcp]==0.7.3" # for the MCP proxy

What's new

• two-key setup writes a whole deployment (principal key, constitution, judges, proxy.yaml, ledger) from answers or a file, checks it before it is in place, and records it.
• two-key config set and undo change one setting at a time. The whole set must still pass config check, a weaker change needs a typed yes, a signed setting needs the principal key, and every change is a config_changed ledger entry with no values. config get, show and check read a config without starting anything. See docs/SETUP.md.
• The principal key can be encrypted with a passphrase; the proxy reads it from an owner-only keys.passphrase_file.
• A signed serial in the constitution. Once a ledger has run one, it refuses an older constitution, a reused serial, or none, so nobody can quietly go back to older rules. Two proxies started at once on one ledger cannot both run one serial.
• The start-up checks now cover the upstream server's own files behind a launcher such as sudo, plus upstream.check_paths for the rest (Start-up checks do not cover the upstream server's files when upstream.command goes through sudo #13).
• Shared ledgers are sturdier: each write and the checkpoint that signs it happen in one hold of the lock, and the SIEM copy of an entry another proxy wrote is marked replay.
• Only the tool's id is required in a tool spec: irreversible and data_class_floor default to true and classified, the strict side. Existing constitutions sign to the same bytes.
• docs/SETTINGS.md lists every setting, generated from the code. CI covers Python 3.10 to 3.14 on Linux, macOS and Windows, with hash-pinned installs.
• Live-tested by GrokBot across runs 9 to 9t (175 cases). Every Two-Key finding is fixed; the last three regression rounds found none.

Upgrading from 0.7.0, 0.7.1 or 0.7.2

• Everything loads unchanged and nothing needs re-signing.
• Read the proxy's start-up output: it may now name the upstream server's files, or warn upstream_paths_unchecked when a launcher such as sudo or npx hides them (under high_assurance it refuses). Give the program as an absolute path or list its folder in upstream.check_paths.
• To turn on rollback protection, add "serial: 1" to your rules file and sign it again; count up by one for each new constitution.
• config check now fails if the monitored agent's credential variable is unset.
• With two proxies on one ledger, dedupe SIEM events on entry_hash.
• A tool spec may now leave out irreversible and data_class_floor; left out, they are true and classified, so a reversible or lower-class tool should still say so.

Full details: CHANGES.md, "Release v0.7.3" and "Upgrading from 0.7.0".

---

This discussion was created from the release release-v0.7.3.