4 Commits

Include renames

Author	SHA1	Message	Date
adminandClaude Opus 5.5	557629d2bf	hub v0.137.0 source + burn-down round 2 in felhom.eu: R-277 R-581 R-600 R-544 R-855 R-134 R-92 R-292 R-599 R-725 R-728 (hub), R-819 R-857 R-555 R-364 R-587 (gates/tools), R-571 R-129 R-124-runbook (docs); 28 rows closed incl. catalog + agent v0.147.0 rows, R-350 merged into R-132, R-888 opened, R-887 mechanism (249 -> 222) ... Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS	2026-10-05 19:43:37 +02:00
admin	acfc2b7e95	R-109 + R-122: the recipe assembly stops dropping sections (hub v0.83.0) ... AssembleDRRecipe's hostHalfShape/appHalfShape are ALLOW-LISTS, not the forward-compat their comment advertised: a section an emitter adds is silently discarded until it is named in both the shape struct and AssembledRecipe. No error, no log, no failing test. R-122 (found this session): that already happened and shipped. The controller has emitted offsite_restic since fork-4 — the offsite recovery LOCATION — the hub stored it for all three real customers, and appHalfShape never listed the key, so no delivered recipe has ever contained it. It stayed green because the fixture drAppHalf is hand-written and omits the field. R-109: the agent's new backup_target is a new top-level host-half section and would have been dropped identically, making the fix read as shipped while changing nothing an operator can see. 3 tests built on halves read verbatim out of the live dr_recipe table, plus 2 red-proofs (each mutation asserted to have landed). vet rc=0, suite rc=0, 17 ok. Registers: R-106 + R-109 dispositioned; R-105/R-106 were READY in ROADMAP with no OPEN-ITEMS row (→ R-123, registered); R-124 filed on the "root" spelling.	2026-07-30 13:13:56 +02:00
adminandClaude Opus 4.8	149a3b092e	hub v0.13.1 — DR recipe v1 drive-shape sync (test-data + regression guard only) ... Tracks felhom-agent v0.39.0, which dropped role + restic_repo_coord from the host-half drives[]. Hub reads drives as json.RawMessage (verbatim passthrough) → no store/handler change needed. Dropped role from the store golden + drHostHalf fixture; re-synced the api host-report golden byte-identical with the agent copy (it previously lacked dr_recipe entirely). Added TestAssembleDRRecipe_V1DriveShape regression guard (demonstrated to fail when the fixture re-adds role, then reverted). No behavior change; redeploy optional. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-16 20:25:51 +02:00
adminandClaude Opus 4.8	5f5e3c54a1	hub v0.13.0: DR recipe — assemble + store + view the secret-free reconstruction recipe ... DR recipe slice (hub half), grounded in SPIKE-dr-recipe-2026-06-16. The hub receives two additive dr_recipe halves on the existing report paths (agent storage/guest/PBS on host-report; controller customer/apps on the controller report), stores them PLAINTEXT in a DEDICATED dr_recipe table keyed by customer (each half preserves the other), and AssembleDRRecipe stitches them into one operator-readable recipe (ignore-unknown + version-skew tolerant). View: a DR-recipe panel on the customer page + GET /customers/{id}/dr-recipe.json download (operator-auth, no secrets to redact). Plaintext-at-rest is correct — the recipe is the clean inverse of the retired infra-backup. Tests: store round-trip (each half preserves the other), assemble-matches-golden, ignore-unknown + version skew, partial halves, no-secrets sweep. Manifest tag bumped to v0.13.0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-16 18:49:45 +02:00