legends-empire v0.3.2

Existing vaults can now perform new native writes when they contain validated, already rolled-back transaction history from another operating system. The terminal history and backups remain unchanged. Incomplete foreign transactions and retries of the original foreign operation still require their original backend.

This fixes native Windows knowledge attachment in vaults with older POSIX rollback history, including the Legends Coolify operations library. It also preserves native retry behavior by closing a validated backup handle before removing its old operation directory.

Validation: all 13 hosted Windows/macOS/Linux Python 3.11–3.14 and reproducibility jobs passed. Focused regressions and full suites passed on actual Linux and macOS hosts; native Windows transaction, filesystem, checkpoint and attachment tests passed. Adversarial tests cover malformed journals, missing/corrupt backups, incomplete history and forbidden foreign replay. The public archive is audited and reproducible.

Existing platform constraints remain: native Windows writes require local fixed NTFS; legacy Bash helpers require POSIX. Windows process-interruption recovery does not promise POSIX directory-fsync power-loss durability. See docs/windows-wsl.md.

legends-empire 0.3.1: native Windows transactions

Native Windows vault transactions now use retained NT handles, protected private ACLs, file identity checks and process locks on local fixed NTFS. Knowledge attachment, capture, reviewed writes, recovery and Git checkpoints can run with native Python. Linux and macOS retain their POSIX backend.

Completed foreign-platform transaction history remains readable; unfinished operations must be recovered using their original backend. A separate POSIX read-race fix detects same-size rewrites with retained timestamps.

Validation includes native fleet runs on Windows, Linux and macOS, hosted Python 3.11–3.14 matrices, process interruption/recovery, cross-process locking and independent Windows filesystem review. The release ZIP is audited for public packaging and reproducibility.

Scope: native Windows refuses network/non-NTFS/reparse paths and unsupported metadata. It preserves supported owner/group/DACL information but does not promise POSIX directory-fsync durability after power loss. Legacy Bash helpers remain POSIX-only. See docs/windows-wsl.md for exact constraints.

legends-empire v0.3.0

Optional Home-ready shared Empire root

Prepare one canonical business and project structure while retaining standalone Empire. Add an independently authorized AI Marketing Hub Home v0.5.2 headless capability layer through inspected, hash-approved transactions, then explicitly compose entry instructions and bind the shared root.

• Original project/company/brand scaffolds preserve unknown facts and whole-life work.
• Pinned source inventory, conflict refusal, bounded recovery, native validation with an explicit trusted interpreter, and nondestructive detach.
• Qualified native instructions, text examples and first-user support routes; no Obsidian plugin/settings installation.
• Public module contains compatibility metadata and original adapter code, not licensed Home source. Home remains optional and separately obtained.

Verified: full platform suites before final support-path delta; final 30 targeted tests; independently reviewed 111 first-user links with zero missing; native task/context/reuse checks. Reproducible public artifact audited with 263 payload files.

Commit: 2855997
Artifact SHA256: 2834cc3c89e8b1aeb6b86cb1d4445e0ad8ed6403fc7c1b441a0a11e63bdb909c

Native Home dependencies are separate. Installation is headless, not complete desktop setup, and does not establish marketing delivery quality or authorize external actions.

legends-empire 0.2.4: verified research evidence intake

Verify client-scoped research evidence from legends-dataforseo and legends-firecrawl before bringing it into an Empire vault.

• Adds offline, read-only research-evidence verify and plan commands for both producer contracts.
• Checks complete response and manifest integrity, available intake-note hashes, provider state consistency and explicitly selected workspace.
• Produces a bounded intake plan for the existing capture and transaction workflow. It does not automatically copy files or promote source contents to accepted findings.
• Updates the shipped stewardship reference pack with the cross-module evidence workflow, preserving user-owned notes and detecting modified references during updates.
• Documents Windows verification/planning support, existing POSIX transaction requirements and the 64 MiB response intake limit.

Validation: full hermetic make test, final extracted-package verification, 12 evidence tests, 19 knowledge-pack tests and product contracts passed. A separate 19-call rehearsal captured both producers' packages, verified six immutable byte-identical sources, repeated capture without duplicates and wrote a reviewed note citing those sources. An 18-case adversarial matrix found no remaining producer/Empire discrepancy.

Hashes establish integrity, not factual truth. Freshness, relevance and business conclusions still require review. No provider requests were needed for these checks.

Release ZIP SHA-256: d92f922f119f13d2572db1aa420bb349bb135f7dfb6ce9c64add0c6d5497d232.

legends-empire 0.2.3: visible vault stewardship

Vault stewardship is a named maintenance workflow in legends-empire.

When asked to organize a vault, agents select vault stewardship, announce the workflow, verify readiness and report what actually ran. The revised installed Markdown recipe makes that behavior explicit.

Catalog 1.0.6 adds legends-vault-stewardship as a direct invocation alias for the same Empire installation. No separate package or registered skill is introduced. Existing users refresh their catalog and update Empire through cto-legends.

The engine and attachable knowledge pack are unchanged. Native Windows supports inspection and previews; transaction writes still require a supported POSIX filesystem.

Validation: full hermetic suite, executable contracts, extracted-package doctor and synthetic scan, knowledge-pack attachment and preservation checks, and public cross-platform CI.

legends-empire 0.2.2

legends-empire 0.2.2

Vault stewardship is part of legends-empire, reached through the single cto-legends router. This patch checks filesystem permission support before transaction journals, backups or notes are written. Unsupported mounts now receive an actionable error instead of reaching a later verification failure and rollback.

The probe is an empty temporary file in the confined runtime directory. Runtime locks and empty directories can already exist when it rejects a filesystem. Exact per-file content and permission checks remain unchanged. WSL Windows-drive mounts require DrvFS metadata support; native Windows continues to support inspection and preview.

Validation: seven new filesystem regression tests, 11 historical journal recovery tests, full hermetic suite and executable contracts, independent review, cross-platform CI, artifact audit, extracted-package installation and knowledge attachment, repeat no-op and preserved private records.

The real house knowledge shelf attached through a verified metadata-enabled mount: seven files, repeat no-op, all 90 historical journal and backup files unchanged. Knowledge pack content remains 0.2.0.

A fresh Codex session selected the router but its host policy blocked file reads. End-to-end automatic execution in that host remains unproven.

Artifact SHA256: b0b9e91fab49c15b10b19b086fb86262de7eadb5a08fb9aa40ca5675dd7e35f0

legends-empire 0.2.1

legends-empire 0.2.1

Fix stewardship knowledge-pack attachment for vaults with transaction history created by the earlier claude-obsidian engine. The two exact historical journal/result schema names are supported with the existing integrity checks. New transactions keep the current schema; terminal history is not rewritten.

Includes the Markdown stewardship workflows, deterministic vault/project/session inspection, baseline comparison and attachable knowledge shelf introduced in 0.2.0. The stewardship knowledge pack remains version 0.2.0 because its content has not changed.

Validation: full hermetic suite and executable contracts; 11 recovery tests; all 10 public CI jobs across Linux, macOS and the Windows portable surface; reproducible artifact audit; extracted-artifact seven-path attachment, repeat no-op and private-record preservation. A read-only check of the house vault validated 14 historical transactions with all 90 metadata and backup files unchanged.

Native Windows supports inspection and attachment preview. Transaction application requires WSL or a supported POSIX host. A fresh Codex host acceptance attempt was blocked by that host's command policy, so unrestricted end-to-end discovery in that host is not claimed.

Artifact SHA256: 358431917f3416d8cba1f8b40ba580f03da54d398366cf9ec6e77385cced2a05

legends-empire 0.2.0: vault stewardship

Vault stewardship is now a core capability inside legends-empire.

Ask your agent to clean and organize a vault, review stale projects or recover
unfinished work. Through the single cto-legends router, the workflow combines
repeatable link and record checks, a bounded review agenda, Markdown maintenance
campaigns, inspected repairs and before/after evidence.

The included knowledge pack supplies reusable methods, ontology and project/session
templates. Preview its attachment to a selected vault. Updates preserve personal
work and refuse to overwrite edited reference files.

• No second registered skill, product installation, database or service.
• Native Windows supports scans and previews. Transaction writes require WSL
  or POSIX and supported wiki/ paths.
• No automatic semantic truth claims, live session control, Plane sync or
  full seven-province starter in this release.

Validation: full hermetic suite; Linux/macOS Python 3.11 through 3.14;
Windows portable checks; reproducible artifact build; extracted ZIP doctor,
scan, knowledge attachment, idempotence, preserved private records and campaign tests.

Source: 79c376eb19171fddfec8c7008b263200c60a22f0.
Attached ZIP SHA-256: ae4a9669daeb98992e60f63359a5c474113f35d255586e021c67273a2325bd21.
Canonical router skill is unchanged, pinned from
45b08cd6d5c6276d67386f6dc92ffd1e10b9fe0b.

See docs/stewardship.md and docs/knowledge-packs.md for the operating recipe
and attachment contract. Catalog admission follows this immutable release.

v0.1.1 Router-native contract patch

Post-reset patch: hermetic suite, contract probes, release builder, and docs assert the router-native surface instead of the removed per-module skill registrations. No behavior change to the memory tools.

Single registered skill (cto-legends, vendored pinned copy at skills/cto-legends/SKILL.md), authoritative version 0.1.1 via VERSION. Router pin: 6975dcbf073e5eec7a30ce6a04a6975238c61158. Source release (tag plus notes); no installer binaries attached.

legends-empire v0.1.0 (router-native generation)

Router-native generation reset.

• Single registered skill: cto-legends, vendored pinned copy at skills/cto-legends/SKILL.md.
• Router pin: 6975dcbf073e5eec7a30ce6a04a6975238c61158 (cto-legends-public HEAD at reset time).
• Per-module skill registrations, agents/ definitions, .claude-plugin/ manifest, host shims, and per-host skill installers removed.
• Authoritative version 0.1.0 via VERSION; CHANGELOG head 0.1.0 (history kept).
• Prior releases and version tags wiped per the reset; git history preserved.