Files

tegwick e8bb469033 feat(WARDEN-WP-0018): activate whynot-design npm publish lane + resolvable flag

railiance-platform finished provisioning the whynot-design npm publish lane
(CCR-2026-0001, commit 8f617fc: active, readiness=ready, resolvable=true, positive
fetch + negative denial verified). First concrete warden access --fetch-resolvable
non-SSH lane — end-to-end proof of the WP-0014 conduit + WP-0017 discoverability.

T1 — catalog entry whynot-design-npm-publish (active, exec_capable) with the
owner-confirmed zero-placeholder handoff: path platform/workloads/coulomb/whynot-design/
npm-publish (the superseded whynot-design/whynot-design/... form is not used), field
NPM_AUTH_TOKEN, OIDC role whynot-design-workload-kv-read, policy + flex-auth ref. Added
wiki/playbooks/whynot-design-npm-publish.md.

T2 — RouteEntry.resolvable (active + exec_capable + no <…> placeholder), surfaced in
route/access --json; Catalog.find resolves an exact catalog-id first so
`warden access whynot-design-npm-publish` is deterministic. Tests added; fixed a
no-match test query that substring-collided (no ⊂ whynot). 213 pass, lint clean.

T3 — notified whynot-design (zero-placeholder command + resolvable gate + path
correction) and confirmed activation to railiance-platform. Sibling lanes stay draft
per their deferral.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-29 00:32:00 +02:00

capabilities

docs(WP-0010): sharpen mission to "issue SSH, route the rest" + pointer catalog

2026-06-18 20:44:53 +02:00

flex-auth

feat: close WP-0009/WP-0013 production integration stewardship strand

2026-06-24 12:44:32 +02:00

indexes

WARDEN-WP-0006: NetKingdom stewardship docs and alignment

2026-06-17 08:22:45 +02:00

policy

feat(WARDEN-WP-0015): T2 — machine-readable posture descriptors + warden policy

2026-06-27 18:10:54 +02:00

routing

feat(WARDEN-WP-0018): activate whynot-design npm publish lane + resolvable flag

2026-06-29 00:32:00 +02:00

README.md

Add capability registry scaffold (REUSE-WP-0014-T06 B04)

2026-06-16 01:56:08 +02:00

README.md

Capability Registry

Markdown-first capability index for federation and reuse planning.

Authoring

Copy a capability entry template (see reuse-surface templates/capability-entry.template.md).
Add the row to indexes/capabilities.yaml.
Run reuse-surface validate from a checkout with the CLI installed.
Merge to main and verify publish with reuse-surface establish --publish-check.

Federation contract: reuse-surface docs/RegistryFederation.md.