@endora-commerce/cli 0.100.0

package/dist/new-instance/template.d.ts

@@ -0,0 +1,505 @@
+/**
+ * The tree `endora new instance` writes — one plan, three kinds of file, and a
+ * rule that refuses a fourth (`contracts/instance-tree.md` §1, §2).
+ *
+ * ## R1.1 and R1.2 are the whole design
+ *
+ * Every file here carries its {@link FileKind}, and the kind is what decides
+ * whether it may exist at all:
+ *
+ *   * **the client's own** — a value only they can supply, or code they will
+ *     edit. Written once, never regenerated, never read by us again.
+ *   * **wiring** — the smallest expression that hands the platform something it
+ *     cannot derive: a database handle, a root directory, a process's argv.
+ *     Bounded by R1.4 and counted by {@link wiringLineCount}.
+ *   * **derived** — rendered from a fact the platform or the module set already
+ *     holds.
+ *
+ * **A file that is none of the three may not be written** (R1.2), which is the
+ * rule that refuses the fork one file at a time: a composition root is not the
+ * client's (it is ours), is not wiring (it is 2 628 lines), and is not derived
+ * (nothing generates it). The kind is a field on every entry rather than a
+ * comment, so T139's T4 can assert it over the plan the command actually
+ * builds.
+ *
+ * ## Nothing is copied, so nothing is rewritten
+ *
+ * R1.3 / R5.5 / NFR-002. `endora new storefront` copies a reference tree and
+ * rewrites every declaration that names something above it; this command copies
+ * nothing, so there is no `rewrite.ts` beside this file and there must never be
+ * one — its appearance would be evidence that something was copied that should
+ * not have been. Every string below is rendered from the resolved packages, the
+ * CLI's own manifest and the operator's own flags.
+ *
+ * ## No demo artefact, at any tier (D-216)
+ *
+ * *"A client scaffolding an instance for their own trading receives no demo
+ * artefact in a tree they own: no composition, no script, no example and no
+ * placeholder. Silence means no."* Nothing here writes one, and the capability
+ * is discoverable through the next-steps block rather than reported as an
+ * omission — a capability announced as a deficiency is not optional.
+ *
+ * ## What this build cannot yet write, said here rather than discovered
+ *
+ * The backend member's wiring names symbols on the platform's declared
+ * subpaths — `./composition`, `./db`, `./lifecycle`, `./overlay` and
+ * `./packages` today. **How many symbols that is is not written here** (D-100): the
+ * reconciliation test derives it from the barrels on every run and prints it,
+ * and the count in this sentence was already wrong when the three names below
+ * were wrong. `composeApp` is one of them since T118 — the
+ * position §2.3 stated (*"`composeApp` is imported, never written (R1.2)"*) is
+ * met, and the file below supplies the one argument that composition takes:
+ * `deploymentRoot`, the directory holding `apps/`, which no package can derive
+ * because in an instance the platform came out of `node_modules`
+ * (`contracts/application-root-supplier.md` R1.1). **No contribute callback is
+ * supplied and there is nowhere in this tree to write one** — R2.4 — so a
+ * client's instance contributes over no name a module defaults.
+ *
+ * The ORM configuration below is the one place an instance restates its own
+ * artefacts, and it has none, so the platform's `*From` factories answer over
+ * the packages it installed: `configuredEntitiesFrom`,
+ * `discoverConfiguredMigrations` and `mikroOrmConfigFrom` on `./db`, and
+ * `resolveManifestEntries` on `./lifecycle` with its three suppliers.
+ *
+ * **That sentence used to name three other symbols, and nothing held this file
+ * to it.** It read *"`configuredMigrations`, `configuredEntities` and
+ * `resolvedManifestEntries` are `./db`'s and `./lifecycle`'s **under other
+ * names**"* — a doc block describing the repair, beside rendered text that had
+ * never taken it, so a scaffolded backend did not compile and the knowledge was
+ * present the whole time. The guard is
+ * `test/new-instance/template-reconciliation.test.ts`' T1, at **symbol**
+ * granularity rather than subpath: `./composition` and `./lifecycle` are both
+ * declared subpaths, so a reconciliation of the specifier alone passes over all
+ * three errors.
+ *
+ * §2.3's sixth wiring file, `backend/src/cli.ts`, **is** written since
+ * `specs/123-oss-install-experience/` G2, and the omission that stood in its
+ * place is deleted rather than reworded. Its reason was *"the demo layer around
+ * it is exported under no subpath"*, and what discharged it was not a wider
+ * `exports` map: `backend/src/cli/demo-command.ts` moved into
+ * `<scope>platform/demo` — where `test/unit/kernel/host-residue-partition.test.ts`
+ * had it ledgered as platform-shaped residue all along — and the dispatch around
+ * both halves became `<scope>platform/cli`'s `runCli`. So the file this command
+ * renders names nothing it had to invent, holds no copy of the 479 lines it
+ * calls (D-207), and is five lines.
+ *
+ * The cost of the omission was measured rather than aesthetic: with no CLI, a
+ * scaffolded instance could run no `admin_users create`, so the admin bundle A5
+ * and A13 prove is built and styled had nobody to log in as.
+ */
+import { type EnvironmentInput } from '@endora-commerce/contracts';
+import { type InstanceBuildInput } from '../lib/instance-build-inputs.js';
+import { type Topology } from './deploy.js';
+/** §1.1's three kinds, and there is no fourth. */
+export type FileKind = 'client' | 'wiring' | 'derived';
+/** Which member of the workspace a file belongs to, or the workspace root. */
+export type MemberName = 'root' | 'deployment' | 'backend' | 'admin' | 'docs';
+/** One workspace member an operator can name, and what a person is told about it. */
+export interface MemberDeclaration {
+    /** The `--without` name, and the directory the member is written into. */
+    readonly name: 'backend' | 'admin' | 'docs';
+    /** One line, for a human choosing which parts of an instance they want. */
+    readonly describes: string;
+    /**
+     * Why the member cannot be declined, or `null` when it can.
+     *
+     * A sentence rather than a boolean because the one place this is read with a
+     * human in front of it — the install wizard's checklist — renders the reason
+     * instead of a checkbox that refuses when unchecked (125 FR-152).
+     */
+    readonly fixed: string | null;
+}
+/**
+ * The members this template writes, and therefore the whole `--without`
+ * vocabulary (`specs/118-instance-member-selection/contracts/instance-members.md`
+ * R3.5a, ruled by D-215).
+ *
+ * **This is the one statement of the member set**, and two consumers read it:
+ * the refusal below, and `endora install`'s checklist (125 R6.3a), which
+ * renders one row per entry and holds no list of its own. A member the template
+ * gains is added here, beside the decision that writes it, and reaches both —
+ * `test/new-instance-members.test.ts` fails when a planned member has no entry.
+ */
+export declare const MEMBER_VOCABULARY: readonly MemberDeclaration[];
+/**
+ * F10 and F11 (`instance-members.md` §5.6), decided over the names alone — the
+ * refusal sentence, or `null` when every name is one this template can decline.
+ *
+ * Exported because two commands validate the same flag before either writes:
+ * `endora new instance`, and `endora install`, which reports it together with
+ * every other precondition (125 FR-157) rather than one refusal later.
+ */
+export declare function memberRefusal(without: readonly string[]): string | null;
+/** One file the command would write. */
+export interface PlannedFile {
+    /** Relative to the target directory, with `/` separators. */
+    readonly path: string;
+    readonly kind: FileKind;
+    readonly member: MemberName;
+    readonly content: string;
+}
+/**
+ * One module package the instance declares — and **its own** version beside its
+ * own name.
+ *
+ * The version travels on the same record as the name deliberately. It used to
+ * be absent, and the site that writes the `dependencies` entries had exactly one
+ * version in scope — the platform's — so every module was declared at it. That
+ * is only correct while a release moves every package together, and a release
+ * does not: of the packages this repository published on 2026-09-11, 68 moved to
+ * `0.8.0` and 15 to `0.7.1`, so a scaffolded instance asked a registry for
+ * `@endora-commerce/mod-addresses@^0.8.0` and was told the latest is `0.7.1`.
+ * Nothing in the estate makes a release uniform and nothing should: D-225 owns
+ * the series, and 15 packages genuinely had only patch-level changes.
+ *
+ * A caret range over a version a **different** package declares is not a value
+ * this command may invent (R2.5a), and it is the one such value that fails at
+ * the client's first `pnpm install` rather than in anything we run.
+ */
+export interface PlannedModulePackage {
+    /** The module id, which is what `--module` names and what orders the entries. */
+    readonly id: string;
+    /** The npm name, verbatim — this is the `dependencies` key. */
+    readonly packageName: string;
+    /**
+     * The version **this package** declares about itself, read off the manifest
+     * of the package the run resolved beside the target directory.
+     */
+    readonly version: string;
+}
+/** A member this run did not write, and every reason that holds (D-215 §4). */
+export interface PlannedOmission {
+    readonly path: string;
+    readonly reason: string;
+}
+/** The whole plan, decided before anything is written (R5.2). */
+export interface InstancePlan {
+    readonly files: readonly PlannedFile[];
+    readonly omitted: readonly PlannedOmission[];
+    /** The workspace members whose directories this run writes. */
+    readonly members: readonly MemberName[];
+    /** The registry `--registry` named, normalised, or `null`. */
+    readonly registry: string | null;
+    /** Every dependency the root manifest declares, name to range. */
+    readonly dependencies: ReadonlyMap<string, string>;
+}
+/** Everything the plan is rendered from. Pure in, pure out. */
+export interface PlanInput {
+    /** The workspace name, from the target directory's basename. */
+    readonly name: string;
+    readonly deployment: string;
+    readonly scope: string;
+    /**
+     * The platform package's own version. It ranges the **platform** entry and
+     * nothing else — see {@link PlannedModulePackage} for what happened the last
+     * time it ranged something else.
+     */
+    readonly platformVersion: string;
+    readonly enginesNode: string;
+    readonly packageManager: string | undefined;
+    /** The resolved module set, each entry carrying its own version. */
+    readonly modules: readonly PlannedModulePackage[];
+    /** `null` when the admin shell does not resolve at the version being installed. */
+    readonly adminShellVersion: string | null;
+    /** `null` when the admin design system does not resolve. §2.4's other package. */
+    readonly adminKitVersion: string | null;
+    /**
+     * The ranges the admin member's own build tools are written from, each read
+     * off the admin shell's manifest rather than chosen here (R2.5a).
+     *
+     * `react` and `react-dom` are its `peerDependencies` — what a host that
+     * mounts the shell must resolve — and `vite`, `@vitejs/plugin-react`,
+     * `tailwindcss` and `@tailwindcss/vite` are the optional peers by which the
+     * shell states what kind of application a host is. A name with no range here
+     * is **not written and not guessed**: the member is omitted, naming it, for
+     * the same reason `devDependenciesFor` leaves one out.
+     */
+    readonly adminRanges: ReadonlyMap<string, string>;
+    /**
+     * The packages the admin project must supply because what it composes
+     * declares them **optional** — name to range, already resolved.
+     *
+     * `index.ts`' `composedOptionalPeers` is the derivation and carries the
+     * argument: `manifests:generate` marks a peer optional exactly when only a UI
+     * layer reaches it, so for a project that renders those UI layers the set is
+     * not optional but **required**, and it is the one statement in either tree of
+     * what an admin host has to have.
+     */
+    readonly adminPeers: ReadonlyMap<string, string>;
+    /** The CLI's own version — `endora generate` is what renders §2.6's artefacts. */
+    readonly cliVersion: string;
+    /**
+     * The ranges the documentation member is written from — name to range, read
+     * off the CLI's own manifest (R2.3's first named source, and R2.5a).
+     *
+     * `@docusaurus/core` and `@docusaurus/preset-classic` are the CLI's **optional
+     * peers**, which is the same declaration the admin shell makes about a host
+     * that mounts it: *"an application of this kind resolves these"*. The CLI
+     * renders this site's navigation and imports neither package, exactly as the
+     * shell declares `vite` and `tailwindcss` and imports neither. A name with no
+     * range here is **not written and not guessed**: the member is omitted,
+     * naming it.
+     */
+    readonly docsRanges: ReadonlyMap<string, string>;
+    /**
+     * The ranges the instance's own `devDependencies` are derived from, each read
+     * off a manifest this run resolved rather than chosen here (R2.5a).
+     *
+     * The four peers and `ioredis` come from `@endora-commerce/platform`'s own
+     * `peerDependencies` and `dependencies`; `typescript` comes from the CLI's own
+     * manifest, which R2.3 names as a source. A package with no such source is not
+     * written — see {@link devDependenciesFor}.
+     */
+    readonly declaredRanges: ReadonlyMap<string, string>;
+    /** Already normalised by the caller; `null` writes no `.npmrc`. */
+    readonly registry: string | null;
+    /** The `.npmrc` text, when there is a registry. Written by `npmrc.ts` (R5.7). */
+    readonly npmrc: string | null;
+    /**
+     * Which machine layout the `deploy/` examples describe (D-230).
+     *
+     * It selects and records nothing: no file this command writes carries the
+     * value, and nothing reads one back. `deploy.ts` is where the derivation and
+     * that rule both live.
+     */
+    readonly topology: Topology;
+    /**
+     * The members the operator declined with `--without` (D-215, 118 R3.5).
+     *
+     * Optional, and absent is the empty set: the subtractive default is
+     * *everything*, so a caller that says nothing about members gets every member
+     * this build can write. Already validated by {@link memberRefusal}.
+     */
+    readonly without?: ReadonlySet<string> | undefined;
+    /**
+     * What this instance reads from its environment — the platform's declaration
+     * unioned with the manifests of the modules it installs
+     * (`modules.ts`' `instanceEnvironmentInputs`).
+     *
+     * It is a **parameter** rather than a constant for the reason every other
+     * version and range here is: the declaration belongs to the packages the
+     * client's machine resolved, not to this CLI, and a list compiled in here
+     * could never see a module a client installed from a registry (D-100, R2.3).
+     */
+    readonly declared: readonly EnvironmentInput[];
+    /**
+     * The text of a `.env` the operator placed in the target directory before
+     * running, or `''`.
+     *
+     * Tier 2 (`input-resolution.md` R1.2), and it reaches the plan rather than the
+     * writer so that `--dry-run` reports the file it would actually produce. What
+     * the operator wrote is merged into and never rewritten: their comments, their
+     * ordering and their own keys survive.
+     */
+    readonly existingEnv: string;
+    /**
+     * The secrets this run generated, name to value (R2.5d).
+     *
+     * They arrive already generated because the plan is pure and a plan that
+     * called `randomBytes` would render a different tree on every call — which
+     * `--dry-run`'s whole purpose is to rule out. The caller generates once and
+     * reports the names in the provenance line.
+     */
+    readonly generated: ReadonlyMap<string, string>;
+}
+/**
+ * A workspace name a client can actually install.
+ *
+ * npm's own rule, applied to the basename the operator chose, and **refused**
+ * rather than sanitised: a command that quietly renamed the directory the
+ * operator named would put a name nobody chose into the file that is the
+ * module list (R1.2 there).
+ */
+export declare function assertWorkspaceName(name: string): void;
+/**
+ * The deployment name, which is `DEPLOYMENT`'s value and nothing else reads it
+ * (§2.2).
+ *
+ * F4. It is a directory name under `apps/`, so the refusal is about what a
+ * directory name may be: no separator, no traversal, no leading dot.
+ */
+export declare function assertDeploymentName(deployment: string): void;
+/**
+ * The derived artefacts an instance generates and commits none of (§2.6,
+ * `instance-repository.md` R3.2).
+ *
+ * **There are three and this list carried two** until T138 wrote the admin
+ * member. `admin/src/tailwind.generated.css` arrived with T124 on the same day
+ * this command landed, R3.2 already said three, and `new-instance.test.ts`'
+ * *"both generated artefacts are git-ignored"* asserted the stale count rather
+ * than catching it. A committed stylesheet enumeration is the tree and the
+ * install disagreeing about which packages were scanned — which is silent, and
+ * is the whole failure `admin-stylesheet-composition.md` exists for.
+ *
+ * **The fourth is the entity index** (`specs/109-backend-test-kit/` T065), and it
+ * is the first entry here that belongs to **no member**: its consumer is a test,
+ * and a test is not a member of a client's workspace. It is in this list for the
+ * one reason the list exists — `.gitignore` has to cover it — and it is
+ * `.gitignore`d for §2.6's own predicate: which modules a host installed is a
+ * fact about the install, so a committed index is the tree and the install
+ * disagreeing about which tables exist.
+ */
+export declare const GENERATED_ARTEFACTS: readonly ["admin/src/modules.generated.ts", "admin/src/tailwind.generated.css", "docs/sidebars.modules.generated.js", "backend/test/entities.generated.ts"];
+/**
+ * The generated **trees** — a whole directory the generator owns, rather than a
+ * file it writes.
+ *
+ * They are apart from {@link GENERATED_ARTEFACTS} because the two answer
+ * different questions: that list is the files a reconciliation can name and
+ * compare, this one is what `.gitignore` has to cover. The documentation half
+ * of §2.6 is a *population* rather than a file — one copied page per page a
+ * module ships, one reference page per module, and the stamp that lets a run
+ * undo the previous one's copies — so a client's `.gitignore` names the
+ * directories and git's own "a tracked file is never ignored" keeps a page they
+ * write themselves visible with no exception list to maintain.
+ */
+export declare const GENERATED_TREES: readonly ["docs/docs/modules/**", "docs/docs/module-reference/**", "docs/.module-docs-copies.json"];
+/**
+ * The named CLI aliases an instance's manifests earn
+ * (`specs/123-oss-install-experience/` T2-D).
+ *
+ * **Derived, never written.** `cli` is the pass-through and covers every
+ * command any installed module declares; what a named alias buys on top of it
+ * is that an operator reads it in `pnpm run`, and an alias addressing a module
+ * this instance did not install would fail with `unknown module` at the one
+ * moment a client is least able to tell a missing module from a broken CLI.
+ *
+ * **There is deliberately no `demo:seed` or `demo:reset` entry**, and
+ * `specs/123-oss-install-experience/` T2-D asked for both. D-216 is more
+ * specific than the task and is the owner's: *"a client scaffolding an instance
+ * for their own trading receives no demo artefact in a tree they own: no
+ * composition, **no script**, no example and no placeholder"* — and it names
+ * where the capability does belong, which is the next-steps block. `cli` reaches
+ * both verbs anyway (`pnpm run cli demo seed`), so nothing is unavailable; what
+ * is refused is a line in a client's manifest they did not ask for.
+ */
+export declare function cliAliasesFor(modules: readonly PlannedModulePackage[]): readonly (readonly [string, string])[];
+/**
+ * The backend member's scripts, every one of them reading the instance's own
+ * `.env` (`specs/123-oss-install-experience/` G3).
+ *
+ * **`--env-file-if-exists=../.env`, and the `..` is the whole of it.** Every
+ * root script is `pnpm -C backend run …`, so these run with `backend/` as the
+ * working directory while the `.env` a client is told to fill in sits at the
+ * root of the tree beside `.env.example` and beside the `.env` entry in
+ * `.gitignore`. Without the prefix the file is inert: a client fills it in, runs
+ * `pnpm run migrate`, and the process reads nothing at all — which is the second
+ * half of the defect the acceptance criterion papers over by supplying the
+ * values through `process.env` instead.
+ *
+ * `-if-exists` rather than `--env-file`, because a `.env` is not obligatory: a
+ * container-hosted instance is configured entirely from its process environment,
+ * and a flag that refused to start without the file would break exactly the
+ * deployment `deploy/compose.prod.yml` describes. A value already in the
+ * environment wins over the file, which is Node's own precedence and the one an
+ * operator expects.
+ *
+ * It is one function rather than a spelling repeated ten times, so a script
+ * added later cannot be the one that silently does not read the file.
+ */
+export declare function backendScripts(input: PlanInput): Record<string, string>;
+/** Lines of wiring in a plan — R1.4's bound, measured rather than intended. */
+export declare function wiringLineCount(plan: InstancePlan): number;
+/**
+ * The environment inputs a client is asked to fill in, in declaration order.
+ *
+ * Two exclusions, and both are rules rather than names. A **generable secret**
+ * is written into the `.env` this command produces and appears in no
+ * `.env.example` (R2.5d), so asking for it would be asking for a value the tool
+ * has already supplied. And an input **no written member reads** is out of the
+ * population (118).
+ */
+export declare function declaredEnvironmentInputs(declared: readonly EnvironmentInput[], admin: boolean): readonly EnvironmentInput[];
+/** The generable secrets this run owes a value for, in declaration order. */
+export declare function generableEnvironmentInputs(declared: readonly EnvironmentInput[], admin: boolean): readonly EnvironmentInput[];
+/**
+ * `.env.example` — every input this instance actually reads (FR-010).
+ *
+ * **Two populations, and keeping them apart is the point.** The build inputs are
+ * inlined into an artefact by `docker build`; the declared inputs are read by a
+ * process on every start. An operator who conflates them rebuilds an image to
+ * change a password. They are two headed sections of one file rather than two
+ * files because a client fills in one `.env`, and a second example beside the
+ * first is a second thing to forget.
+ *
+ * Neither section is a list. The first is `INSTANCE_BUILD_INPUTS`; the second is
+ * the platform's declaration unioned with the manifests of the modules this run
+ * installed, scoped to the members it wrote. The defect it closes is the
+ * acceptance criterion's own note — *"its `.env.example` declares none of them,
+ * so a client who fills in the file the command wrote has nothing to put them
+ * in"* — and the note is deleted in the same merge request, because an
+ * instrument that reports a gap must not outlive it.
+ */
+export declare function envExample(inputs: readonly InstanceBuildInput[], declared: readonly EnvironmentInput[], admin: boolean): string;
+/**
+ * The `.env` this command writes — the generated secrets, and a blank for
+ * everything else the instance reads.
+ *
+ * R2.5d: a generated secret is written **where the operator can read it**,
+ * change it and copy it into a secret store. The placeholders are there so that
+ * the file a client edits is the file their instance reads: telling them to
+ * `cp .env.example .env` after this command has already written one would have
+ * them overwrite the generated secrets with empty strings, and the boot that
+ * then failed would name none of this.
+ *
+ * **Every placeholder is commented out, and that is not cosmetic.** A blank
+ * assignment is not the same state as no assignment: Node's `--env-file` reads
+ * `MEILISEARCH_URL=` as the empty string, and the platform's `??` fallbacks
+ * treat an empty string as a value. Measured on the instance acceptance
+ * criterion — a `.env` listing every optional input as a blank turned twenty
+ * "unset"s into twenty empty strings and the health route answered **503** over
+ * a search engine that was running. So the file lists what there is to fill in
+ * and changes nothing until a client removes a `#`, and {@link writeEnvFile}
+ * fills a placeholder in place rather than appending a second assignment.
+ *
+ * A `.env` the operator placed here first is **merged into, never rewritten**:
+ * their comments, their ordering and their own keys survive, and a value they
+ * already supplied is not generated over.
+ */
+export declare function envFile(input: PlanInput, admin: boolean): string;
+/**
+ * The plan. Nothing here touches the filesystem, so `--dry-run` reports exactly
+ * what a real run writes rather than a second derivation of it (R5.3).
+ */
+export declare function planInstance(input: PlanInput): InstancePlan;
+/**
+ * The packages the instance builds with, each range read off a manifest this
+ * run resolved (§2.1, R2.5a).
+ *
+ * `instance-tree.md` §2.1 names the set — *"the platform's four peers plus
+ * `@mikro-orm/migrations`, `tsx`, `typescript`"* — and says nothing about where
+ * the **ranges** come from, which is the question R2.5a answers: a value with
+ * no source is one the command would have to invent. So each is derived:
+ *
+ *   * the four peers, from `@endora-commerce/platform`'s own
+ *     `peerDependencies`. A platform that widens `zod` to `^5` widens this in
+ *     the same run, with nothing here to edit.
+ *   * `@mikro-orm/migrations`, from the range the platform declares for
+ *     `@mikro-orm/core`. The MikroORM packages version in lockstep and a
+ *     migrator from another major does not load the driver from this one.
+ *   * `ioredis`, from the platform's own `dependencies`. It is not in §2.1's
+ *     list and it is not optional: the five operator commands construct the
+ *     `OperatorResources` the platform asks them for, and one of its three
+ *     members is a Redis connection.
+ *   * `typescript`, from the CLI's own manifest — R2.3's first named source.
+ *
+ * **`tsx` is deliberately absent.** No manifest this run can read declares a
+ * range for it, so writing one would be the invention R2.5a forbids; the
+ * member's `dev` script uses `tsc` and `node --watch`, which need nothing that
+ * is not already here.
+ */
+export declare function devDependenciesFor(input: PlanInput, 
+/**
+ * Does this instance have an artefact to generate at all?
+ *
+ * The root's `generate` script is `endora generate` — one run renders every
+ * member's artefacts — so the binary has to be on the **root's** path. An
+ * instance with no artefact family at all has no `generate` script, and
+ * declaring the tool that runs it would be a dependency with nothing to do.
+ *
+ * The caller's predicate is `planInstance`'s `generatesArtefacts`, which since
+ * T065 counts the entity index: a headless instance with a module installed
+ * does have something to render, so it does get the tool.
+ */
+generates?: boolean): readonly (readonly [string, string])[];
+//# sourceMappingURL=template.d.ts.map

package/dist/new-instance/template.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"template.d.ts","sourceRoot":"","sources":["../../src/new-instance/template.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAwFG;AACH,OAAO,EAIL,KAAK,gBAAgB,EACtB,MAAM,4BAA4B,CAAC;AAGpC,OAAO,EAAyB,KAAK,kBAAkB,EAAE,MAAM,iCAAiC,CAAC;AACjG,OAAO,EAKL,KAAK,QAAQ,EACd,MAAM,aAAa,CAAC;AAGrB,kDAAkD;AAClD,MAAM,MAAM,QAAQ,GAAG,QAAQ,GAAG,QAAQ,GAAG,SAAS,CAAC;AAEvD,8EAA8E;AAC9E,MAAM,MAAM,UAAU,GAAG,MAAM,GAAG,YAAY,GAAG,SAAS,GAAG,OAAO,GAAG,MAAM,CAAC;AAE9E,qFAAqF;AACrF,MAAM,WAAW,iBAAiB;IAChC,0EAA0E;IAC1E,QAAQ,CAAC,IAAI,EAAE,SAAS,GAAG,OAAO,GAAG,MAAM,CAAC;IAC5C,2EAA2E;IAC3E,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAC;IAC3B;;;;;;OAMG;IACH,QAAQ,CAAC,KAAK,EAAE,MAAM,GAAG,IAAI,CAAC;CAC/B;AAED;;;;;;;;;;GAUG;AACH,eAAO,MAAM,iBAAiB,EAAE,SAAS,iBAAiB,EAiBzD,CAAC;AAEF;;;;;;;GAOG;AACH,wBAAgB,aAAa,CAAC,OAAO,EAAE,SAAS,MAAM,EAAE,GAAG,MAAM,GAAG,IAAI,CAuBvE;AAED,wCAAwC;AACxC,MAAM,WAAW,WAAW;IAC1B,6DAA6D;IAC7D,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,IAAI,EAAE,QAAQ,CAAC;IACxB,QAAQ,CAAC,MAAM,EAAE,UAAU,CAAC;IAC5B,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;CAC1B;AAED;;;;;;;;;;;;;;;;;GAiBG;AACH,MAAM,WAAW,oBAAoB;IACnC,iFAAiF;IACjF,QAAQ,CAAC,EAAE,EAAE,MAAM,CAAC;IACpB,+DAA+D;IAC/D,QAAQ,CAAC,WAAW,EAAE,MAAM,CAAC;IAC7B;;;OAGG;IACH,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;CAC1B;AAED,+EAA+E;AAC/E,MAAM,WAAW,eAAe;IAC9B,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,MAAM,EAAE,MAAM,CAAC;CACzB;AAED,iEAAiE;AACjE,MAAM,WAAW,YAAY;IAC3B,QAAQ,CAAC,KAAK,EAAE,SAAS,WAAW,EAAE,CAAC;IACvC,QAAQ,CAAC,OAAO,EAAE,SAAS,eAAe,EAAE,CAAC;IAC7C,+DAA+D;IAC/D,QAAQ,CAAC,OAAO,EAAE,SAAS,UAAU,EAAE,CAAC;IACxC,8DAA8D;IAC9D,QAAQ,CAAC,QAAQ,EAAE,MAAM,GAAG,IAAI,CAAC;IACjC,kEAAkE;IAClE,QAAQ,CAAC,YAAY,EAAE,WAAW,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;CACpD;AAED,+DAA+D;AAC/D,MAAM,WAAW,SAAS;IACxB,gEAAgE;IAChE,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IACtB,QAAQ,CAAC,UAAU,EAAE,MAAM,CAAC;IAC5B,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB;;;;OAIG;IACH,QAAQ,CAAC,eAAe,EAAE,MAAM,CAAC;IACjC,QAAQ,CAAC,WAAW,EAAE,MAAM,CAAC;IAC7B,QAAQ,CAAC,cAAc,EAAE,MAAM,GAAG,SAAS,CAAC;IAC5C,oEAAoE;IACpE,QAAQ,CAAC,OAAO,EAAE,SAAS,oBAAoB,EAAE,CAAC;IAClD,mFAAmF;IACnF,QAAQ,CAAC,iBAAiB,EAAE,MAAM,GAAG,IAAI,CAAC;IAC1C,kFAAkF;IAClF,QAAQ,CAAC,eAAe,EAAE,MAAM,GAAG,IAAI,CAAC;IACxC;;;;;;;;;;OAUG;IACH,QAAQ,CAAC,WAAW,EAAE,WAAW,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IAClD;;;;;;;;;OASG;IACH,QAAQ,CAAC,UAAU,EAAE,WAAW,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IACjD,kFAAkF;IAClF,QAAQ,CAAC,UAAU,EAAE,MAAM,CAAC;IAC5B;;;;;;;;;;;OAWG;IACH,QAAQ,CAAC,UAAU,EAAE,WAAW,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IACjD;;;;;;;;OAQG;IACH,QAAQ,CAAC,cAAc,EAAE,WAAW,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IACrD,mEAAmE;IACnE,QAAQ,CAAC,QAAQ,EAAE,MAAM,GAAG,IAAI,CAAC;IACjC,iFAAiF;IACjF,QAAQ,CAAC,KAAK,EAAE,MAAM,GAAG,IAAI,CAAC;IAC9B;;;;;;OAMG;IACH,QAAQ,CAAC,QAAQ,EAAE,QAAQ,CAAC;IAC5B;;;;;;OAMG;IACH,QAAQ,CAAC,OAAO,CAAC,EAAE,WAAW,CAAC,MAAM,CAAC,GAAG,SAAS,CAAC;IACnD;;;;;;;;;OASG;IACH,QAAQ,CAAC,QAAQ,EAAE,SAAS,gBAAgB,EAAE,CAAC;IAC/C;;;;;;;;OAQG;IACH,QAAQ,CAAC,WAAW,EAAE,MAAM,CAAC;IAC7B;;;;;;;OAOG;IACH,QAAQ,CAAC,SAAS,EAAE,WAAW,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;CACjD;AAED;;;;;;;GAOG;AACH,wBAAgB,mBAAmB,CAAC,IAAI,EAAE,MAAM,GAAG,IAAI,CAStD;AAED;;;;;;GAMG;AACH,wBAAgB,oBAAoB,CAAC,UAAU,EAAE,MAAM,GAAG,IAAI,CAS7D;AAED;;;;;;;;;;;;;;;;;;;GAmBG;AACH,eAAO,MAAM,mBAAmB,6JAKtB,CAAC;AAEX;;;;;;;;;;;;GAYG;AACH,eAAO,MAAM,eAAe,qGAIlB,CAAC;AAEX;;;;;;;;;;;;;;;;;;GAkBG;AACH,wBAAgB,aAAa,CAC3B,OAAO,EAAE,SAAS,oBAAoB,EAAE,GACvC,SAAS,CAAC,SAAS,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC,EAAE,CAOxC;AAeD;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,wBAAgB,cAAc,CAAC,KAAK,EAAE,SAAS,GAAG,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CA8BvE;AAED,+EAA+E;AAC/E,wBAAgB,eAAe,CAAC,IAAI,EAAE,YAAY,GAAG,MAAM,CAI1D;AAkBD;;;;;;;;GAQG;AACH,wBAAgB,yBAAyB,CACvC,QAAQ,EAAE,SAAS,gBAAgB,EAAE,EACrC,KAAK,EAAE,OAAO,GACb,SAAS,gBAAgB,EAAE,CAI7B;AAED,6EAA6E;AAC7E,wBAAgB,0BAA0B,CACxC,QAAQ,EAAE,SAAS,gBAAgB,EAAE,EACrC,KAAK,EAAE,OAAO,GACb,SAAS,gBAAgB,EAAE,CAI7B;AAoDD;;;;;;;;;;;;;;;;;GAiBG;AACH,wBAAgB,UAAU,CACxB,MAAM,EAAE,SAAS,kBAAkB,EAAE,EACrC,QAAQ,EAAE,SAAS,gBAAgB,EAAE,EACrC,KAAK,EAAE,OAAO,GACb,MAAM,CAoCR;AAED;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AACH,wBAAgB,OAAO,CAAC,KAAK,EAAE,SAAS,EAAE,KAAK,EAAE,OAAO,GAAG,MAAM,CA4BhE;AAED;;;GAGG;AACH,wBAAgB,YAAY,CAAC,KAAK,EAAE,SAAS,GAAG,YAAY,CAyY3D;AA2CD;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AACH,wBAAgB,kBAAkB,CAChC,KAAK,EAAE,SAAS;AAChB;;;;;;;;;;;GAWG;AACH,SAAS,UAAQ,GAChB,SAAS,CAAC,SAAS,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC,EAAE,CAoBxC"}