@theholocron/cli 5.0.0-alpha.393 → 5.0.0-alpha.395

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 CHANGED
@@ -111,7 +111,7 @@ Every command is tagged with how much of a repo it needs:
111
111
  | ------------ | -------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
112
112
  | `global` | the CLI binary alone | `version`, `clone`, `new repo` / `plugin`, `repo upgrade …`, `auth set` / `check`, `package …`, `run lint commit-msg`, `skills …` |
113
113
  | `repo-aware` | `./holocron.config`, walking up from cwd, no plugins | `run`, `run ci`, `config show`, `repo sync readme`, `deploy on-release` |
114
- | `workspace` | the `@theholocron/holocron-plugin-*` packages resolvable | `doctor`, `repo setup`, `repo sync`, `repo cleanup branches`, `secrets …`, `deploy`, `sync github`, `sync issues` |
114
+ | `workspace` | the `@theholocron/holocron-plugin-*` packages resolvable | `doctor`, `repo setup`, `repo sync`, `repo cleanup branches`, `secrets …`, `deploy`, `sync github`, `sync issues`, `ideas sync` |
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
@@ -691,6 +691,14 @@ Provider credentials for Discord: `discord.holonet` is the **bot token** (Bot
691
691
 
692
692
  See the [command pages](https://theholocron.dev/holocron/commands/notifications-setup/) for each command's options.
693
693
 
694
+ ## Ideas
695
+
696
+ - **`holocron ideas sync [--dry-run] [--yes]`** — files the idea notes in `ideas.dir` (an Obsidian vault; the `ideas`
697
+ block of `holocron.config`, or `HOLOCRON_IDEAS_DIR`) whose `status:` is the filing state (`ideas.states.file`, default
698
+ `in-progress`) and that have no `issue:`: it creates an issue through the `issues` provider (title the first `#`
699
+ heading, body the note plus `Filed from idea: <title>`) and writes `issue:` into the note. Notes with embedded files
700
+ are skipped. It never deletes, asks first unless `--dry-run` or `--yes`, and a second run changes nothing.
701
+
694
702
  ## Syncing issues
695
703
 
696
704
  - **`holocron sync issues --from <a> --to <b> [--since <time>] [--yes]`** — one direction of an issue sync between two
@@ -898,7 +906,7 @@ the local override exists to exempt.
898
906
  (`@theholocron/kyber/plugins`: dynamic-imports plugins, resolves capability config packages,
899
907
  builds the capability registry); Holocron's prefix, plugin options and the credentials / `.env`
900
908
  step are passed in
901
- - `src/cli.ts` — yargs entry, dispatches subcommands. `holocron run` / `ci` are
909
+ - `src/cli/cli.ts` — yargs entry, dispatches subcommands. `holocron run` / `ci` are
902
910
  delegated to [`@theholocron/astromech`](../astromech) (`createAstromech`).
903
911
  `holocron repo sync` / `holocron repo setup` write each repo's `.github/workflows/*.yml`
904
912
  thin callers from `astromech.thinCallers()`; `holocron sync github` pushes the
@@ -921,7 +929,7 @@ the local override exists to exempt.
921
929
  The engine itself (the picker, argv and secret env, the dry-run preview, the spawn)
922
930
  and the prompting pieces — `promptForPositionals`, `promptForOptions` — live in
923
931
  `@theholocron/kyber` (`/menu`, `/prompts`), which has no knowledge of commands.
924
- - `src/plugin/connection-probe/` — the `connectionProbe` a plugin offers, kyber's `connectionProbe` (`@theholocron/kyber/checks`)
932
+ - `src/plugin/probes/connection-probe/` — the `connectionProbe` a plugin offers, kyber's `connectionProbe` (`@theholocron/kyber/checks`)
925
933
  typed as the plugin system's `Probe` with `verify` returning `VerifyTokenResult`; `monitoring check` runs its checks
926
934
  with kyber's `runCheckAgainstUrl`.
927
935
  - `src/commands/move-tag/` — the `package move-tag` yargs command, the registry entry and `runMoveTag`, which adds the