Files

tegwick bd335ec724 feat(WARDEN-WP-0019): route secret-exec lanes to secrets-engine (route-primary, proxy fallback)

secrets-engine (SECRETS-WP-0003) shipped a native secret-exec front door
(`secrets-engine route/exec`, decision e6381a56) and asked ops-warden to route to it.
Bernd's call: route-primary, proxy-fallback — surface the secrets-engine exec as the
primary path for owned lanes, keep `warden access --exec` as a transparent fallback.

T1 — RouteEntry gains exec_owner/exec_command/pointer_command (+ has_native_exec),
screened for secret material like the other handoff fields. whynot-design-npm-publish
points its native exec at secrets-engine. `warden access` renders Primary (secrets-engine
exec) + Fallback (warden proxy); route/access JSON gain the fields and a native-exec-aware
next_action. Tests added; 217 pass, lint clean.

T2 — credential-routing.md adds secrets-engine as the secret-exec owner (route primary,
proxy fallback); SCOPE adds secrets-engine to Related Repos and records the npm lane as
production-exercised (@whynot/design@0.4.0); playbook leads with secrets-engine exec and
fixes the fallback one-liner (--field NPM_AUTH_TOKEN, --no-policy) per whynot-design.

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

2026-06-29 17:41:49 +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-0019): route secret-exec lanes to secrets-engine (route-primary, proxy fallback)

2026-06-29 17:41:49 +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.