diff --git a/README.md b/README.md index 3cc750c..2969938 100644 --- a/README.md +++ b/README.md @@ -81,7 +81,7 @@ lyracore packages disable NAME [--yes] lyracore packages remove NAME [--yes] lyracore packages build lyracore packages check -lyracore packages replay [DATABASE ...] [--check] [--yes] [--force-all] [--client-data PATH] +lyracore packages apply [DATABASE ...] [--check] [--yes] [--force-all] [--client-data PATH] lyracore packages config NAME [KEY [VALUE]] [--new] ``` @@ -154,7 +154,7 @@ no `--accept` option. | `packages remove NAME` | Delete a disabled Package after confirmation. Refuse changes to its recorded Content Identity. | | `packages build` | Refresh typings, install pinned Bun dependencies, typecheck and run Datascripts, compile Runtime Scripts, and check the generated artifacts together. | | `packages check` | Check Package Deltas and Script Artifacts against their inputs, refreshing typings when needed. Preflight also runs this check. | -| `packages replay` | Apply enabled Packages' spell Package Deltas and reconcile Runtime Scripts on each target Shard. | +| `packages apply` | Prepare installed sources, publish Rust Packages, and apply artifacts on each target Shard. | | `packages config NAME [KEY [VALUE]]` | List Package Config, read one key, or write one key on every recorded fixture Shard. | A bare name such as `playerbots` selects a Package from the @@ -164,7 +164,7 @@ must contain one Package at its root. Use `./my-package` to select a local folde ```bash lyracore packages add playerbots lyracore packages list -lyracore packages replay --check +lyracore packages apply --check ``` Adding, updating, enabling, or disabling a Package does not publish the Module or sync a client. @@ -172,8 +172,10 @@ Follow the next steps the command prints. Package Teardown deletes the Package's before disabling it on a recorded dev node, so the command asks first. Without a recorded node it moves the folder and reports any tables that still need teardown before publishing. -`packages replay` uses the recorded fixture Shards unless you name destinations. `--check` prints -the plan without changing Shards. Replays skip Import Families whose recorded inputs already +`packages apply` uses the recorded fixture Shards unless you name destinations. `--check` prints +the plan without changing Shards. It can build local artifacts. `apply` prepares missing or stale +artifacts and publishes the Module when the Package Inventory contains Rust or a target records +pending Package Teardown. Artifact application skips Import Families whose recorded inputs already match, so a retry resumes unfinished work; `--force-all` reapplies matching families too. `--client-data PATH` supplies the client archives needed for the spell family. An empty enabled Package set also reconciles state, removing Runtime Scripts and spell changes from disabled @@ -183,8 +185,8 @@ Packages. a key. Reads report disagreements between Shards. Use `lyracore config` for the client path; Package Config holds the values a Package reads at runtime. -Use `--yes` to answer the confirmation for `add`, `update`, `disable`, `remove`, or `replay` in -advance. It does not bypass their checks. Bun is needed for authoring with `packages build`; +Use `--yes` to answer the confirmation for `add`, `update`, `disable`, `remove`, or `apply` in +advance. It does not bypass their checks. Bun is needed when `build` or `apply` must compile sources; applying a prebuilt Package does not require it. `packages build` records a Build Identity for each artifact it generates. Datascripts need a Base diff --git a/docs/commands.md b/docs/commands.md index f3c7d95..d54b171 100644 --- a/docs/commands.md +++ b/docs/commands.md @@ -71,7 +71,7 @@ lyracore packages enable NAME lyracore packages list lyracore packages new NAME [--from RUNG] lyracore packages remove NAME [--yes] -lyracore packages replay [DATABASE ...] [--check] [--yes] [--force-all] [--client-data PATH] +lyracore packages apply [DATABASE ...] [--check] [--yes] [--force-all] [--client-data PATH] lyracore packages update [NAME] [--yes] lyracore character gm NAME true|false lyracore production status --server SERVER --gateway-log PATH --realm-core DB DATABASE ... @@ -104,7 +104,7 @@ lyracore update | `packages list` | every installed Package: enabled or disabled, where it came from, and whether it has drifted | | `packages new` | copy and rename a Reference Package from the collection tag matching this checkout's Package API | | `packages remove` | delete a disabled Package, after a confirmation and a check for local changes | -| `packages replay` | reapply every enabled Package's claims and Runtime Scripts onto the named Shards, or the whole recorded fixture topology by default | +| `packages apply` | prepare installed sources, publish Rust Packages, and apply artifacts to the named Shards or recorded development topology | | `packages update` | update Git Package Sources from their repository and Official Package Sources from the compatible collection tag | | `character gm` | flip GM commands on or off for a character, on whichever world shard has it | | `production status` | read-only checks for an explicitly named production topology and the latest gateway start | @@ -284,11 +284,11 @@ installed in its place. The Provenance Stamp records the collection's URL and th directory was resolved at. `packages update` can advance the installed Package to the current commit at the compatible tag, after the normal Trust Review and confirmation. -**It publishes nothing.** The two remaining steps are printed for you to run: +The command prints the next steps for the content it installed: ```bash -./lyracore publish # compile the Package in and publish it to every database -./lyracore client sync # if the Package ships addons or client overrides +./lyracore packages apply # prepare and activate installed Packages +./lyracore client sync # if the Package ships client content ``` A failed `preflight` leaves the copy in place, says the module on the node is unchanged, and names @@ -315,9 +315,9 @@ Each `.