@theholocron/cli 5.0.0-alpha.421 → 5.0.0-alpha.423
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +94 -92
- package/dist/cli.mjs +25024 -24950
- package/dist/cli.mjs.map +1 -1
- package/dist/{config-system-BFlPXyU2.mjs → config-system-B_K14uij.mjs} +2 -2
- package/dist/{index-8QnGZze1.d.mts → index-Dg-iGm_W.d.mts} +47 -47
- package/dist/index.d.mts +8 -8
- package/dist/index.mjs +10 -10
- package/dist/plugin/capabilities.d.mts +1 -1
- package/dist/presets.d.mts +1 -1
- package/dist/presets.mjs +1 -1
- package/package.json +14 -14
package/README.md
CHANGED
|
@@ -17,16 +17,16 @@ holocron --help
|
|
|
17
17
|
## Interactive mode
|
|
18
18
|
|
|
19
19
|
Run `holocron` with no command, a parent command with no subcommand
|
|
20
|
-
(`holocron
|
|
21
|
-
missing a required positional (`holocron deploy`, `holocron
|
|
20
|
+
(`holocron check`, `holocron repo`, `holocron upgrade`, …), or a leaf command
|
|
21
|
+
missing a required positional (`holocron deploy`, `holocron new secret`), and
|
|
22
22
|
you get a prompt instead of a `--help` dead end.
|
|
23
23
|
|
|
24
24
|
The menu mirrors the command tree: each level shows only the next word, and a
|
|
25
25
|
group (marked `›`) opens its own submenu, as deep as the commands nest. Nothing
|
|
26
|
-
is shown as a `<command> <subcommand>` path — `config
|
|
27
|
-
`
|
|
28
|
-
(`
|
|
29
|
-
searches the whole tree
|
|
26
|
+
is shown as a `<command> <subcommand>` path — `show config` is `show ›` then
|
|
27
|
+
`config`. Every submenu has a `← back` item, and a command that is also a group
|
|
28
|
+
(`sync`, `deploy`) has a `(run it)` item at the top of its submenu. Typing
|
|
29
|
+
searches the whole tree, with
|
|
30
30
|
name matches ranked above description matches.
|
|
31
31
|
|
|
32
32
|
```console
|
|
@@ -34,11 +34,11 @@ $ holocron
|
|
|
34
34
|
? What would you like to do? › repo
|
|
35
35
|
❯ repo ›
|
|
36
36
|
? repo — choose a subcommand: › upgrade
|
|
37
|
-
?
|
|
37
|
+
? upgrade — choose a subcommand: › node
|
|
38
38
|
? Target Node.js major version: › 24
|
|
39
39
|
```
|
|
40
40
|
|
|
41
|
-
For a command that declares options (so far: `package
|
|
41
|
+
For a command that declares options (so far: `publish package` — more are
|
|
42
42
|
rolled out one command group at a time), it also offers those: any required
|
|
43
43
|
option is prompted like a positional, and everything else goes through one
|
|
44
44
|
"Set any options?" checkbox, prompting only what you picked:
|
|
@@ -48,7 +48,7 @@ option is prompted like a positional, and everything else goes through one
|
|
|
48
48
|
? npm dist-tag (blank = latest): › beta
|
|
49
49
|
```
|
|
50
50
|
|
|
51
|
-
`package
|
|
51
|
+
`publish package` specifically has three workflows that don't mix — a
|
|
52
52
|
steady-state publish, a one-shot `--initial` bootstrap, and a `--sync-trust`
|
|
53
53
|
maintenance run — so it asks which one first, then only offers that
|
|
54
54
|
workflow's own options; nothing from a different workflow is ever shown:
|
|
@@ -75,7 +75,7 @@ since a dry run never checks it anyway and a code typed any earlier risks
|
|
|
75
75
|
going stale while something else is still being answered.
|
|
76
76
|
|
|
77
77
|
Whether an option is _checkbox-optional vs. always included_ and _collected
|
|
78
|
-
upfront vs. collected last_ are independent choices. `package
|
|
78
|
+
upfront vs. collected last_ are independent choices. `publish package`'s
|
|
79
79
|
`--otp` is always collected last, but whether it's checkbox-optional depends
|
|
80
80
|
on `HOLOCRON_NPM_ENFORCE_2FA`: unset (the default), it's opt-in like any other
|
|
81
81
|
checkbox pick; set in your own shell profile (never checked into the repo),
|
|
@@ -89,7 +89,7 @@ through. A non-interactive shell (CI, a script, a pipe) gets the old
|
|
|
89
89
|
hard-failure message instead of hanging on a prompt.
|
|
90
90
|
|
|
91
91
|
For a command whose handler honours `--dry-run` (most of them — everything
|
|
92
|
-
except
|
|
92
|
+
except the token commands and `show config`), the menu always previews it first — a
|
|
93
93
|
dry run doesn't mutate anything, so there's nothing to ask permission for —
|
|
94
94
|
then asks the one real decision:
|
|
95
95
|
|
|
@@ -107,28 +107,28 @@ entirely, straight to the real run, for when you already know what you want.
|
|
|
107
107
|
|
|
108
108
|
Every command is tagged with how much of a repo it needs:
|
|
109
109
|
|
|
110
|
-
| Context | Needs | Examples
|
|
111
|
-
| ------------ | -------------------------------------------------------- |
|
|
112
|
-
| `global` | the CLI binary alone | `version`, `clone`, `new repo` / `plugin`, `
|
|
113
|
-
| `repo-aware` | `./holocron.config`, walking up from cwd, no plugins | `run`, `run ci`, `config
|
|
114
|
-
| `workspace` | the `@theholocron/holocron-plugin-*` packages resolvable | `doctor`, `
|
|
110
|
+
| Context | Needs | Examples |
|
|
111
|
+
| ------------ | -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
112
|
+
| `global` | the CLI binary alone | `version`, `clone`, `new repo` / `plugin` / `token` / `github-app`, `upgrade …`, `check token` / `resolved`, `remove token` / `skill`, `list tokens` / `skills`, `publish …`, `install skills`, `update skills`, `run lint commit-msg` |
|
|
113
|
+
| `repo-aware` | `./holocron.config`, walking up from cwd, no plugins | `run`, `run ci`, `show config`, `sync readme`, `deploy on-release` |
|
|
114
|
+
| `workspace` | the `@theholocron/holocron-plugin-*` packages resolvable | `doctor`, `setup`, `sync`, `cleanup branches`, `sync secrets`, `deploy`, `sync github`, `sync issues`, `sync ideas` |
|
|
115
115
|
|
|
116
116
|
A `workspace` command run from a bare global install (no plugins next to the
|
|
117
117
|
CLI) fails with one actionable line — install the plugins as devDependencies or
|
|
118
|
-
use `pnpm exec holocron <cmd>`. `
|
|
118
|
+
use `pnpm exec holocron <cmd>`. `check token` degrades to "token present,
|
|
119
119
|
verification skipped" instead. `holocron --help` prints the grouping; see
|
|
120
120
|
[Execution Contexts](https://docs.theholocron.dev/holocron/execution-contexts).
|
|
121
121
|
|
|
122
122
|
### Viewing the resolved config
|
|
123
123
|
|
|
124
|
-
`holocron config
|
|
124
|
+
`holocron show config` prints the resolved config. On a TTY it opens a foldable
|
|
125
125
|
tree by default; piped or redirected, it always emits plain, valid JSON
|
|
126
|
-
(`holocron config
|
|
126
|
+
(`holocron show config | jq`).
|
|
127
127
|
|
|
128
128
|
```console
|
|
129
|
-
holocron config
|
|
130
|
-
holocron config
|
|
131
|
-
holocron config
|
|
129
|
+
holocron show config # TTY: foldable tree (↑↓ move, →/⏎ expand, ← collapse, E/C all, q quit)
|
|
130
|
+
holocron show config --depth 2 # static coloured tree, anything nested deeper than 2 levels collapsed
|
|
131
|
+
holocron show config --no-interactive # static coloured tree, fully expanded
|
|
132
132
|
```
|
|
133
133
|
|
|
134
134
|
Passing `--interactive` explicitly needs a TTY on stdin and stdout and fails
|
|
@@ -256,20 +256,20 @@ and nothing else carries a copy. `.holocron/org.md` (the agent contract the CLI
|
|
|
256
256
|
|
|
257
257
|
### repo options
|
|
258
258
|
|
|
259
|
-
Additional `repo` fields recognised by `holocron
|
|
259
|
+
Additional `repo` fields recognised by `holocron setup`:
|
|
260
260
|
|
|
261
261
|
| Field | Type | Description |
|
|
262
262
|
| ----------------- | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
263
|
-
| `repo.teams` | `Array<string \| { slug, permission }>` | GitHub teams granted repo access. String shorthand defaults to `push` (Write). `holocron
|
|
263
|
+
| `repo.teams` | `Array<string \| { slug, permission }>` | GitHub teams granted repo access. String shorthand defaults to `push` (Write). `holocron setup` also writes `.github/CODEOWNERS` for teams with `push`/`maintain`/`admin`. |
|
|
264
264
|
| `repo.topics` | `string[]` | GitHub topics set on the repository. |
|
|
265
|
-
| `repo.protection` | `"balanced" \| "strict" \| "none"` | Branch-protection preset applied by `holocron
|
|
265
|
+
| `repo.protection` | `"balanced" \| "strict" \| "none"` | Branch-protection preset applied by `holocron setup`. For `"strict"`, the required status checks are derived from the task manifest — see below. |
|
|
266
266
|
| `repo.properties` | `RepoProperties` | Org-level custom property values synced to the GitHub dashboard. |
|
|
267
|
-
| `repo.variables` | `{ repo?, org?, sync?, prune? }` | GitHub Actions variables created and updated by `holocron
|
|
268
|
-
| `repo.secrets` | `{ repo?, org?, environments?, sync? }` | Names of the secrets that must exist, checked (never written) by `holocron doctor secrets`. Names only. The notification layout's secrets and a Chromatic project token are expected without being listed. `sync: [{ environment, keys?, scope?, repos? }]` declares the vault environments `secrets
|
|
267
|
+
| `repo.variables` | `{ repo?, org?, sync?, prune? }` | GitHub Actions variables created and updated by `holocron setup`. Undeclared ones are left alone unless `prune` is on. `sync: [{ environment, keys, scope?, visibility? }]` names the vault environment `holocron sync secrets` fills Actions variables from (a separate environment from the secrets one; names only, a blank value is skipped, `doctor variables` expects the names). A name given as a literal and in `sync`, or `prune` with `sync`, is a config error. |
|
|
268
|
+
| `repo.secrets` | `{ repo?, org?, environments?, sync? }` | Names of the secrets that must exist, checked (never written) by `holocron doctor secrets`. Names only. The notification layout's secrets and a Chromatic project token are expected without being listed. `sync: [{ environment, keys?, scope?, repos? }]` declares the vault environments `sync secrets` fills from (it follows these entries, one step per scope, unless `--github-secret` is given; the `local` and `dev` layers are never synced (a `ConfigError`, and an entry naming them does not load); an environment with no entry and no `--github-secret` is a `ConfigError` before the vault is read, #2104; a blank value is skipped); the doctor expects their keys (every key the `vault` provider lists when `keys` is omitted, names only) at the `scope` (`repo`, `env=<name>`, `org=<name>`). An `org=` scope requires `repos`, the repositories that can read the secrets (visibility `selected`, never `all`); without it the config does not load. `doctor secrets` flags a secret readable by more repositories than its entry lists, and a name held at both repository and organization level. |
|
|
269
269
|
|
|
270
270
|
### Custom properties synced to GitHub
|
|
271
271
|
|
|
272
|
-
`holocron
|
|
272
|
+
`holocron setup` and `holocron sync` both call `syncProperties()` with two
|
|
273
273
|
kinds of fields — always one-way (`holocron.config.ts` → resolved →
|
|
274
274
|
properties; properties are never a second editable source of truth):
|
|
275
275
|
|
|
@@ -307,7 +307,7 @@ these functions unchanged, gathering the same inputs over the GitHub API
|
|
|
307
307
|
instead (D8 — one derivation, two input sources, not two
|
|
308
308
|
implementations).
|
|
309
309
|
|
|
310
|
-
A provider's `Errors.describe()` returns `envKeys` (always pushed to repo secrets by `holocron
|
|
310
|
+
A provider's `Errors.describe()` returns `envKeys` (always pushed to repo secrets by `holocron setup`) and an optional
|
|
311
311
|
`frameworkEnvKeys` (`{ next: ["NEXT_PUBLIC_SENTRY_DSN"] }`), keyed by a `StackName` from `deriveStack()` and pushed only when
|
|
312
312
|
the root or a workspace package depends on that framework.
|
|
313
313
|
|
|
@@ -319,11 +319,11 @@ posts, instead of reporting pass/fail.
|
|
|
319
319
|
|
|
320
320
|
### Required status checks (`protection: "strict"`)
|
|
321
321
|
|
|
322
|
-
`holocron
|
|
322
|
+
`holocron setup` builds the branch-protection required-check list from the
|
|
323
323
|
manifest, not a hand-maintained array:
|
|
324
324
|
|
|
325
325
|
In the repo that holds the reusable workflows (holocron itself) the list is `ci / Required checks` and `DCO`. That is the aggregate
|
|
326
|
-
check (`ci/workflows/ci.yml`, written by `
|
|
326
|
+
check (`ci/workflows/ci.yml`, written by `setup` / `sync` as `.github/workflows/ci.ci.yml`): it waits on
|
|
327
327
|
every `{ required: true }` task, the hand-written checks in `extraRequiredChecks` and its `codecov/*` statuses, and its
|
|
328
328
|
job summary lists each of them with a link, failing ones first. `DCO` stays its own required context. In any other
|
|
329
329
|
repo, which has no `ci` caller yet, the list is:
|
|
@@ -352,12 +352,12 @@ The generated ruleset also sets `require_extra_approval_for_unattributed_changes
|
|
|
352
352
|
false` — with `required_approving_review_count: 0` and a single maintainer, the
|
|
353
353
|
GitHub default (`true`) is an unsatisfiable block on any PR with an
|
|
354
354
|
unverified/unattributed commit. Repository-admin bypass still covers the real
|
|
355
|
-
risk. And the `codecov.yml` `holocron
|
|
355
|
+
risk. And the `codecov.yml` `holocron setup` writes carries `if_not_found:
|
|
356
356
|
success` on every status default, so an infra-only PR (dep bump, config,
|
|
357
357
|
lockfile — no coverable change) passes instead of hanging on a `codecov/*`
|
|
358
358
|
required check that never posts. It also ignores `**/*.mdx`, so a docs-only PR that
|
|
359
359
|
adds pages is not judged to change testable files and left with an empty upload.
|
|
360
|
-
A re-run of `holocron
|
|
360
|
+
A re-run of `holocron setup` backfills all of these into an existing repo.
|
|
361
361
|
|
|
362
362
|
### Default branch (`repo.defaultBranch`)
|
|
363
363
|
|
|
@@ -368,7 +368,7 @@ export default defineConfig({
|
|
|
368
368
|
});
|
|
369
369
|
```
|
|
370
370
|
|
|
371
|
-
`holocron
|
|
371
|
+
`holocron setup` syncs GitHub's repo-level default branch (`HEAD`) — what a
|
|
372
372
|
fresh clone checks out, what `gh pr create`/the compare UI target by default,
|
|
373
373
|
and what Sentinel's `validateConfig()` reads (it only ever reads config from
|
|
374
374
|
the repo's default branch, never a PR ref — a deliberate security boundary).
|
|
@@ -388,7 +388,7 @@ export default defineConfig({
|
|
|
388
388
|
```
|
|
389
389
|
|
|
390
390
|
Controls `holocron probe docs patch` (skipped, reports without failing, or fails for an export a PR adds or changes
|
|
391
|
-
without a doc comment) and whether `holocron
|
|
391
|
+
without a doc comment) and whether `holocron setup` adds the `documentation` flag and its statuses to
|
|
392
392
|
`codecov.yml`, informational for `"warn"`. It never touches the required checks. See the
|
|
393
393
|
[config docs](https://docs.theholocron.dev/holocron/config/#doc-comment-coverage).
|
|
394
394
|
|
|
@@ -402,7 +402,7 @@ export default defineConfig({
|
|
|
402
402
|
});
|
|
403
403
|
```
|
|
404
404
|
|
|
405
|
-
`holocron
|
|
405
|
+
`holocron setup` writes `.husky/pre-push` (runs `holocron run ci` before every
|
|
406
406
|
push) and `.husky/pre-commit` (runs `gitleaks protect --staged` + `lint-staged`
|
|
407
407
|
before every commit — scoped to staged changes, not the whole history, so a
|
|
408
408
|
past false positive can't permanently block future commits) and sets
|
|
@@ -413,7 +413,7 @@ setup --hooks` / `--no-hooks` override per run. Bypass one push with `git push
|
|
|
413
413
|
|
|
414
414
|
### Task scripts
|
|
415
415
|
|
|
416
|
-
`holocron
|
|
416
|
+
`holocron sync` reconciles `package.json#scripts` from the `tasks` manifest
|
|
417
417
|
(merge, never clobber — only the managed keys are touched):
|
|
418
418
|
|
|
419
419
|
```ts
|
|
@@ -451,7 +451,7 @@ export default defineConfig({
|
|
|
451
451
|
`holocron.config`'s `tasks` — **task arrays concatenate**
|
|
452
452
|
(`holocron.config` first), the dedicated file **wins on scalars**,
|
|
453
453
|
`extraRequiredChecks` concatenate. `holocron run` / `holocron run ci` /
|
|
454
|
-
`holocron
|
|
454
|
+
`holocron setup` / `holocron sync` all read the merged result, so the
|
|
455
455
|
split is transparent. Useful for keeping the capability/provider config
|
|
456
456
|
and the "what this repo runs" manifest in separate files (this repo does).
|
|
457
457
|
|
|
@@ -529,7 +529,7 @@ Provider plugins support this through the `Deployment` capability's
|
|
|
529
529
|
existing `getDeployment(id)`. They should set `errorMessage` on the
|
|
530
530
|
returned `DeploymentRecord` whenever the provider exposes one.
|
|
531
531
|
|
|
532
|
-
### `holocron
|
|
532
|
+
### `holocron check monitor <url>`
|
|
533
533
|
|
|
534
534
|
Runs every configured `monitoring` check against `<url>` instead of each
|
|
535
535
|
check's own configured `url` — no vendor API call, only a plain HTTP
|
|
@@ -554,7 +554,7 @@ posts as the GitHub check, no separate reporting step needed.
|
|
|
554
554
|
|
|
555
555
|
### Skills installer
|
|
556
556
|
|
|
557
|
-
`holocron
|
|
557
|
+
`holocron setup` can install shared skills from `@theholocron/skills` into the local repo:
|
|
558
558
|
|
|
559
559
|
```ts
|
|
560
560
|
export default defineConfig({
|
|
@@ -624,23 +624,23 @@ commands and the config are provider-neutral; Discord is the first provider.
|
|
|
624
624
|
|
|
625
625
|
| Command | What it does |
|
|
626
626
|
| ------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
|
627
|
-
| `holocron notifications
|
|
628
|
-
| `holocron
|
|
629
|
-
| `holocron
|
|
630
|
-
| `holocron
|
|
631
|
-
| `holocron
|
|
632
|
-
| `holocron project
|
|
627
|
+
| `holocron setup notifications` | Applies the layout; looks everything up by name first, so a re-run changes nothing that matches |
|
|
628
|
+
| `holocron new channel <name>` | Creates one channel (optionally with a webhook whose URL is stored as a secret) |
|
|
629
|
+
| `holocron new server --name <n> --owner <id>` | Creates the server the layout describes, writes its id into the config, applies the layout, invites the owner, waits for them to join and hands the server over (`--resume` finishes an interrupted hand-over; `--force` allows a second server) |
|
|
630
|
+
| `holocron link account` | Links your account on the provider to your GitHub account by signing in with the provider (OAuth, nothing secret kept) |
|
|
631
|
+
| `holocron sync roles` | Makes who holds a role match a GitHub team, through the links file (`--keep` only adds; `--provider` picks one) |
|
|
632
|
+
| `holocron reconcile project [board]` | Sets item statuses where a rule says so: an open blocker means `blocked`, no blocker left means `planned`, closed means `done` (status only; `--dry-run` previews; an open item with no status is reported). Runs hourly from `platform.projectReconcile.yml`, which `setup` writes when `providers.projects` declares boards |
|
|
633
633
|
| `holocron doctor notifications [--built-only] [--deliver] [--post]` | Step by step: does the server match the layout, do the secrets exist, and does a person (not the bot) own it. A full run also leaves one `🧪 test:` post in the layout's `testChannel`; `--built-only` posts nothing; `--deliver` posts to every channel and removes each post; `--post [channel]` posts the result as the bot (the failures, or only the summary when none fail). It also reads the Checkly feed (webhook, alert channel, subscriptions), the Comlink relay (Worker, route, bindings, the tracker's integration and rule) and the Notifications workflow (the file, and the secrets it reads), posting nothing, so `--built-only` keeps those steps. The `bot-permissions` row compares what the bot's roles hold server-wide with the permissions it needs (`ServerInspection` `botPermissions`; the owner and Administrator hold all, channel overwrites are left to the forum row) and, when some are missing, fails naming them in plain words with the invite link that asks for them again (not a credential); it is skipped, with the reason, when the roles could not be read |
|
|
634
634
|
| `holocron doctor variables` | Do the Actions variables `repo.variables` declares exist, with those values (and, for the organization's, that visibility)? One row for the repository and one for the organization, each only when declared. Read-only. A `repo.variables.sync` entry adds one row that checks its names exist (no value is read or shown). An undeclared variable counts only with `prune`; a scope that cannot be read (no provider, no org token) is a skip, not a failure |
|
|
635
635
|
| `holocron doctor ci` | Has the repo moved to the flat task vocabulary? One row each for the `tasks:` entries (a deprecated alias, with the id that replaces it), the generated callers (file, workflow and job name equal the task id), the `ci` aggregate's `expected` list (no id missing or stale) and where the callers point (`theholocron/.github` or holocron `ci-v1`). Read-only, no provider needed; exits 1 on a failure. The ruleset's checks are `doctor repo`'s |
|
|
636
636
|
| `holocron doctor github-app` | Does each GitHub App instance in `githubApps` (`{ name, manifest, environment }`) have what its manifest file (`default_permissions`, `default_events`) declares? Reads the App's id and key from the vault `environment` in memory (never printed), calls `GET /app` and `GET /app/installations` with the App's JWT. Rows per instance: `reachable`, `events` (all subscribed), `permissions` (each granted at least at the manifest's level, `read < write < admin`), `installations` (none lags the App, a pending update fails). Extras on the App are `info` in a row's detail, never a failure. A gap ends with the App's settings page (user- or organization-owned) and, for an installation, its own page. Credentials that cannot be read are a skip; an unreadable manifest or a rejected JWT fails. Read-only |
|
|
637
637
|
| `holocron doctor logs` | Does each Axiom dataset the setup ships logs to exist, and does the token reach it? Rows: `token is accepted` (a 401 fails), one `dataset for <service>` for the CLI (`HOLOCRON_AXIOM_DATASET`, resolved by the logger's own chain), Sentinel (`SENTINEL_AXIOM_DATASET`) and any other `dev.serve.logging.datasetVar` (a 404 fails and names the fix), `organization` (`HOLOCRON_AXIOM_ORG`, then `AXIOM_ORG`), and an `info` row per dataset with the `retentionDays` Axiom reports (or says it reported none). Reads through the optional `Logs.readDataset` / `Logs.checkToken`; never creates a dataset or prints a token. A name or token that cannot be read is a skip. Read-only |
|
|
638
|
-
| `holocron doctor environments` | Do the deployment environments exist? The ones `
|
|
639
|
-
| `holocron doctor project [--post [channel]]` | Does each board `providers.projects.boards` declares exist and match its template? One row per board, status list, field, view and automation rule; the board's extras and the items `project
|
|
638
|
+
| `holocron doctor environments` | Do the deployment environments exist? The ones `setup` creates (`staging`, `production`, when an `environments` provider is configured) plus every environment `repo.secrets.environments` names. One row. A missing one fails; an extra one is never a problem; no provider with some named is a skip |
|
|
639
|
+
| `holocron doctor project [--post [channel]]` | Does each board `providers.projects.boards` declares exist and match its template? One row per board, status list, field, view and automation rule; the board's extras and the items `reconcile project` would fix (no status, closed but not done, open blocker but not blocked, blocked without a blocker) are `info` rows, never a failure. A template file that does not read fails, naming the file. Read-only; `--post` shares the failing rows through the `notifications` bot. |
|
|
640
640
|
| `holocron doctor shared-values [--strict] [--allow NAME]...` | Does a secret hold the same value in two layers? Reads `<org/repo> - local`, `- dev`, `- ci` and `- prod` in memory and compares the concealed entries by a salted hash made fresh per run; prints names only, one row per pair of layers (`info`, shown as skipped; `--strict` fails), and `info` rows for `ci` variables missing from or different in `dev`. `doctor.sharedVariables` and `--allow` leave out names shared on purpose; a layer that cannot be read is a skip, a missing `local` is silent. Read-only |
|
|
641
641
|
| `holocron doctor variable-owners` | Does a variable name live in more than one place? Reads the names (never a value) of the 1Password Environments the config names and of the GitHub Actions secrets and variables, and fails for a name two places hold, unless a `repo.secrets.sync` / `repo.variables.sync` entry made the copy, `doctor.sharedVariables` lists it, or both places are instances of one `githubApps` App. A bare name beside its prefixed one (`X`, `HOLOCRON_X`) is an `info` row; a place that cannot be read is a skip. Read-only |
|
|
642
|
-
| `holocron doctor credentials` | Does the credentials environment exist, and does it hold every variable the configured plugins take? One row per variable and provider (`ok`, `fail` when missing, `skip` for an optional one not set), listing names only: it never reads a value, and says which spelling of the environment's name matched.
|
|
643
|
-
| `holocron doctor repo` | Do the repository settings `
|
|
642
|
+
| `holocron doctor credentials` | Does the credentials environment exist, and does it hold every variable the configured plugins take? One row per variable and provider (`ok`, `fail` when missing, `skip` for an optional one not set, such as `HOLOCRON_DISCORD_WEBHOOK` or `HOLOCRON_RELEASE_TOKEN`), listing names only: it never reads a value, and says which spelling of the environment's name matched. |
|
|
643
|
+
| `holocron doctor repo` | Do the repository settings `setup` writes match the config? One row per group the config declares: description and homepage, default branch and merge settings, topics, custom properties, team access, branch protection; labels and security settings are always checked. Read-only. Reads through optional `Source` methods (`getRepoInfo`, `getProperties`, `listLabels`, `listTeamAccess`, `getRulesetDetail`, `getSecurity`); a group that cannot be read is a skip, not a failure |
|
|
644
644
|
| `holocron doctor dns` | Do the DNS records the config makes setup write exist, pointing where they should? The preview domain's apex and wildcard CNAMEs (Cloudflare), the docs site a wiki provider asks for, and the relay Worker's proxied placeholder; one row per zone. A missing record, another target or a missing proxy fails; an extra record never does. A record `ensureCustomDomain()` returns is not checked, because asking for it creates the domain |
|
|
645
645
|
| `holocron doctor monitoring` | Do the checks the `monitoring` provider declares exist in its account, matched by name, with the URL, method and (when stated) frequency, locations, activated, should-fail, body and assertions the config sets? One row. A check in the account that is not declared is never a problem. A provider that cannot list its checks, could not load or has no token is a skip |
|
|
646
646
|
| `holocron doctor secrets` | Do the secrets the config says must exist (`repo.secrets`, plus the notification layout's webhook and role secrets and the Chromatic token) exist? One row for the repository, the organization and each environment, each only when something is expected there. Names only; an undeclared secret is never a problem. A scope that cannot be read is a skip |
|
|
@@ -653,15 +653,15 @@ Channels fed by another service are declared with `feeds` on the channel: `{ nam
|
|
|
653
653
|
|
|
654
654
|
Channels fed by the error tracker add `feeds: { errors: true }` and a layout `relay: { host, zone?, script?, code? }`: `setup` makes a dedicated webhook, points `host` at the Comlink Worker (a proxied DNS record via `dns`), and deploys it via `workers.deployScript` with the webhook URL as `COMLINK_<SOURCE>_WEBHOOK`. The URL never leaves the Worker's secret; other secrets on the script are kept. With `relay.errors: { projects, integration?, rule?, frequency? }` it also ensures the tracker's integration and alert rule (`errors.ensureRelay`) and deploys the Worker with the integration's signing secret. Needs `errors`, `workers` and `dns`; only one channel may be fed.
|
|
655
655
|
|
|
656
|
-
`holocron secrets
|
|
656
|
+
`holocron sync secrets <env> --worker <script>` also sets every key of the vault environment on a deployed Worker as a secret, through the optional `Workers.setSecret(script, name, value)` (write-only; the Cloudflare plugin implements it). The Worker must already exist. Sync only adds and updates: it never removes a binding, because a Worker also holds secrets that are not in the vault (for Comlink, the `COMLINK_<SOURCE>_WEBHOOK` that `setup notifications` sets), so a key deleted from the vault must be deleted from the Worker separately. Keys are written one at a time and each is reported; if one fails, the exit code is 1 and re-running finishes the rest, since every write is idempotent.
|
|
657
657
|
|
|
658
|
-
`holocron secrets
|
|
658
|
+
`holocron sync secrets <env>` also writes GitHub Actions **variables** when `repo.variables.sync` has an entry for that environment: each key goes through the `source` provider's `syncVariables` (repo scope) or `syncOrgVariables` (`org=<name>`), one call per key and never pruning, so a name the vault lacks or holds blank is skipped and GitHub keeps its value. Keep these in a vault environment of their own (a vault does not tell a visible value from a secret one, and a variable is readable afterwards). An environment declared only by variable entries pushes nothing to `secrets` or `deployment`. Values are never printed. `doctor variables` checks that the names exist at their scope.
|
|
659
659
|
|
|
660
|
-
`holocron secrets
|
|
660
|
+
`holocron list secrets [--scope repo|environment|organization] [--env <name>] [--json]` prints the names (never the values; GitHub does not return them) of the secrets at each scope, sorted, under a heading per scope. With no `--scope` it lists the repository, plus the organization (`--org`, `HOLOCRON_ORG` or the config's `org`) and the `--env` environment when they are known; `--scope` lists one. A scope that cannot be listed is reported under its heading and the rest are still listed; the exit code is 1 if any fails. `--json` prints `[{ scope, names, error? }]`. It is read-only, so `--dry-run` does not apply. Comparing the names with what the config expects is `doctor secrets`, which also covers the keys of the vault environments declared in `repo.secrets.sync`.
|
|
661
661
|
|
|
662
|
-
A channel with `kind: "forum"` is a forum, with `tags` (each a `name`, an `emoji` and whether it is `moderated`); `setup` adds and corrects the tags but never removes one, and a text channel of the same name must be deleted first, since neither kind can become the other. A forum takes no `webhook` and none of the webhook feeds (`monitoring`, `errors`); its one feed is `feeds: { prs: true }`, the pull-request feed, where Sentinel keeps one post per pull request tagged with its state. The object form `feeds: { prs: { exclude: { repos?: ["owner/name"], authors?: ["login"] } } }` leaves some pull requests out. `feeds.prs` belongs to a forum (a text channel with it is refused) and the forum's `tags` must hold all eight states, `draft`, `conflicts`, `failing`, `changes requested`, `ready`, `waiting`, `merged` and `closed`, or `setup` refuses the layout. `setup` does nothing more for it; `doctor notifications` checks that the forum exists, has those tags and that the bot can start posts and manage threads in it (`ServerInspection` `botThreads`, filled in by the Discord provider after the forum's own permission overwrites). `defaultReaction` is the emoji Discord offers on every post (its Get Started step "Set a default reaction for posts"); Discord allows only one, so `starterReactions` lists more (`["👍", "👎", "❓"]` for approve, disapprove, question) that the bot adds to the first message of each post `specs
|
|
662
|
+
A channel with `kind: "forum"` is a forum, with `tags` (each a `name`, an `emoji` and whether it is `moderated`); `setup` adds and corrects the tags but never removes one, and a text channel of the same name must be deleted first, since neither kind can become the other. A forum takes no `webhook` and none of the webhook feeds (`monitoring`, `errors`); its one feed is `feeds: { prs: true }`, the pull-request feed, where Sentinel keeps one post per pull request tagged with its state. The object form `feeds: { prs: { exclude: { repos?: ["owner/name"], authors?: ["login"] } } }` leaves some pull requests out. `feeds.prs` belongs to a forum (a text channel with it is refused) and the forum's `tags` must hold all eight states, `draft`, `conflicts`, `failing`, `changes requested`, `ready`, `waiting`, `merged` and `closed`, or `setup` refuses the layout. `setup` does nothing more for it; `doctor notifications` checks that the forum exists, has those tags and that the bot can start posts and manage threads in it (`ServerInspection` `botThreads`, filled in by the Discord provider after the forum's own permission overwrites). `defaultReaction` is the emoji Discord offers on every post (its Get Started step "Set a default reaction for posts"); Discord allows only one, so `starterReactions` lists more (`["👍", "👎", "❓"]` for approve, disapprove, question) that the bot adds to the first message of each post `sync specs` makes. Existing posts are left alone, a reaction the bot cannot add is skipped, and `doctor notifications` checks `defaultReaction`. Unicode emoji only.
|
|
663
663
|
|
|
664
|
-
`holocron specs
|
|
664
|
+
`holocron sync specs [--channel <forum>] [--files <paths...>] [--pr <number>] [--refresh] [--refresh-origin] [--refresh-titles] [--withdraw] [--notify]` keeps one forum post per ADR and spec in step with the files: it makes the post (titled with the document's own title, tagged with the file's status), writes its address into the file as `discussion.url`, and turns a gatekeeper's retag into an edit of the file's `status:` line in the working tree for a pull request. `--files` syncs only those files and `--pr` names a pull request on their posts, for a pull request that is still open. `--refresh-origin` is a one-off repair: it rewrites the `PR:` line of existing posts to the one the current rule names (the optional `prLine` of `DiscussionPatch`, and of `DiscussionPost`), and nothing else in them. `--refresh-titles` is the same kind of one-off repair for the title: it renames each existing post whose title differs from the current rule's (the optional `title` of `DiscussionPatch`, and of `DiscussionPost`) and changes nothing else; a rate limit stops it cleanly, reports how many documents are left, and the next run continues. The id that opens a post is a link to the file on the default branch (`repo.defaultBranch`, else `HEAD`) once the file is there, and plain text while `--pr` names an open pull request; the normal sync rewrites a post's id line (and only that line) whenever it is not the one the rule gives and no `--pr` is given, which covers a file that moved and a post made while its pull request was open, so it needs no extra request when every post is right and `--refresh` is no longer needed for it. `--refresh` runs the `PR:`, title and id-link repairs in one pass (the id link is the optional `idLine` of `DiscussionPatch`, and of `DiscussionPost`, which changes only the message's first line); `--refresh-origin` and `--refresh-titles` still do only their own. `--withdraw` (with `--files`, on the base branch) tags the posts of a pull request closed unmerged `withdrawn` and closes them; `withdrawn` is a tag only, never a file `status:`, and the next sync puts the file's own status back. It cannot be combined with `--refresh`, `--refresh-origin` or `--refresh-titles`. `--dry-run` previews it. The posts behind it are also usable for other keys, such as a pull request (`owner/repo#123`, the state a tag name): `DiscussionPatch.body` replaces the first message's text (the provider keeps its footer), and the optional `Notifications` methods `postDiscussionMessage(channel, key, content, { quiet })` (a closed post is unarchived, written to and closed again), `readDiscussionMessages(channel, key, limit)` (text, newest first, 50 by default) and `dedupeDiscussion(channel, key)` (keeps the oldest post of the key, deletes the rest, returns how many) append to, read and repair a post, and `duplicateDiscussions(channel)` lists the keys with more than one post without deleting: `holocron cleanup posts [channel] [--provider <name>] [--yes]` uses the two to clear duplicates that are already there (the forum with `feeds.prs` by default; `--dry-run` previews it). See the [`sync specs` page](https://docs.theholocron.dev/holocron/commands/sync-specs/).
|
|
665
665
|
|
|
666
666
|
Pinned messages are declared under the provider's `layout` as `pinned: [{ channel, content }]` or `pinned: [{ channel, file }]` (`channel` is a channel in the layout, `content` up to 2000 characters, `file` a text file in the repository, such as `.holocron/pinned/rules.md`, whose contents are the message and win over a hand edit; `doctor notifications` reports the drift); the layout is the whole set of messages the bot has pinned in those channels.
|
|
667
667
|
|
|
@@ -695,18 +695,18 @@ Capability surface behind it (all optional, so providers without the concept omi
|
|
|
695
695
|
Provider credentials for Discord: `discord.holonet` is the **bot token** (Bot → Reset Token), `discord.holonet.oauth` is the
|
|
696
696
|
**OAuth client secret** (OAuth2 → Reset Secret). They are different values; the API can create or read neither.
|
|
697
697
|
|
|
698
|
-
See the [command pages](https://theholocron.dev/holocron/commands/notifications
|
|
698
|
+
See the [command pages](https://theholocron.dev/holocron/commands/setup-notifications/) for each command's options.
|
|
699
699
|
|
|
700
700
|
## Ideas
|
|
701
701
|
|
|
702
|
-
- **`holocron ideas
|
|
702
|
+
- **`holocron sync ideas [--dry-run] [--yes]`** — files the ideas that are ready: it reads them through the `ideas`
|
|
703
703
|
provider (`providers.ideas: ["obsidian", { dir }]`, an Obsidian vault; `HOLOCRON_IDEAS_DIR` overrides `dir`; the older
|
|
704
704
|
`ideas.dir` is deprecated and read as that entry when `providers.ideas` is absent) and, for each one whose status is
|
|
705
705
|
the filing state (`ideas.states.file`, default `in-progress`) with no issue, creates an issue through the `issues`
|
|
706
706
|
provider (title the first `#` heading, body the note plus `Filed from idea: <title>`) and records it with
|
|
707
707
|
`Ideas.markFiled` (an `issue:` property, for Obsidian). Ideas with attachments are skipped. It never deletes, asks first
|
|
708
708
|
unless `--dry-run` or `--yes`, and a second run changes nothing.
|
|
709
|
-
- **`holocron
|
|
709
|
+
- **`holocron new spec <issue> [--name <topic>] [--dry-run] [--yes]`** — the spec-time step: reads the issue through the
|
|
710
710
|
`issues` provider (`#1234`, `1234` or a Linear key) and writes `.notes/<name>.spec.md` (`tech-` and the title in
|
|
711
711
|
kebab-case, or `--name` as the whole name) with `status: draft`, `issue:`, `blocked-by: []`, no `id`, and the issue's text
|
|
712
712
|
under `## Problem` less the `Filed from idea:` line and the marker. It never overwrites a file, never edits the issue or
|
|
@@ -728,11 +728,11 @@ See the [command pages](https://theholocron.dev/holocron/commands/notifications-
|
|
|
728
728
|
|
|
729
729
|
## Cleaning up
|
|
730
730
|
|
|
731
|
-
- **`holocron
|
|
731
|
+
- **`holocron apply properties [--yes]`** — adds the capabilities the organization's `holocron_capabilities`
|
|
732
732
|
custom property does not allow yet (`holocron doctor repo` names them). The allowed values are organization-wide, so it
|
|
733
733
|
asks first (`--yes` skips the question; `--dry-run` only reads). It only adds values: nothing is removed or reordered
|
|
734
734
|
and the rest of the definition is kept. It needs a token with the organization's Custom properties: admin.
|
|
735
|
-
- **`holocron
|
|
735
|
+
- **`holocron cleanup branches [--local | --remote]`** — lists the branches whose pull request is merged,
|
|
736
736
|
grouped, each saying whether it lives locally, on the remote or both; then asks, and offers a checklist with the
|
|
737
737
|
proven-merged ones ticked. Proven merged means an ancestor of `origin/alpha` or `origin/main`, or the head (or an
|
|
738
738
|
ancestor, or one of the commits) of a merged pull request. Branches with more commits than their merged PR, with
|
|
@@ -742,12 +742,12 @@ See the [command pages](https://theholocron.dev/holocron/commands/notifications-
|
|
|
742
742
|
|
|
743
743
|
## Upgrading
|
|
744
744
|
|
|
745
|
-
- **`holocron
|
|
745
|
+
- **`holocron upgrade node <to>`** — patches every Node.js version pin
|
|
746
746
|
(`engines.node`, `.nvmrc`, `.node-version`, `.github/workflows/*`,
|
|
747
747
|
`Dockerfile`, `.tool-versions`) to a new major. The rewrite is
|
|
748
748
|
`runUpgradeNode()` in `@theholocron/astromech/upgrade`; the command only
|
|
749
749
|
binds the logger and reads `upgrade.node.extra`.
|
|
750
|
-
- **`holocron
|
|
750
|
+
- **`holocron upgrade deps`** — bumps every `@theholocron/*` pin in
|
|
751
751
|
`pnpm-workspace.yaml` (`catalog:` and every named `catalogs.*`) to its latest
|
|
752
752
|
published version, then migrates `holocron.config.ts` from the 7.x preset
|
|
753
753
|
shape (`const { repo, workflows } = node()` + `repo.requiredChecks` +
|
|
@@ -763,12 +763,12 @@ credential only affects that feature. Store them once in the OS keyring
|
|
|
763
763
|
(macOS Keychain, Windows Credential Manager, libsecret on Linux):
|
|
764
764
|
|
|
765
765
|
```sh
|
|
766
|
-
holocron
|
|
767
|
-
holocron
|
|
768
|
-
holocron
|
|
769
|
-
holocron
|
|
770
|
-
holocron
|
|
771
|
-
holocron
|
|
766
|
+
holocron new token github.read ghp_xxx # clone + CI run listing
|
|
767
|
+
holocron new token github.issues ghp_xxx # issue management
|
|
768
|
+
holocron new token github.sync ghp_xxx # sync-github workflow templates
|
|
769
|
+
holocron new token github.release ghp_xxx # semantic-release
|
|
770
|
+
holocron new token github.admin ghp_xxx # setup, secrets, environments
|
|
771
|
+
holocron new token github.user-sync ghp_xxx # the files that link GitHub accounts to other services' members
|
|
772
772
|
```
|
|
773
773
|
|
|
774
774
|
The resolution chain per capability is:
|
|
@@ -781,26 +781,28 @@ See [`docs/tokens.md`](../../docs/tokens.md) for required PAT scopes per feature
|
|
|
781
781
|
|
|
782
782
|
A plugin lists the tokens it takes in a `tokens: PluginToken[]` export (each resolver exposes its own as `.token`), as
|
|
783
783
|
`{ envName, vendorEnvName?, keyringKey, verifiable?, optional? }`, so `holocron doctor tokens`, `doctor credentials` and
|
|
784
|
-
`
|
|
784
|
+
`export tokens` can find them. Set `optional: true` on a token the plugin only falls back to, such as the Discord
|
|
785
785
|
webhook a post uses when it names no channel: the checks that expect every listed token do not expect it, and
|
|
786
|
-
`
|
|
786
|
+
`export tokens` marks it `(optional)` when it has no value. `verifiable: false` marks a token `verifyToken` does not
|
|
787
787
|
apply to.
|
|
788
788
|
|
|
789
|
-
|
|
789
|
+
The token commands:
|
|
790
790
|
|
|
791
791
|
```sh
|
|
792
|
-
holocron
|
|
793
|
-
holocron
|
|
794
|
-
holocron
|
|
795
|
-
holocron
|
|
796
|
-
holocron
|
|
797
|
-
holocron
|
|
798
|
-
holocron
|
|
799
|
-
holocron
|
|
800
|
-
holocron
|
|
792
|
+
holocron check token github.read # re-verify a stored token
|
|
793
|
+
holocron remove token github.read # remove a stored token
|
|
794
|
+
holocron list tokens # show all stored providers
|
|
795
|
+
holocron list skills # the skills installed in .agents/skills/
|
|
796
|
+
holocron remove skill --all # remove every installed skill (or name some; a bare call asks on a terminal)
|
|
797
|
+
holocron export tokens # tokens as NAME=value lines in a private .credentials, to import into a credentials environment
|
|
798
|
+
holocron export tokens --only HOLOCRON_SENTRY_TOKEN # one token, to the clipboard
|
|
799
|
+
holocron export tokens --blank --vendor-names --file --only VERCEL_TOKEN --only HOLOCRON_RELEASE_TOKEN # the stored ones filled, the rest empty
|
|
800
|
+
holocron new github-app --name "My App - dev" --webhook-url https://<tunnel>/api/webhook --manifest apps/sentinel/github-app.manifest.json # a GitHub App from a manifest (the flow is in @theholocron/dagobah); its id, key and webhook secret to a private .credentials
|
|
801
|
+
holocron new tunnel --name sentinel-dev --hostname sentinel-dev.example.dev --port 3000 --run # a named tunnel with a stable hostname to a local port
|
|
802
|
+
holocron list projects # the org's project boards (also: create [template], close <number-or-name>, setup)
|
|
801
803
|
holocron migrate project v5 --from github --to github:repo=acme/new --dry-run # preview putting a board's issues on a board of the same name in the target (GitHub; --template picks the template a missing board is made from, default roadmap); a target without boards (Linear) gets a project of that name instead
|
|
802
804
|
holocron migrate issues --all --from github --to linear:team=ENG --limit 20 --order newest --dry-run # a trial run: read only the 20 last-created issues (--order oldest, the default, reads the first created); prints `limited to 20 of M`, and a second run with the same limit selects the same issues (`migrate issues` and `migrate project`, and `sync issues`; not `migrate issue`)
|
|
803
|
-
holocron
|
|
805
|
+
holocron move issues v4 v5 --dry-run # preview carrying the open items of one project board to another; without --dry-run it asks first (--yes skips)
|
|
804
806
|
holocron doctor project # does each declared board match its template? (read-only; --post shares the failures)
|
|
805
807
|
holocron dev # the app, its vault variables and the tunnel, in one command (settings: `dev` in holocron.config)
|
|
806
808
|
```
|
|
@@ -841,7 +843,7 @@ Each service has one dataset for all its environments (ADR-0019; the CLI's is `h
|
|
|
841
843
|
(`local`, `development`, `ci`, `test`, `production`), so a query filters by it.
|
|
842
844
|
`log.axiom.dataset` is only a per-repo override. The dataset side of the
|
|
843
845
|
resolution is **execution-context-aware** (ADR-0012): a `global`-context command
|
|
844
|
-
(`clone`, `new`, `
|
|
846
|
+
(`clone`, `new`, `new token`, `upgrade node`, `plugin create`, …) is not "about"
|
|
845
847
|
any repo, so it skips the repo's `log.axiom.dataset` and uses the CLI's dataset
|
|
846
848
|
from the environment or credential chain. `repo-aware` / `workspace` commands
|
|
847
849
|
(`doctor`, `deploy`, `sync`, …) keep the full chain above. See the [logging guide](https://docs.theholocron.dev/holocron/logging/).
|
|
@@ -921,18 +923,18 @@ the local override exists to exempt.
|
|
|
921
923
|
step are passed in
|
|
922
924
|
- `src/cli/cli.ts` — yargs entry, dispatches subcommands. `holocron run` / `ci` are
|
|
923
925
|
delegated to [`@theholocron/astromech`](../astromech) (`createAstromech`).
|
|
924
|
-
`holocron
|
|
926
|
+
`holocron sync` / `holocron setup` write each repo's `.github/workflows/*.yml`
|
|
925
927
|
thin callers from `astromech.thinCallers()`; `holocron sync github` pushes the
|
|
926
928
|
reusable `workflow_call` implementations + composite actions from
|
|
927
929
|
`astromech.reusableTemplates()` (written in `ci/`) to `theholocron/.github` (a pure sync target —
|
|
928
930
|
never hand-edit its `.github/workflows/*`).
|
|
929
|
-
- `src/commands/` — `
|
|
930
|
-
`
|
|
931
|
-
`
|
|
932
|
-
`
|
|
933
|
-
`
|
|
934
|
-
`
|
|
935
|
-
`
|
|
931
|
+
- `src/commands/` — `setup`, `sync`, `doctor`, `deploy`,
|
|
932
|
+
`check monitor`, `list secrets`, `new secret`, `sync secrets`, `publish package`,
|
|
933
|
+
`publish bump-versions`, `publish tag`, `sync github`, `upgrade node`,
|
|
934
|
+
`upgrade deps`, `new plugin`, `check token`, `export tokens`, `setup notifications`,
|
|
935
|
+
`new channel`, `link account`,
|
|
936
|
+
`sync roles`, `doctor ci`, `doctor credentials`, `doctor dns`, `doctor environments`, `doctor monitoring`, `doctor notifications`, `doctor project`, `doctor repo`, `doctor secrets`, `doctor shared-values`, `doctor tokens`, `doctor variable-owners`, `doctor variables`
|
|
937
|
+
`sync roles`, `reconcile project`, `doctor ci`, `doctor credentials`, `doctor dns`, `doctor environments`, `doctor monitoring`, `doctor notifications`, `doctor repo`, `doctor secrets`, `doctor shared-values`, `doctor tokens`, `doctor variable-owners`, `doctor variables`
|
|
936
938
|
- `src/commands/deep-checks/` — `DEEP_CHECKS`, the registry every `doctor <capability>` is
|
|
937
939
|
listed in; the shared row renderer and `declaredVsActual` helper are in `@theholocron/kyber/ui`
|
|
938
940
|
- `src/interactive-menu/` — the interactive fallback's Holocron data: `command-catalog`
|
|
@@ -943,9 +945,9 @@ the local override exists to exempt.
|
|
|
943
945
|
and the prompting pieces — `promptForPositionals`, `promptForOptions` — live in
|
|
944
946
|
`@theholocron/kyber` (`/menu`, `/prompts`), which has no knowledge of commands.
|
|
945
947
|
- `src/plugin/probes/connection-probe/` — the `connectionProbe` a plugin offers, kyber's `connectionProbe` (`@theholocron/kyber/checks`)
|
|
946
|
-
typed as the plugin system's `Probe` with `verify` returning `VerifyTokenResult`; `
|
|
948
|
+
typed as the plugin system's `Probe` with `verify` returning `VerifyTokenResult`; `check monitor` runs its checks
|
|
947
949
|
with kyber's `runCheckAgainstUrl`.
|
|
948
|
-
- `src/commands/move-tag/` — the `
|
|
950
|
+
- `src/commands/move-tag/` — the `publish tag` yargs command, the registry entry and `runMoveTag`, which adds the
|
|
949
951
|
command-bound logger to kyber's `moveMajorTag` (`@theholocron/kyber/git`).
|
|
950
952
|
|
|
951
953
|
## Status
|