CONTENT-WP-0000-T04 needed a browser on the workstation. The published capability is a discovery card at availability A2, and plan-check still returns new for "headless browser". REUSE-IN-0001 asks the query to name a verified trial or to report that availability gap.
Assistant: grok
Assistant-Session: 01a1346c-fdff-7741-b1af-b7283661554b
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 4609@bnt-lap001
Assistant-Session: 085df492-f02a-4fe6-acad-2aa52789fe1b
Updated by fix-consistency on 2026-09-20:
- update .custodian-brief.md for reuse-surface
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 4609@bnt-lap001
Assistant-Session: 085df492-f02a-4fe6-acad-2aa52789fe1b
Updated by fix-consistency on 2026-09-20:
- update .custodian-brief.md for reuse-surface
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 4609@bnt-lap001
Assistant-Session: 085df492-f02a-4fe6-acad-2aa52789fe1b
Residual handoff from FLEX-WP-0020 (flex-auth -> access-engine). Forge ID 42
and the repo UUID are unchanged, and runtime names stay flex-auth per
FLEX-DEC-2026-013, so this is a federation-source-coordinate change only.
Both tasks start in wait: the forge rename has not landed (access-engine
raw index returns 404, flex-auth still resolves), and flipping the URL early
would drop an enabled publish-passing source from the composed index.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 4609@bnt-lap001
Assistant-Session: 085df492-f02a-4fe6-acad-2aa52789fe1b
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 4609@bnt-lap001
Assistant-Session: 085df492-f02a-4fe6-acad-2aa52789fe1b
Moves the remaining finished workplans into workplans/archived/. Prefixes
use each workplan's own completion date per the convention, not the date
the archive sweep ran.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 4609@bnt-lap001
Assistant-Session: 085df492-f02a-4fe6-acad-2aa52789fe1b
Updated by fix-consistency on 2026-09-20:
- update .custodian-brief.md for reuse-surface
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 4609@bnt-lap001
Assistant-Session: 085df492-f02a-4fe6-acad-2aa52789fe1b
Rebind REUSE-WP-0017/0018/0019 to their authoritative State Hub records:
workplan UUIDs restored into blank frontmatter, task ids rebound to the
2026-07-06 originals (matched by heading and creation order) rather than
the 2026-08-28 deterministic duplicates. Bindings upload now syncs 22/22
instead of returning 422; C-03 clears.
Closes REUSE-WP-0021-T02 and the workplan.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 4609@bnt-lap001
Assistant-Session: 085df492-f02a-4fe6-acad-2aa52789fe1b
Updated by fix-consistency on 2026-09-20:
- update .custodian-brief.md for reuse-surface
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 4609@bnt-lap001
Assistant-Session: 085df492-f02a-4fe6-acad-2aa52789fe1b
Set flavor on open workplans from origin/prose/status. Copy existing
depends_on aliases only. Do not promote residuals.
Assistant: grok
Assistant-Session: 01a09dc1-b21e-77e1-919e-fcad2f82b267
Updated by fix-consistency on 2026-08-25:
- update .custodian-brief.md for reuse-surface
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
The remote row pointed at 127.0.0.1:18000, a reverse tunnel back to the
workstation. On railiance01 the State Hub runs in the cluster on that same
machine, so the request left the box and came back to reach a local service.
Refs CUST-WP-0067-T07
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
A registration change now self-heals: PATCH of a composition field advances
composed_at on the next plain GET, while a description-only PATCH leaves the
cache alone. Both confirmed against the production hub.
Record the revision 9 lesson: it reported STATUS: deployed and Upgrade
complete while shipping nothing, because the values file still pinned the
previous tag. A successful helm upgrade proves the chart applied, not that the
code changed -- confirm the running image afterwards.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Enabling a federation source left /v1/federated serving its cached compose and
reporting stale: false while doing it, so a repo could be correctly registered
and silently invisible for as long as its cached index survived. That is how
evidence-binder stayed missing after re-enabling until a manual
POST /v1/federated/compose was issued.
Registration writes now mark the composed index stale, and a plain GET
recomposes when the flag is set. Clearing it there is not a silent clear: that
pass really did refetch. A PATCH touching only a description does not
invalidate anything.
This changes a contract documented in specs/FederationHubAPI.md, so the
staleness section is rewritten rather than left to drift, including the two
triggers that now set the flag.
The first two tests written for this were worthless -- they passed with the fix
removed, because a newly registered repo has no cache entry and gets fetched
regardless. The real failure needs a populated cache holding stale content
inside its 24h TTL. test_re_enabled_source_refetches_a_stale_cache models that
and fails on pre-fix code; verified by reverting the mark_stale calls.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
evidence-binder published their repaired index at e462775 and correctly held
the re-enable request until it was visible on Forgejo. Pre-checked this time
before touching production: backing entries return 200, and a local compose of
all 61 sources gave 64 capabilities with zero warnings and no duplicate IDs.
Public endpoint now serves 61 sources / 64 capabilities, with both
capability.evidence.binding and capability.evidence.rect-registry at
D3 / A2 / C3 / R3.
Open T09 for the gap this exposed: enabling a source does not invalidate the
composed index. The endpoint kept serving a stale compose, reporting
stale: false throughout, until POST /v1/federated/compose was called by hand.
A repo can be correctly registered and silently invisible.
SCOPE.md: refresh the federated counts, record the deployed image, and correct
the multi-domain claim — member rows have begun carrying their own domain
(evidence-binder publishes domain: infotech) even though the manifest is still
composed under helix_forge.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Helm revision 8. /health returns 200 from uvicorn instead of 404 from the
landing nginx, / still serves the landing page, and make reuse-smoke passes
end to end for the first time.
Also resolves the composed_at observation: it was not a bug, just a build
that predated REUSE-WP-0019-T06. The timestamp now advances per recompose.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
An index row with no id now says whether it looks like a SCOPE.md capability
block, instead of leaving the author to work out why their repo contributes
nothing to the federated index. That confusion is invisible without a
diagnostic: the row is valid YAML, the file parses, and the member just
silently disappears.
Swept all 61 federation sources with --refresh: evidence-binder is the only
affected member. The other ten zero-count repos are genuine empty scaffolds.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Clears the hub scope check's C5b/C5c warnings: Relevant When, Not Relevant
When, How It Fits, Terminology, Related / Overlapping, and Provided
Capabilities were all missing, along with any fenced capability block.
The Terminology section calls out something this workplan ran into for real:
the fenced `capability` blocks in SCOPE.md (type/title/description/keywords)
look like index rows in registry/indexes/capabilities.yaml but are a different
shape and are not validated. evidence-binder copied the SCOPE block shape into
its index, which is why it had no `id` and broke federation composition.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Helm revision 7 on Railiance01. Production now runs a Forgejo image; the Gitea
dependency is gone from both the federation sources and the image reference.
/v1/reuse-events returns 200 for the first time, so REUSE-WP-0019 T04/T05 are
finally live. PVC and all 61 registrations survived.
Also diagnose T06: /health is served correctly by the app (200 in-cluster) but
Traefik routes it to the landing nginx, because router priority is derived from
rule-string length and Path(/health) ties with PathPrefix(/). Raise T06 to
medium — make reuse-smoke is the documented deploy check and it false-negatives.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
