Effigy 0.8.17

╭─────────────────────────────────────────╮
│ EFFIGY /home/runner/work/effigy/effigy │
╰──────────── v0.8.17+local.a537f0d.dirty ╯

Added

• effigy catalog cache clear removes the repo-local catalog discovery cache, forcing the next catalog walk to inspect previously pruned large empty subtrees.

Changed

• Catalog discovery now caches discovered manifest paths and large no-catalog subtrees under .effigy/cache, avoiding repeated full-tree walks in repos with large generated data directories.

Fixed

• Generated asset scans now ignore Effigy's internal .effigy state, so catalog cache files do not inflate scan counts or trip generated-assets reports.
• Container project names are normalized before backend calls, so bundle-derived names from mixed-case paths such as r7-webCore no longer fail Docker/nerdctl project-name validation.

Effigy 0.8.16

╭─────────────────────────────────────────╮
│ EFFIGY /home/runner/work/effigy/effigy │
╰──────────── v0.8.16+local.6d0c92b.dirty ╯

Fixed

• Port auto-allocation now fails with an explicit registry-exhausted error when no full project range remains, instead of creating a truncated 65535..65535 allocation that later breaks container bootstrap.
• Explicit and implicit container deferrals run from inside a managed container no longer re-resolve host-side external mount paths against the container repo root, so mounts like host = "../../libraries" remain host-relative instead of failing under /var/www/....

Effigy 0.8.15

╭─────────────────────────────────────────╮
│ EFFIGY /home/runner/work/effigy/effigy │
╰──────────── v0.8.15+local.9a0c1e6.dirty ╯

Added

• Managed Colima profile disk sizing is now configurable via effigy config set containers.profile_disk_gib <GiB> and effigy container profile recreate --disk <GiB>. Interactive profile recreate runs prompt for the disk size when --disk is omitted.
• effigy container profile purge deletes the managed Colima profile and its runtime data without recreating or restarting it.
• effigy uninstall now plans or removes initial Effigy-owned local machine state: user-global config, user-global catalog overrides, and the managed Colima profile.

Effigy 0.8.14

╭─────────────────────────────────────────╮
│ EFFIGY /home/runner/work/effigy/effigy │
╰──────────── v0.8.14+local.5bdc28d.dirty ╯

Fixed

• Bootstrap and catalog discovery now ignore catalog.alias values supplied only by bundle defaults. Repos without an explicit project alias use the repo/folder name, so bootstrapping a repo like git@github.com:acowtancy/acowtancy.git keeps the acowtancy destination instead of renaming it to an inherited root.
• Bootstrap's built-in database seed fallback now prepares the default container runtime before importing SQL dumps, so bundle-backed repos without an explicit bootstrap:db-seed task do not fail with container service ... is not running immediately after root setup.

Effigy 0.8.13

╭─────────────────────────────────────────╮
│ EFFIGY /home/runner/work/effigy/effigy │
╰──────────── v0.8.13+local.87e3485.dirty ╯

Fixed

• Workspace/container handoff no longer fails when a TCP alias domain maps to a service name that is not resolvable inside the primary container yet. Effigy now warns and skips that /etc/hosts patch instead of aborting docker compose exec tcp alias hosts, so optional sidecars like memcached do not block container bring-up.

Effigy 0.8.12

╭─────────────────────────────────────────╮
│ EFFIGY /home/runner/work/effigy/effigy │
╰──────────── v0.8.12+local.385f34d.dirty ╯

Added

• Supply-chain policy via cargo-deny (deny.toml): enforces RUSTSEC advisories, an OSI-permissive license allowlist, registry-wildcard bans, and a crates.io-only source rule. Enforced in CI by a cargo deny check job and paired with Dependabot weekly cargo + GitHub-Actions update PRs. Run cargo deny check locally before changing dependencies.

Added

• The gateway now verifies route-table integrity before the (possibly elevated) daemon trusts it: the route table is written owner-only (0o600) with an Effigy-managed provenance marker, and the daemon's read path refuses a group/other-writable or unmarked/foreign-marked table, keeping its last-known-good in-memory routes instead. effigy gateway status reports route_table_trust and effigy doctor warns when the table is untrusted. (Migration: a routes.json written by an older Effigy lacks the marker and will be treated as untrusted until the next route registration re-stamps it — re-run effigy container up or re-register routes once after upgrading.)

Changed

• The repo-wide clippy allows (result_large_err, too_many_arguments, type_complexity) now live in [workspace.lints.clippy] instead of CLI -A flags, and the 33 redundant per-site #[allow(clippy::too_many_arguments)] attributes were removed. A plain cargo clippy now matches CI with no extra flags.
• Updated dependencies (regex, s3, reqx, tabled, sha2 0.11, rusqlite 0.40) and pinned the toolchain to Rust 1.96 via rust-toolchain.toml. The newer sha2/rusqlite releases require rustc ≥ 1.95; this raises the project's effective minimum supported Rust to 1.96.

Fixed

• Container bring-up now warns pre-emptively when the colima-forwarded host SSH-agent socket is stale (a dangling /run/host-services/ssh-auth.sock after the host agent socket rotates on a long-running VM), naming the colima restart <profile> fix — instead of failing later with the cryptic nerdctl mkdir /run/host-services/ssh-auth.sock: file exists.
• effigy scan dead-code now refuses a stale graph index (not just an unusable one) and points to effigy graph index, instead of reporting false positives from drifted symbol positions and missing edges.
• SecretValue now serializes as [REDACTED] instead of plaintext. A secret accidentally included in a Serialize-derived struct (logs, JSON output, diagnostics) can no longer leak; the encrypted vault payload is the only path that serializes real secret bytes, and it now opts in explicitly.
• The local gateway daemon and the process supervisor no longer cascade a panic across every subsequent request or child-reap when a lock is poisoned by an unrelated thread panic. Poisoned route-table, TLS-cert, and child/process-map locks now recover the inner guard and keep serving instead of aborting.
• effigy doctor no longer reports a schema error on this repo's own clean tree. Test-fixture manifests under tests/ are excluded from ambient catalog discovery via [catalog.discovery] ignore, so partial/malformed fixture effigy.toml files are no longer treated as live catalogs.
• The manifest schema validator now recognizes the [catalog.discovery] table (enabled, ignore) that catalog discovery already consumes, so configuring it no longer trips manifest.schema.unsupported_key.

Effigy 0.8.11

╭─────────────────────────────────────────╮
│ EFFIGY /home/runner/work/effigy/effigy │
╰──────────── v0.8.11+local.75fc8e0.dirty ╯

Fixed

• The release-binaries workflow now pins macOS runners by CPU architecture so Apple Silicon and Intel release builds run their smoke checks on matching GitHub-hosted images.
• Gateway loopback migration now persists repo-scoped identity upgrades back to the registry file instead of only updating the in-memory assignment map.

Effigy 0.8.9

╭─────────────────────────────────────────╮
│ EFFIGY /home/runner/work/effigy/effigy │
╰───────────── v0.8.9+local.4509699.dirty ╯

Fixed

• effigy container profile resize now applies managed Colima sizing by stopping and restarting the profile in place, and container profile status now points operators at that non-destructive path instead of only the destructive recreate workflow.

Effigy 0.8.8

╭─────────────────────────────────────────╮
│ EFFIGY /home/runner/work/effigy/effigy │
╰───────────── v0.8.8+local.ee229bd.dirty ╯

Fixed

• release:linux:rehearse now streams in-container Linux build output as it
  runs instead of buffering the full build log until the container command
  exits.
• effigy container cache list --global now detects legacy opaque efv-*
  volumes that contain Rust target directories, so
  effigy container cache prune --kind rust-target --yes can clear old
  container build caches instead of relying on orphan volume cleanup.
• The managed default effigy Colima profile now targets a 300GiB disk for
  new or recreated profiles, and running-profile warnings include undersized
  disks as well as undersized memory.
• effigy container profile status and effigy container profile recreate
  now provide an explicit inspect-and-rebuild workflow for applying managed
  Colima profile sizing to existing local profiles.

Effigy 0.8.7

╭─────────────────────────────────────────╮
│ EFFIGY /home/runner/work/effigy/effigy │
╰───────────── v0.8.7+local.1ebc258.dirty ╯

Fixed

• effigy scan dead-code now recognizes Rust public/test/API roots,
  descriptor and dispatch roots, data-shape references, impl/call references,
  serde default helpers, binary entrypoints, nested crate modules, and
  cross-file references more accurately, reducing Effigy's own current
  dead-code findings to zero after removing confirmed dead artifacts.