coulomb/secrets-engine
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

refactor(catalog): explicit org/repo terminology; npm targets coulomb Gitea registry

Browse source 
Gitea's "project/package/release" terms are overloaded, so the catalog now uses
the most explicit words:
- org  = coulomb (the Gitea organisation)
- repo = whynot-design (the Gitea repository/product) — not an org, not a scope
- npm scope @whynot and package @whynot/design are distinct from both

Changes:
- catalog schema: replace conflated `owner` with required `org` + `repo`; `owner`
  is now a derived `org/repo` slug property
- npm-config delivery is data-driven: registry + scope live in
  delivery_config.npm and are validated; engine no longer hardcodes a registry
- exec delivery writes `<scope>:registry=<url>` + scoped `:_authToken` for the
  configured Gitea registry (token still env-expanded, never written to disk)
- pilot lane points at https://gitea.coulomb.social/api/packages/coulomb/npm/,
  scope @whynot, KV path coulomb/whynot-design/npm/publish
- npm-publish-demo uses @whynot scope so dry-run resolves the Gitea registry
- docs: terminology table; routing owner shown as coulomb/whynot-design
- tests: org/repo required, npm-config validation, registry authkey mapping

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-06-28 12:44:55 +02:00
parent 147cf8acda
commit f87f4e5e4d
9 changed files with 153 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

15
docs/cli.md
View file

@ -1,5 +1,20 @@
# secrets-engine CLI
## Terminology (Gitea is overloaded — be explicit)
| Term we use | Means | Example | Not to be confused with |
| --- | --- | --- | --- |
| **org** | the Gitea organisation | `coulomb` | the npm scope |
| **repo** | the Gitea repository / product | `whynot-design` | an org; a Gitea "project" board |
| **npm scope** | the `@`-prefix npm name | `@whynot` | the org or the repo |
| **npm package** | the published artifact | `@whynot/design` | the repo it's built from |
| **lane / catalog id** | a secrets-engine secret lane | `whynot-design-npm-publish` | — |
A catalog entry carries `org` + `repo` explicitly (never a bare "owner"), and the
npm registry/scope live in `delivery_config.npm` as data — the engine never
hardcodes a registry. The pilot publishes `@whynot/design` from the
`coulomb/whynot-design` repo to `https://gitea.coulomb.social/api/packages/coulomb/npm/`.
## Install
```bash