@assemora/cli 0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Assemora
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+

package/README.md

@@ -0,0 +1,272 @@
+# @assemora/cli
+
+The `assemora` executable (SPEC.md §77).
+
+```bash
+assemora dev          # run the project, restarting when a file changes
+assemora make:model Post
+assemora db:generate add-posts
+assemora db:migrate
+assemora routes
+```
+
+## It is a client of the application, not a second one
+
+The CLI never imports a feature package. It does not import `@assemora/auth`,
+`@assemora/pages`, `@assemora/media`, `@assemora/resources`, `@assemora/http` or
+`@assemora/mcp`, and `pnpm boundaries` fails the build if it ever does.
+
+It gets the application by importing the *project's own code* at runtime through
+`assemora.config.ts`, and then asks it questions: `app.registry.describe()` for
+routes, models, resources, blocks, commands and queries, and
+`app.queries.execute('auth.agents.list', …)` for anything that is data rather than
+declaration. Listing agents therefore goes through the Query Bus, is authorized and is
+audited, exactly as it would be from Studio or from an agent. The CLI is one more
+client of the application layer (ADR-0021).
+
+Two things follow, and they are the honest cost rather than bugs. An application that
+cannot be constructed cannot be introspected: `assemora routes` boots the app, which
+means it also opens a database connection. And `assemora agents` is subject to
+policies — run it as nobody and it does not list nothing, it refuses, which is correct
+and will surprise somebody at least once. The refusal says so and names the flag:
+`--actor <id>` is how you say who is asking.
+
+The alternative was a CLI that parses the project's TypeScript, which would need a
+second implementation of what a model, a resource and a block are. The Schema Registry
+exists so that no subsystem keeps its own copy.
+
+## `assemora.config.ts`
+
+```ts
+import { defineConfig } from '@assemora/cli'
+
+export default defineConfig({
+  // How the CLI gets an application. It is NOT booted — the CLI boots it, once.
+  app: () => import('./src/app.ts').then((module) => module.createApp()),
+
+  // What `assemora dev` and `assemora start` run, relative to this file.
+  server: 'src/server.ts',
+
+  paths: {
+    source: 'src',
+    migrations: 'database/migrations',
+    generated: '.assemora/generated',
+  },
+
+  openapi: { out: 'openapi.json', info: { title: 'My project', version: '0.1.0' } },
+  sdk: { out: 'src/generated/sdk.ts' },
+})
+```
+
+`defineConfig` is identity plus types. It exists so the object is checked where it is
+written, which is the only place a mistake in it is cheap to fix.
+
+Every path is relative to the directory holding the config, so `assemora db:migrate`
+means the same thing typed from `src/` as from the root — the config is found by
+walking up from the working directory, `assemora.config.ts` first and then
+`assemora.config.js`. Node 24 strips TypeScript types natively, so a `.ts` config is
+imported directly: no transpiler, no dependency, and the file the developer edits is
+the file that runs.
+
+`app` hands back an application that has *not* been booted. The CLI boots it once per
+process, so two commands in one process — and `console`, which is many — share a
+single application and a single database pool.
+
+Everything is optional except `app`. `paths` defaults to the three values above;
+`api:openapi` falls back to `openapi.json` and takes its title and version from the
+project's `package.json`; `sdk:generate` falls back to `<source>/generated/sdk.ts`.
+
+## The commands
+
+Grouped as SPEC.md §77 groups them, which is how `assemora` with no arguments prints
+them.
+
+### Project
+
+| | |
+| --- | --- |
+| `assemora new <name>` | scaffold a new project |
+
+It calls `scaffold()` from `create-assemora` — the same code path as
+`pnpm create assemora`. This is the convenience, not a second implementation.
+
+### Run
+
+| | |
+| --- | --- |
+| `assemora dev` | run the server and restart it when a file changes |
+| `assemora build` | typecheck, regenerate what the config declares, run the project's build |
+| `assemora start` | run the server |
+
+`dev` and `start` spawn `node [--watch] <config.server>` under the same Node the CLI is
+running under, streaming its output, forwarding SIGINT, SIGTERM and SIGHUP and exiting
+with its code. Everything after `--` is node's: `assemora dev -- --inspect` runs
+`node --watch --inspect src/server.ts`.
+
+The child runs in a process group of its own and every signal is sent to that group,
+because `node --watch` is a wrapper and the server holding the port is its child — a
+signal delivered to the watcher alone would leave the server running with init for a
+parent. A second signal escalates to SIGKILL, on the group for the same reason.
+
+`build` is "everything that must be current before this is deployed", in three steps:
+a typecheck with the project's own TypeScript and its own `tsconfig.json` (skip it with
+`--no-typecheck`), then exactly what the config declares — by running `api:openapi` and
+`sdk:generate` rather than by generating anything itself — and then the project's own
+`build` script, if it declares one, with the package manager the project names. That
+script runs last because the generated SDK is an input to whatever bundles it.
+
+### Generate
+
+| | |
+| --- | --- |
+| `assemora make:model Post` | `src/models/post.ts` |
+| `assemora make:resource Post` | `src/resources/posts.ts` |
+| `assemora make:block hero` | `src/blocks/hero.ts` |
+| `assemora make:module blog` | `src/modules/blog.ts` |
+| `assemora make:command posts.publish` | `src/commands/publish-post.ts` |
+| `assemora make:policy posts` | `src/policies/posts.ts` |
+
+One file into `paths.source`, refusing to overwrite unless `--force`. `BlogPost`,
+`blog_post`, `blog-post` and `blogPost` produce a byte-identical file, so nobody has
+to remember which spelling the generator wanted.
+
+The path goes to stdout and the next step goes to stderr, so
+`assemora make:model Post` can be piped into an editor. What is generated compiles
+against the real APIs, and `make.test.ts` is what proves it: a generator that emits
+code the framework rejects is worse than no generator.
+
+### Database
+
+| | |
+| --- | --- |
+| `assemora db:generate [name] [--check] [--force]` | write a migration for everything the models changed |
+| `assemora db:migrate` | apply every migration that has not run yet |
+| `assemora db:rollback` | undo the most recently applied migration |
+| `assemora db:status` | list every migration and whether it is applied |
+
+`db:generate` diffs the snapshot at `<generated>/schema.json` against the booted
+application's model registry, writes `<migrations>/<NNNN>_<name>.sql` and moves the
+snapshot forward — in that order, so a snapshot never runs ahead of a migration that
+was not written. Every destructive change is printed as a warning naming the table and
+the column. `--check` writes nothing and exits `1` if a migration would be generated,
+which is what CI runs.
+
+The diff is taken against the snapshot rather than against a live database, so
+generation is deterministic, works offline, and produces the same migration for two
+developers whose databases have drifted. `db:status` is where drift against a real
+database is reported.
+
+A missing snapshot means "nothing has been created yet", which is true for the first
+migration and a lie once `<migrations>` holds one — the migration generated then
+re-creates every table and `db:migrate` fails on the first that already exists. So
+`db:generate` refuses that combination and names both files: the snapshot belongs in
+version control, and a checkout that received the migrations without it is the state to
+fix. `--force` diffs against an empty schema anyway, for a project whose migrations were
+written by hand and never had a snapshot.
+
+A pending migration that changes or destroys stored data needs `--force` outside
+development, and so does any rollback (SPEC.md §34). The CLI has `NODE_ENV` and
+nothing else to go on, so the question is answered the safe way round: `development`
+and `test` are development, and everything else — staging, a typo, an unset variable
+— is treated as production.
+
+#### The migration file format
+
+```sql
+-- 0002_add-sku
+-- Written by `assemora db:generate`. A comment beginning `-- +` is read back by
+-- `assemora db:migrate`; every other comment in this file is for you.
+-- +destructive drops column products.legacy_sku
+
+-- +migration up
+alter table "products" add column "sku" varchar(255);
+
+-- +migration down
+alter table "products" drop column "sku";
+```
+
+A plain `.sql` file, because the whole point of generating one is that a person reads
+it in a pull request before it ever reaches a database. One rule makes it both
+parseable and reviewable: **a comment beginning `-- +` is a directive, and every other
+comment is prose**. There are two directives — `+migration up` / `+migration down`
+open a section, and `+destructive <sentence>` is what `db:migrate` prints before it
+runs. A directive that is not recognised is refused rather than ignored, because a
+typo in `-- +migration down` would otherwise put a `drop` in the section that runs
+forwards.
+
+Statements are separated by `;`, exactly as anybody would write them, so the file is
+also runnable with `psql -f`. A semicolon inside a string, a quoted identifier or a
+dollar-quoted body is part of the statement rather than the end of it.
+
+The filename is `<number>_<name>.sql`. The number decides the order, so a file without
+one is refused rather than sorted somewhere arbitrary, and two files sharing a number
+— two branches that each generated `0004` — are refused by name rather than resolved
+by whatever order the filesystem offers. A file with no `-- +migration` marker at all
+is read as an `up` migration, which is what somebody who dropped a `.sql` file into
+the directory meant. A migration with no `down` section is refused by
+`db:rollback` by name, rather than quietly running nothing and marking itself undone.
+
+### Inspect
+
+| | |
+| --- | --- |
+| `assemora routes` | the HTTP routes this application registers |
+| `assemora models` | the models it declares, with their tables and relations |
+| `assemora resources` | the resources it declares, and the models behind them |
+| `assemora blocks` | the block types a page can be assembled from |
+| `assemora agents` | the agent identities this application knows |
+
+All five take `--json`, because the next thing anybody does with a listing is pipe it —
+and every log the booted application writes goes to stderr for the same reason, so what
+is on stdout is the answer and nothing else. `agents` additionally takes `--actor <id>`,
+`--page` and `--per-page`. An application built without `@assemora/auth` registers no
+`auth.agents.list`, and `agents` says that plainly rather than failing on an unknown
+query. A read the authorizer refuses names `--actor`, because running as nobody is the
+commonest way to meet that refusal and the authorizer has never heard of a flag.
+
+### Artifacts
+
+| | |
+| --- | --- |
+| `assemora api:openapi` | write the OpenAPI 3.1 document |
+| `assemora sdk:generate` | write the typed client |
+
+`--out <file>` beats the config, the config beats the default, and `--stdout` beats
+all three by naming no file at all — and writes nothing else, so it pipes.
+
+### Console
+
+| | |
+| --- | --- |
+| `assemora console` | open a REPL holding the booted application |
+
+`app`, `commands`, `queries` and `registry` are in scope, plus
+`as(actorId, operation)` which runs an operation inside a user context. There is no
+database handle in scope and this package could not obtain one: a mutation typed here
+passes validation, authorization, revisions and audit exactly as one typed anywhere
+else does. `.exit` closes the application, so the pool it opened goes with it.
+
+## Exit codes
+
+`0` succeeded, `1` the command failed, `2` the invocation was wrong — an unknown
+command, a missing argument, `--page two`. The distinction matters to a script: `2`
+says the arguments were nonsense and retrying will not help, while `1` says the work
+was attempted and did not finish.
+
+Errors print one clear sentence to stderr. `--debug` adds the stack and every cause
+below it.
+
+`run(argv)` returns the exit code and never calls `process.exit`, so the whole CLI is
+drivable from a test in-process. `bin.ts` is the only thing that ends the process, and
+it sets `process.exitCode` rather than exiting, so a piped listing is flushed rather
+than truncated mid-line.
+
+## Adding a command
+
+One `defineCommand` in the group that owns it, registered into the table in
+`registry.ts`. The help is printed from the table rather than written out beside it,
+so there is no second list to keep in step. A group reaches the table by being
+imported from `commands/index.ts`, and a group needing a heavy import —
+`@assemora/database-postgres` for `db:*`, the SDK generator for `sdk:generate` —
+reaches for it inside its handler rather than at the top of its module, so
+`assemora --help` stays instant.

package/bin.mjs

@@ -0,0 +1,31 @@
+#!/usr/bin/env node
+/**
+ * The file `assemora` is linked to.
+ *
+ * A package manager creates the executable when a package is *installed*, and `dist/`
+ * does not exist at that moment: it is gitignored and written by `pnpm build`, which
+ * runs afterwards. A `bin` pointing straight at `dist/bin.js` is therefore a link to
+ * nothing on a fresh clone — pnpm warns once and moves on, and every script that types
+ * `assemora` fails for the life of that checkout, which is how CI came to fail on a
+ * repository whose sources were fine.
+ *
+ * So the linked file is committed, and it loads the build. It is `.mjs` rather than
+ * TypeScript for the same reason `scripts/copy-templates.mjs` is: it has to run before
+ * this package has a build of its own.
+ *
+ * The build is looked for rather than caught. Catching `ERR_MODULE_NOT_FOUND` around
+ * the import would also swallow a missing dependency *inside* the CLI and report it as
+ * an unbuilt package, which is a worse lie than the error it replaces.
+ */
+import { existsSync } from 'node:fs'
+
+const compiled = new URL('./dist/bin.js', import.meta.url)
+
+if (existsSync(compiled)) {
+  await import(compiled.href)
+} else {
+  // `process.exitCode` rather than `process.exit()`, for the reason `src/bin.ts` gives:
+  // exiting outright truncates what is still being written.
+  process.stderr.write('assemora: @assemora/cli is not built. Run `pnpm build` first.\n')
+  process.exitCode = 1
+}

package/dist/args.d.ts

@@ -0,0 +1,35 @@
+/**
+ * argv, parsed by hand (SPEC.md §77).
+ *
+ * `node:util`'s `parseArgs` was the obvious alternative and it wants every option
+ * declared before the first token is read, so that it knows which ones take a value.
+ * The command table here is assembled by seven independent modules that know nothing
+ * about each other's flags (ADR-0021), so the parser has to work without that table.
+ * A third-party parser was never a candidate: the CLI is a framework's front door and
+ * has to install instantly, which is the same reason it has no dependencies at all.
+ */
+export type ParsedArgs = {
+    /** The first token that is not a flag — `make:model`, `db:migrate`, `routes`. */
+    readonly command: string | undefined;
+    /** Everything else that is not a flag, in order, with the command removed. */
+    readonly positionals: readonly string[];
+    /**
+     * Flags by their written name, `--dry-run` included: no camel-casing happens, so
+     * what a handler asks for is what the user typed. A repeated flag keeps the last
+     * value, because that is what a shell alias plus an override is meant to do.
+     */
+    readonly flags: Readonly<Record<string, string | boolean>>;
+    /** Everything after `--`, untouched. `dev` forwards it to node. */
+    readonly passthrough: readonly string[];
+};
+export declare const parseArgs: (argv: readonly string[]) => ParsedArgs;
+/**
+ * A flag's value, or the fallback.
+ *
+ * A flag written without a value has no string to give, so `--out --json` answers
+ * the fallback rather than the word `true`: a handler that wanted a path should ask
+ * for one, not receive a plausible-looking lie.
+ */
+export declare const flag: (args: ParsedArgs, name: string, fallback?: string) => string | undefined;
+export declare const bool: (args: ParsedArgs, name: string) => boolean;
+//# sourceMappingURL=args.d.ts.map

package/dist/args.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"args.d.ts","sourceRoot":"","sources":["../src/args.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAEH,MAAM,MAAM,UAAU,GAAG;IACvB,iFAAiF;IACjF,QAAQ,CAAC,OAAO,EAAE,MAAM,GAAG,SAAS,CAAA;IACpC,8EAA8E;IAC9E,QAAQ,CAAC,WAAW,EAAE,SAAS,MAAM,EAAE,CAAA;IACvC;;;;OAIG;IACH,QAAQ,CAAC,KAAK,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,GAAG,OAAO,CAAC,CAAC,CAAA;IAC1D,mEAAmE;IACnE,QAAQ,CAAC,WAAW,EAAE,SAAS,MAAM,EAAE,CAAA;CACxC,CAAA;AAmBD,eAAO,MAAM,SAAS,SAAU,SAAS,MAAM,EAAE,KAAG,UAgEnD,CAAA;AAED;;;;;;GAMG;AACH,eAAO,MAAM,IAAI,SAAU,UAAU,QAAQ,MAAM,aAAa,MAAM,KAAG,MAAM,GAAG,SAIjF,CAAA;AAKD,eAAO,MAAM,IAAI,SAAU,UAAU,QAAQ,MAAM,KAAG,OAOrD,CAAA"}

package/dist/args.js

@@ -0,0 +1,104 @@
+/**
+ * argv, parsed by hand (SPEC.md §77).
+ *
+ * `node:util`'s `parseArgs` was the obvious alternative and it wants every option
+ * declared before the first token is read, so that it knows which ones take a value.
+ * The command table here is assembled by seven independent modules that know nothing
+ * about each other's flags (ADR-0021), so the parser has to work without that table.
+ * A third-party parser was never a candidate: the CLI is a framework's front door and
+ * has to install instantly, which is the same reason it has no dependencies at all.
+ */
+/**
+ * Whether a token is a flag rather than a value.
+ *
+ * This is the whole answer to "how does `--out value` know that `value` is not the
+ * next flag": a token starting with `-` is a flag and never a value. `-` alone is a
+ * value, because that is what it conventionally means, and `-1` is a value too — no
+ * short flag is a digit, and `--limit -1` is far more common than a flag named `1`.
+ * Anything genuinely ambiguous is written `--flag=value`, which never guesses.
+ *
+ * The price of having no option table is that a value-taking flag written *before*
+ * the command would swallow it: `assemora --out x routes` leaves no command behind.
+ * Flags follow the command — which is how the help prints every usage line, and how
+ * anybody types it — so the case is documented rather than guessed at.
+ */
+const isFlagToken = (token) => token !== undefined && token.length > 1 && token.startsWith('-') && !/^-\d/.test(token);
+export const parseArgs = (argv) => {
+    const positionals = [];
+    const flags = {};
+    let passthrough = [];
+    let index = 0;
+    while (index < argv.length) {
+        const token = argv[index];
+        index += 1;
+        if (token === undefined)
+            continue;
+        // The first `--` ends the parse. A second one is somebody else's argument.
+        if (token === '--') {
+            passthrough = argv.slice(index);
+            break;
+        }
+        if (!isFlagToken(token)) {
+            positionals.push(token);
+            continue;
+        }
+        const long = token.startsWith('--');
+        const body = token.slice(long ? 2 : 1);
+        const separator = body.indexOf('=');
+        if (separator >= 0) {
+            const name = body.slice(0, separator);
+            // `--=value` names nothing; treat it as text rather than inventing an empty key.
+            if (name === '')
+                positionals.push(token);
+            else
+                flags[name] = body.slice(separator + 1);
+            continue;
+        }
+        // A cluster is `-fj`, and only its last letter can take the following value —
+        // the earlier letters have nowhere to put one.
+        const names = long ? [body] : [...body];
+        const last = names.length - 1;
+        names.forEach((name, position) => {
+            if (position < last) {
+                flags[name] = true;
+                return;
+            }
+            const next = argv[index];
+            if (next !== undefined && !isFlagToken(next)) {
+                flags[name] = next;
+                index += 1;
+            }
+            else {
+                flags[name] = true;
+            }
+        });
+    }
+    return {
+        command: positionals[0],
+        positionals: positionals.slice(1),
+        flags,
+        passthrough,
+    };
+};
+/**
+ * A flag's value, or the fallback.
+ *
+ * A flag written without a value has no string to give, so `--out --json` answers
+ * the fallback rather than the word `true`: a handler that wanted a path should ask
+ * for one, not receive a plausible-looking lie.
+ */
+export const flag = (args, name, fallback) => {
+    const value = args.flags[name];
+    return typeof value === 'string' ? value : fallback;
+};
+/** What a scripted `--force=$SOMETHING` means when `$SOMETHING` is empty or a denial. */
+const DENIALS = new Set(['', 'false', '0', 'no', 'off']);
+export const bool = (args, name) => {
+    const value = args.flags[name];
+    if (value === undefined)
+        return false;
+    if (typeof value === 'boolean')
+        return value;
+    return !DENIALS.has(value.toLowerCase());
+};
+//# sourceMappingURL=args.js.map

package/dist/args.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"args.js","sourceRoot":"","sources":["../src/args.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAiBH;;;;;;;;;;;;;GAaG;AACH,MAAM,WAAW,GAAG,CAAC,KAAyB,EAAW,EAAE,CACzD,KAAK,KAAK,SAAS,IAAI,KAAK,CAAC,MAAM,GAAG,CAAC,IAAI,KAAK,CAAC,UAAU,CAAC,GAAG,CAAC,IAAI,CAAC,MAAM,CAAC,IAAI,CAAC,KAAK,CAAC,CAAA;AAEzF,MAAM,CAAC,MAAM,SAAS,GAAG,CAAC,IAAuB,EAAc,EAAE;IAC/D,MAAM,WAAW,GAAa,EAAE,CAAA;IAChC,MAAM,KAAK,GAAqC,EAAE,CAAA;IAClD,IAAI,WAAW,GAAsB,EAAE,CAAA;IAEvC,IAAI,KAAK,GAAG,CAAC,CAAA;IAEb,OAAO,KAAK,GAAG,IAAI,CAAC,MAAM,EAAE,CAAC;QAC3B,MAAM,KAAK,GAAG,IAAI,CAAC,KAAK,CAAC,CAAA;QACzB,KAAK,IAAI,CAAC,CAAA;QAEV,IAAI,KAAK,KAAK,SAAS;YAAE,SAAQ;QAEjC,2EAA2E;QAC3E,IAAI,KAAK,KAAK,IAAI,EAAE,CAAC;YACnB,WAAW,GAAG,IAAI,CAAC,KAAK,CAAC,KAAK,CAAC,CAAA;YAC/B,MAAK;QACP,CAAC;QAED,IAAI,CAAC,WAAW,CAAC,KAAK,CAAC,EAAE,CAAC;YACxB,WAAW,CAAC,IAAI,CAAC,KAAK,CAAC,CAAA;YACvB,SAAQ;QACV,CAAC;QAED,MAAM,IAAI,GAAG,KAAK,CAAC,UAAU,CAAC,IAAI,CAAC,CAAA;QACnC,MAAM,IAAI,GAAG,KAAK,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAA;QACtC,MAAM,SAAS,GAAG,IAAI,CAAC,OAAO,CAAC,GAAG,CAAC,CAAA;QAEnC,IAAI,SAAS,IAAI,CAAC,EAAE,CAAC;YACnB,MAAM,IAAI,GAAG,IAAI,CAAC,KAAK,CAAC,CAAC,EAAE,SAAS,CAAC,CAAA;YACrC,iFAAiF;YACjF,IAAI,IAAI,KAAK,EAAE;gBAAE,WAAW,CAAC,IAAI,CAAC,KAAK,CAAC,CAAA;;gBACnC,KAAK,CAAC,IAAI,CAAC,GAAG,IAAI,CAAC,KAAK,CAAC,SAAS,GAAG,CAAC,CAAC,CAAA;YAC5C,SAAQ;QACV,CAAC;QAED,8EAA8E;QAC9E,+CAA+C;QAC/C,MAAM,KAAK,GAAG,IAAI,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC,CAAC,GAAG,IAAI,CAAC,CAAA;QACvC,MAAM,IAAI,GAAG,KAAK,CAAC,MAAM,GAAG,CAAC,CAAA;QAE7B,KAAK,CAAC,OAAO,CAAC,CAAC,IAAI,EAAE,QAAQ,EAAE,EAAE;YAC/B,IAAI,QAAQ,GAAG,IAAI,EAAE,CAAC;gBACpB,KAAK,CAAC,IAAI,CAAC,GAAG,IAAI,CAAA;gBAClB,OAAM;YACR,CAAC;YAED,MAAM,IAAI,GAAG,IAAI,CAAC,KAAK,CAAC,CAAA;YAExB,IAAI,IAAI,KAAK,SAAS,IAAI,CAAC,WAAW,CAAC,IAAI,CAAC,EAAE,CAAC;gBAC7C,KAAK,CAAC,IAAI,CAAC,GAAG,IAAI,CAAA;gBAClB,KAAK,IAAI,CAAC,CAAA;YACZ,CAAC;iBAAM,CAAC;gBACN,KAAK,CAAC,IAAI,CAAC,GAAG,IAAI,CAAA;YACpB,CAAC;QACH,CAAC,CAAC,CAAA;IACJ,CAAC;IAED,OAAO;QACL,OAAO,EAAE,WAAW,CAAC,CAAC,CAAC;QACvB,WAAW,EAAE,WAAW,CAAC,KAAK,CAAC,CAAC,CAAC;QACjC,KAAK;QACL,WAAW;KACZ,CAAA;AACH,CAAC,CAAA;AAED;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,IAAI,GAAG,CAAC,IAAgB,EAAE,IAAY,EAAE,QAAiB,EAAsB,EAAE;IAC5F,MAAM,KAAK,GAAG,IAAI,CAAC,KAAK,CAAC,IAAI,CAAC,CAAA;IAE9B,OAAO,OAAO,KAAK,KAAK,QAAQ,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,QAAQ,CAAA;AACrD,CAAC,CAAA;AAED,yFAAyF;AACzF,MAAM,OAAO,GAAG,IAAI,GAAG,CAAC,CAAC,EAAE,EAAE,OAAO,EAAE,GAAG,EAAE,IAAI,EAAE,KAAK,CAAC,CAAC,CAAA;AAExD,MAAM,CAAC,MAAM,IAAI,GAAG,CAAC,IAAgB,EAAE,IAAY,EAAW,EAAE;IAC9D,MAAM,KAAK,GAAG,IAAI,CAAC,KAAK,CAAC,IAAI,CAAC,CAAA;IAE9B,IAAI,KAAK,KAAK,SAAS;QAAE,OAAO,KAAK,CAAA;IACrC,IAAI,OAAO,KAAK,KAAK,SAAS;QAAE,OAAO,KAAK,CAAA;IAE5C,OAAO,CAAC,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,WAAW,EAAE,CAAC,CAAA;AAC1C,CAAC,CAAA"}

package/dist/bin.d.ts

@@ -0,0 +1,3 @@
+#!/usr/bin/env node
+export {};
+//# sourceMappingURL=bin.d.ts.map

package/dist/bin.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"bin.d.ts","sourceRoot":"","sources":["../src/bin.ts"],"names":[],"mappings":""}