coulomb/whynot-design
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Close WHYNOT-WP-0003 after all nine downstream-consumption tasks finished.
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Hand the remaining npm-read token lane to WHYNOT-IN-0001 as a residual
intake. T09's contract-parity deferral is already a resolved decision.

Assistant: grok
Assistant-Session: 01a04d7c-846d-77e3-af8d-020019e4eb61
This commit is contained in:
tegwick 2026-08-29 14:45:50 +02:00
parent ba10e325d3
commit faec0e6807
2 changed files with 35 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

27
intakes/intakes.md Normal file
View file

@ -0,0 +1,27 @@
# Intake records
## WHYNOT-IN-0001 — Provision a consumer npm-read lane
```yaml
id: WHYNOT-IN-0001
kind: intake
title: "Provision a consumer-install npm-read lane for @whynot/design"
lane: yellow
status: open
origin: residual
origin_ref: WHYNOT-WP-0003
priority: medium
owner: whynot-design
repo: whynot-design
description: |
WHYNOT-WP-0003-T02 published @whynot/design to the coulomb Forgejo npm
registry using the publish lane. A separate read/install token id
(whynot-design-npm-read) was never provisioned; the publish token was
enough to verify one install.
Consumers still need an .npmrc token to install from the org registry.
Route custody through warden route / OpenBao (railiance-platform). Do
not inline a secret in Git, State Hub, or this record.
created: "2026-08-29"
updated: "2026-08-29"
```