@pareto4/pp-core 1.21.1 → 1.23.1

package/pp-core/bin/lib/messages/init.cjs

@@ -0,0 +1,513 @@
+"use strict";
+/**
+ * Catalog slice: init messages (Phase 41). Data only.
+ *
+ * ADR-457 build-at-publish: compiles to the gitignored
+ * `pp-core/bin/lib/messages/init.cjs`. Imports nothing but the entry type.
+ *
+ * Plan 41-07 puts the asking half here: the ten questions (`init.step.*`),
+ * the prompt chrome (`init.chrome.*`), the compose summary printed before the
+ * confirmation (`init.compose.*`) and the auto-answer echoes
+ * (`init.auto_answer.*`). Plan 41-09 adds the answers and errors, plan 41-10 the outcomes
+ * (Done lines, verify report, invariant messages, CLI refusals).
+ *
+ * The `developer` text of every entry is the wording the untouched code printed
+ * (tests/fixtures/message-oracle-init.json pins it byte for byte). The answer
+ * tokens a person types (`internal`, `none`, `yes`, `no`, the provider and
+ * visibility words) are never translated: every reworded variant names them in
+ * backticks. `Ref:` lines are added at render time, never written here.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.init = void 0;
+exports.init = Object.freeze({
+    // ─── Answers and errors (plan 41-09) ────────────────────────────────────────
+    'init.answer.answer_required': {
+        reach: 'business',
+        developer: 'Question "{step}" requires a non-blank answer.',
+        engineer: 'This question needs an answer, so it cannot be left blank. Type one and press Enter.',
+        business: 'This answer cannot be left empty. Type an answer and press Enter.',
+        explain: 'Every question except the optional ones needs an answer before setup can go on. The same question is asked again.',
+    },
+    'init.answer.invalid_client_vault': {
+        reach: 'business',
+        developer: 'Question "client_vault": {detail}',
+        engineer: 'That standards vault location was refused: it must be "owner/name" or a clone URL with no credentials or machine-specific path in it. Type a usable location, or type `none`.',
+        business: 'That location for your standards cannot be used. Type it as "owner/name" or a web address with no password in it, or type `none`.',
+        explain: 'The location is saved in a file that is shared with the team, so it must not hold a password or a path that only works on one computer. The same question is asked again.',
+    },
+    'init.answer.invalid_compose_confirm': {
+        reach: 'business',
+        developer: 'compose_confirm requires "yes" or "no" (also accepts approve/decline, y/n, true/false).',
+        engineer: 'That was not a yes or no. Type `yes` to write `.platform-bindings.json`, or `no` to skip it.',
+        business: 'Please answer `yes` or `no`. Type `yes` to write `.platform-bindings.json`, or `no` to skip it.',
+        explain: 'Setup only writes the platform connection file after you agree. It also accepts y, n, approve and decline. The same question is asked again.',
+    },
+    'init.answer.compose_write_failed': {
+        reach: 'business',
+        developer: 'compose_confirm was approved, but the write to .platform-bindings.json did not succeed — this was NOT recorded as skipped or declined. Call --session-next to see the current state and try again.',
+        engineer: '`.platform-bindings.json` could not be written, so nothing was recorded: the file was not skipped or declined. Type `yes` to try again, or `no` to skip it.',
+        business: '`.platform-bindings.json` could not be written, so nothing was recorded. Type `yes` to try again, or `no` to skip it.',
+        explain: 'You agreed to write the platform connection file, but the write did not succeed. Nothing was saved and your choice was not counted as a no, so the question is asked again.',
+    },
+    'init.answer.compose_write_failed_warnings': {
+        reach: 'business',
+        developer: 'compose_confirm was approved, but the write to .platform-bindings.json did not succeed — this was NOT recorded as skipped or declined. Warnings: {warnings}. Call --session-next to see the current state and try again.',
+        engineer: '`.platform-bindings.json` could not be written, so nothing was recorded: the file was not skipped or declined. What was reported: {warnings}. Type `yes` to try again, or `no` to skip it.',
+        business: '`.platform-bindings.json` could not be written, so nothing was recorded. What was reported: {warnings}. Type `yes` to try again, or `no` to skip it.',
+        explain: 'You agreed to write the platform connection file, but the write did not succeed. Nothing was saved and your choice was not counted as a no, so the question is asked again.',
+        // Every warning joined with `; `: capped at DIAG_CAP so the later warnings are not dropped.
+        longParams: ['warnings'],
+    },
+    'init.answer.session_malformed': {
+        reach: 'business',
+        developer: 'The init session file at .planning/.init-session.json exists but is malformed or unreadable. Run "pp_run query init-contract --session-reset" to start over.',
+        engineer: 'The saved setup answers are damaged or unreadable. Run `pp-tools init --reset` to start over.',
+        business: 'The answers saved for this setup are damaged. Run `pp-tools init --reset` to start over.',
+        explain: 'Setup keeps your answers in a small file so it can carry on where you left off. That file cannot be read, so setup will not guess. Starting over clears it.',
+    },
+    INIT_SESSION_MALFORMED: {
+        reach: 'business',
+        developer: 'The init session file at .planning/.init-session.json exists but is malformed or unreadable. Run "pp_run query init-contract --session-reset" to start over — it is never resumed silently into an unknown state.',
+        engineer: 'The saved setup answers are damaged or unreadable. Run `pp-tools init --reset` to start over; setup is never resumed from a state it cannot read.',
+        business: 'The answers saved for this setup are damaged. Run `pp-tools init --reset` to start over.',
+        explain: 'Setup keeps your answers in a small file so it can carry on where you left off. That file cannot be read, so setup will not guess. Starting over clears it.',
+    },
+    INIT_SESSION_WRITE_FAILED: {
+        reach: 'business',
+        developer: "A filesystem write inside the init session failed ({detail}). This project's .planning directory (or .platform-bindings.json) may not be writable (permissions, a read-only mount, a full disk). Nothing further was recorded for this step — fix the underlying filesystem issue and try the same step again.",
+        engineer: 'Setup could not save your answer to disk, so nothing was recorded for this step. Check that the project folder is writable (permissions, a read-only mount, a full disk), then answer again.',
+        business: 'Your answer could not be saved, so nothing was recorded for this step. Check that the project folder can be written to, then answer again.',
+        explain: 'Setup saves each answer as you give it. Saving failed, usually because the folder is read-only or the disk is full. Fix that, then answer the same question again.',
+    },
+    'init.error_line': {
+        reach: 'developer',
+        developer: 'Error: {message}',
+    },
+    'init.rejected_fallback': {
+        reach: 'business',
+        developer: 'Rejected ({reason}) — please answer again.',
+        engineer: 'That answer was not accepted. Please answer again.',
+        business: 'That answer was not accepted. Please answer again.',
+        explain: 'Setup did not accept the answer and gave no more detail. The same question is asked again.',
+    },
+    'init.unexpected_state': {
+        reach: 'business',
+        developer: 'Unexpected session state: no step id was returned.',
+        engineer: 'Setup reached a state it did not expect. Run `pp-tools init --reset` to start over.',
+        business: 'Setup reached a state it did not expect. Run `pp-tools init --reset` to start over.',
+        explain: 'Setup lost track of which question comes next and stopped rather than guess. Starting over clears it.',
+    },
+    'init.step_overflow': {
+        reach: 'business',
+        developer: 'init session exceeded the maximum step count — aborting to avoid an infinite loop.',
+        engineer: 'Setup went on far longer than it should and was stopped. Run `pp-tools init --reset` and try again.',
+        business: 'Setup went on far longer than it should and was stopped. Run `pp-tools init --reset` and try again.',
+        explain: 'Setup stops after a fixed number of steps so it can never loop forever. Starting over clears the saved answers.',
+    },
+    // ─── Outcomes (plan 41-10) ──────────────────────────────────────────────────
+    // The Done lines, the unfinished-session report, the three invariant messages and the two CLI
+    // refusals. Each Done variant is its own whole sentence, chosen from a reading of the config
+    // (readVaultEnabledState / readVaultRequiredState), never from a claim.
+    'init.done.vault_off': {
+        reach: 'business',
+        developer: 'Done — .platform-bindings.json was composed and written; vault.enabled was left at false as this project set it, so the vault capability stays off and /pp-init Step 2.6 stays inert (arm it with pp-tools config-set vault.enabled true).',
+        engineer: 'Done. The platform connection was saved to `.platform-bindings.json`. `vault.enabled` was left at `false`, as this project set it, so the standards vault stays off and the reachability check in `/pp-init` is skipped. To switch the vault on, run `pp-tools config-set vault.enabled true`.',
+        business: "Done. Your platform connection was saved to `.platform-bindings.json`. Your organisation's standards are switched off, because this project's settings say so, so they are not used and nobody checks that they can be reached. To switch them on, run `pp-tools config-set vault.enabled true`.",
+        explain: "The platform connection was saved. The setting that switches on your organisation's standards is `false` in this project, and setup respects that. Change it with the command shown if you want the standards used.",
+    },
+    'init.done.vault_malformed': {
+        reach: 'business',
+        developer: 'Done — .platform-bindings.json was composed and written; vault.enabled holds a non-boolean value and was left untouched — pp-tools query init-contract --verify reports it as INIT_VAULT_ENABLED_MALFORMED; store the boolean with pp-tools config-set vault.enabled true.',
+        engineer: 'Done. The platform connection was saved to `.platform-bindings.json`. `vault.enabled` holds a value that is not true or false, so it was left untouched and the standards vault stays off. `pp-tools query init-contract --verify` reports it as `INIT_VAULT_ENABLED_MALFORMED`. To fix it, run `pp-tools config-set vault.enabled true`.',
+        business: "Done. Your platform connection was saved to `.platform-bindings.json`. The setting that switches on your organisation's standards holds a value that is neither true nor false, so it was left as it is and the standards stay off. To switch them on, run `pp-tools config-set vault.enabled true`.",
+        explain: "The platform connection was saved. The setting for your organisation's standards holds something other than true or false. Setup does not guess what was meant, so it left the value alone. Store a clear true with the command shown.",
+    },
+    'init.done.vault_armed': {
+        reach: 'business',
+        developer: 'Done — .platform-bindings.json was composed and written; vault.enabled is now true (the vault capability is armed — /pp-init Step 2.6 probes reachability next); each plan records which client standards documents governed it (<vault_standards>), checked by the vault.trace gate.',
+        engineer: 'Done. The platform connection was saved to `.platform-bindings.json` and `vault.enabled` is now `true`, so the standards vault is switched on. Each plan records which client standards documents governed it, and the `vault.trace` check verifies that record. Next, `/pp-init` checks that the vault can be reached.',
+        business: "Done. Your platform connection was saved to `.platform-bindings.json`, and your organisation's standards are now switched on. Each plan records which standards applied to it, and that record is checked. Next, `/pp-init` checks that the standards can be reached.",
+        explain: "The platform connection was saved and your organisation's standards were switched on. From now on every plan notes which standards it followed, and that note is checked. The next step in `/pp-init` tests that the standards can be fetched.",
+    },
+    'init.done.vault_armed_required': {
+        reach: 'business',
+        developer: 'Done — .platform-bindings.json was composed and written; vault.enabled is now true (the vault capability is armed — /pp-init Step 2.6 probes reachability next); each plan records which client standards documents governed it (<vault_standards>), checked by the vault.trace gate; vault.required is true, so a client vault miss, a failed fetch or an unwritable vault summary stops the build at plan:pre and execute:pre.',
+        engineer: 'Done. The platform connection was saved to `.platform-bindings.json` and `vault.enabled` is now `true`, so the standards vault is switched on. Each plan records which client standards documents governed it, and the `vault.trace` check verifies that record. `vault.required` is `true`, so a vault miss, a failed fetch or an unwritable vault summary stops the work before a plan is written and before it is built. Next, `/pp-init` checks that the vault can be reached.',
+        business: "Done. Your platform connection was saved to `.platform-bindings.json`, and your organisation's standards are now switched on and required. Each plan records which standards applied to it, and that record is checked. If the standards cannot be found, downloaded or saved, work stops before a plan is written or built. Next, `/pp-init` checks that the standards can be reached.",
+        explain: "The platform connection was saved and your organisation's standards were switched on as a requirement. If they go missing or cannot be fetched, planning and building stop instead of carrying on without them. The next step in `/pp-init` tests that the standards can be fetched.",
+    },
+    'init.done.written': {
+        reach: 'business',
+        developer: 'Done — .platform-bindings.json was composed and written.',
+        engineer: 'Done. The platform connection was saved to `.platform-bindings.json`. `vault.enabled` was not found in the project settings, so nothing about the standards vault was changed.',
+        business: "Done. Your platform connection was saved to `.platform-bindings.json`. No setting for your organisation's standards was found, so nothing about them was changed.",
+        explain: 'The platform connection was saved. Setup could not find the setting that switches on your organisation\'s standards, so it says nothing about them.',
+    },
+    'init.done.nothing_composed': {
+        reach: 'business',
+        developer: 'Done — nothing was composed (declined, or nothing was composable).',
+        engineer: 'Done. Nothing was written to `.platform-bindings.json`: you declined, or nothing could be composed. To be asked again, run `pp-tools init --reset`.',
+        business: 'Done. Nothing was saved: you chose not to set up the platform connection, or there was not enough to set it up with. To be asked again, run `pp-tools init --reset`.',
+        explain: 'Setup ended without saving a platform connection, either because you said no or because there was nothing to save. A finished setup does not ask again by itself; `pp-tools init --reset` starts the questions over.',
+    },
+    'init.done.skipped': {
+        reach: 'business',
+        developer: 'Nothing was composable from the org profile and project answers — no compose_confirm step was shown and nothing was written (the inert path, INIT-02).',
+        engineer: "Nothing was written: your organisation's profile and your answers were not enough to compose a platform connection, so no confirmation was asked and `.platform-bindings.json` was not created. That is normal for a project no organisation profile applies to.",
+        business: "Nothing was saved: your answers and your organisation's settings were not enough to set up a platform connection, so you were not asked to confirm one and `.platform-bindings.json` was not created. That is normal for a project that no organisation settings apply to.",
+        explain: 'Setup finished without a platform connection because there was nothing it could build one from. No question was skipped and nothing was lost.',
+    },
+    'init.done.unchanged': {
+        reach: 'business',
+        developer: 'The existing .platform-bindings.json is already up to date with what the org profile and project answers would produce — no compose_confirm step was needed and nothing was written.',
+        engineer: "The existing `.platform-bindings.json` already matches what your organisation's profile and your answers would produce, so no confirmation was needed and nothing was written.",
+        business: "Your existing platform connection in `.platform-bindings.json` already matches your answers and your organisation's settings, so you were not asked to confirm anything and nothing was changed.",
+        explain: 'The saved platform connection is already what setup would have built, so setup left the file as it was.',
+    },
+    'init.verify': {
+        reach: 'business',
+        developer: 'The session could not reach a clean end state:',
+        engineer: 'Setup did not reach a clean end state. These problems need fixing:',
+        business: 'Setup did not finish. These problems need fixing:',
+        explain: 'Setup stopped with problems still open. Each one is listed below with its own reference code, then this one.',
+    },
+    'init.verify.line': {
+        reach: 'developer',
+        developer: '  - [{code}] {message}',
+    },
+    INIT_IDENTITY_MISSING: {
+        reach: 'business',
+        developer: 'No "project" block found in .planning/config.json — Step 2 identity capture did not complete.',
+        engineer: 'The project details were not saved: `.planning/config.json` has no `project` section. Run `pp-tools init --reset` and answer the questions again.',
+        business: 'The project details were not saved: `.planning/config.json` has no `project` section. Run `pp-tools init --reset` and answer the questions again.',
+        explain: 'Setup keeps the project name, client and provider in the `project` section of `.planning/config.json`. That section is missing, so the answers did not get saved.',
+    },
+    INIT_VAULT_PROVIDER_UNSET: {
+        reach: 'business',
+        developer: 'project.provider is "{provider}" but vault.provider is unset — the D-13 provisioning gate is disabled.',
+        engineer: '`project.provider` is `{provider}` but `vault.provider` is not set in `.planning/config.json`, so the provisioning check stays off. Set `vault.provider` and run the check again.',
+        business: 'The project is kept on `{provider}`, but `vault.provider` is not set in `.planning/config.json`, so the check that the project is set up there cannot run. Set `vault.provider` and run the check again.',
+        explain: 'The project names a hosting service, but the matching setting for your organisation\'s standards is empty, so one of the setup checks is switched off until it is filled in.',
+    },
+    INIT_COMPOSITION_NOT_RUN: {
+        reach: 'business',
+        developer: 'A binding is composable from the org profile and project answers, but .platform-bindings.json was never written and no decline was recorded — Step 2.5 appears to have been skipped. Run "pp-tools init --reset" to redo the question set and reach the compose confirmation (init-friction F3: a completed session never re-offers composition on a bare re-run).',
+        engineer: "A platform connection could be built from your organisation's profile and your answers, but `.platform-bindings.json` was never written and no decline was recorded, so the confirmation step looks skipped. Run `pp-tools init --reset` to answer the questions again and reach the confirmation. A finished setup does not offer it again on a plain re-run.",
+        business: "A platform connection could be set up from your answers and your organisation's settings, but `.platform-bindings.json` was never saved and you did not say no. Run `pp-tools init --reset` to answer the questions again and reach the confirmation. A finished setup does not offer it again on a plain re-run.",
+        explain: 'Setup could have built the platform connection but never asked you to confirm it. Starting over with `pp-tools init --reset` brings the question back.',
+    },
+    init_non_interactive: {
+        reach: 'business',
+        developer: '"pp-tools init" requires an interactive terminal (stdin is not a TTY) and will not prompt. This command cannot run inside an AI-agent shell or a piped session — open a regular terminal window (e.g. Terminal, iTerm, or Windows Terminal) and run it there. For a non-interactive/CI-driven session, use "pp-tools query init-contract --session-next" / "--session-answer <stepId>=<value>" directly instead.',
+        engineer: '`pp-tools init` asks its questions in a terminal, and this is not one, so nothing was asked. Open a regular terminal window (for example Terminal, iTerm or Windows Terminal) and run `pp-tools init` there. To answer the questions from a script or a CI job, use `pp-tools query init-contract --session-next` and `pp-tools query init-contract --session-answer <stepId>=<value>`.',
+        business: '`pp-tools init` asks its questions in a terminal window, and this is not one, so nothing was asked. Open a regular terminal window (for example Terminal, iTerm or Windows Terminal) and run `pp-tools init` there.',
+        explain: 'Setup asks you questions, so it needs a real terminal window. It refuses to start anywhere else rather than wait for answers that can never arrive.',
+    },
+    'init.unknown_flag': {
+        reach: 'business',
+        developer: 'Unrecognized flag "{flag}" for init. Supported: --offline, --reset. For init workflow subcommands (execute-phase, plan-phase, new-project, ...), use "pp-tools query init.<subcommand>".',
+        engineer: '`{flag}` is not an option that `pp-tools init` understands. The options are `--offline` and `--reset`. For the other init commands, such as `execute-phase`, use `pp-tools query init.<subcommand>`.',
+        business: '`{flag}` is not an option that `pp-tools init` understands. Use `--offline` or `--reset`, or run `pp-tools init` with no option.',
+        explain: '`pp-tools init` accepts only `--offline` (skip the online version lookup) and `--reset` (clear the saved answers and start over). Anything else is refused.',
+    },
+    // ─── Questions: key = init.step.<step id> ──────────────────────────────────
+    'init.step.project_name': {
+        reach: 'business',
+        developer: 'Project name (human-readable, e.g. "Acme Dashboard")',
+        engineer: 'Project name, in plain words (for example "Acme Dashboard").',
+        business: 'What is your project called? Type its name in plain words, for example "Acme Dashboard".',
+        explain: 'The project name is the title people will see for this project. Type it the way you would say it out loud. A short name for web addresses is asked for next.',
+    },
+    'init.step.project_slug': {
+        reach: 'business',
+        developer: 'Project slug (kebab-case, e.g. "acme-dashboard")',
+        engineer: 'Project short name (URL-safe: lowercase words joined by hyphens, for example "acme-dashboard").',
+        business: 'Type a short name for the project: lowercase words joined by hyphens, for example "acme-dashboard".',
+        explain: 'The short name is a compact version of the project name that is safe to use in web addresses and file names. Use lowercase letters, numbers and hyphens only.',
+    },
+    'init.step.client_name': {
+        reach: 'business',
+        developer: 'Client name (company / team, e.g. "Acme Corp") — type "internal" if none',
+        engineer: 'Client name (the company or team, for example "Acme Corp"). Type `internal` if there is no client.',
+        business: 'Who is this project for? Type the company or team name, for example "Acme Corp". If there is no client, type `internal`.',
+        explain: 'The client is the company or team the project is built for. Work for your own organisation has no client, so type `internal`.',
+    },
+    'init.step.client_slug': {
+        reach: 'business',
+        developer: 'Client slug (kebab-case, e.g. "acme") — type "internal" if none',
+        engineer: 'Client short name (URL-safe: lowercase words joined by hyphens, for example "acme"). Type `internal` if there is no client.',
+        business: 'Type a short name for the client: lowercase words joined by hyphens, for example "acme". If there is no client, type `internal`.',
+        explain: 'The client short name is a compact version of the client name for web addresses and file names. Work for your own organisation has no client, so type `internal`.',
+    },
+    'init.step.client_vault': {
+        reach: 'business',
+        developer: 'Client vault repo ("owner/name" or a full clone URL) — type "none" to bind no client vault',
+        engineer: 'Standards vault repository for this client ("owner/name" or a full clone URL). Type `none` to connect no standards vault.',
+        business: 'Where are this client\'s standards kept? Type the location as "owner/name" or a full web address, or type `none` to connect no standards.',
+        explain: 'Some clients keep their coding and delivery standards in a shared place. Naming it here lets pp-core use those standards in the plans it writes. Type `none` if this client has none.',
+    },
+    'init.step.client_vault_default': {
+        reach: 'business',
+        developer: 'Client vault repo ("owner/name" or a full clone URL) — type "none" to use the default vault ({repo})',
+        engineer: 'Standards vault repository for this client ("owner/name" or a full clone URL). Type `none` to use the default vault (`{repo}`).',
+        business: 'Where are this client\'s standards kept? Type the location as "owner/name" or a full web address, or type `none` to use your organisation\'s standards (`{repo}`).',
+        explain: 'Your organisation already names a place where standards are kept. Type `none` to use it, or give a different location if this client keeps its own.',
+    },
+    'init.step.description': {
+        reach: 'business',
+        developer: 'One-line description (what this project does)',
+        engineer: 'One-line description of what the project does.',
+        business: 'Describe in one sentence what this project does.',
+        explain: 'The description is one sentence that tells a new reader what the project is for. It is shown next to the project name.',
+    },
+    'init.step.provider': {
+        reach: 'business',
+        developer: 'Provider (gitlab / azure / github / other / none)',
+        engineer: 'Which Git hosting provider holds this project? Choose `gitlab`, `azure`, `github`, `other` or `none`.',
+        business: 'Which service will keep this project\'s work online? Choose `gitlab`, `azure`, `github`, `other` or `none`.',
+        explain: 'pp-core connects to the service that keeps your project online. Pick the one your team uses, `other` for a service not listed, or `none` if the project is not kept online yet.',
+    },
+    'init.step.visibility': {
+        reach: 'business',
+        developer: 'Visibility (private / public / internal)',
+        engineer: 'Who can see the repository? Choose `private`, `public` or `internal`.',
+        business: 'Who should be able to see this project? Choose `private` (only invited people), `public` (anyone) or `internal` (people in your organisation).',
+        explain: 'Visibility decides who can find and read the project on the service that keeps it online. Choose `private` when you are not sure; it can be widened later.',
+    },
+    'init.step.compose_confirm': {
+        reach: 'business',
+        developer: 'A binding can be composed from the org profile and project answers. Compose and write .platform-bindings.json now? (yes/no)',
+        engineer: "A platform connection can be built from your organisation's profile and your answers. Write it to `.platform-bindings.json` now? Type `yes` to save it or `no` to save nothing.",
+        business: "Your answers and your organisation's settings are enough to set up the platform connection. Save it to `.platform-bindings.json` now? Type `yes` to save it, or `no` to save nothing.",
+        explain: 'The platform connection tells pp-core where this project lives and which standards apply. It is saved in the file `.platform-bindings.json`. Type `yes` to save it, or `no` to leave it for later; nothing is written until you say `yes`.',
+    },
+    // ─── Prompt chrome (fragments of a question) ───────────────────────────────
+    'init.chrome.options': {
+        reach: 'business',
+        developer: 'Options: {options}',
+        engineer: 'Options: {options}',
+        business: 'Choose one: {options}',
+        part: true,
+    },
+    'init.chrome.skip_hint': {
+        reach: 'business',
+        developer: '(press Enter to skip)',
+        engineer: '(press Enter to skip)',
+        business: '(or press Enter to skip this question)',
+        part: true,
+    },
+    'init.chrome.preselected': {
+        reach: 'business',
+        developer: 'preselected',
+        engineer: 'preselected',
+        business: 'suggested',
+        part: true,
+    },
+    'init.chrome.resolved_default': {
+        reach: 'business',
+        developer: '{provider} (resolved default)',
+        engineer: 'detected default',
+        business: 'suggested',
+        part: true,
+    },
+    // ─── Compose summary shown before the confirmation ─────────────────────────
+    'init.compose.header': {
+        reach: 'business',
+        developer: 'A binding can be composed from the org profile and project answers:',
+        engineer: "A platform connection can be built from your organisation's profile and your answers:",
+        business: "Here is the platform connection that can be set up from your answers and your organisation's settings:",
+        part: true,
+    },
+    'init.compose.provenance': {
+        reach: 'business',
+        developer: '  {field} = {value} (from {source})',
+        engineer: '  `{field}` = {value} (from {source})',
+        business: '  `{field}` = {value} (from {source})',
+        part: true,
+        // The value the person approves: shown whole, not cut at the echo cap.
+        longParams: ['value'],
+    },
+    'init.compose.drift_header': {
+        reach: 'business',
+        developer: 'Drift (the already-committed file wins — nothing here is a proposed change):',
+        engineer: 'Out-of-date settings (the file already on disk wins; nothing here is a proposed change):',
+        business: "Some of your organisation's settings differ from the saved file. The saved file wins, so nothing here changes:",
+        part: true,
+    },
+    'init.compose.drift': {
+        reach: 'business',
+        developer: '  the profile would have supplied {profile_value} for "{key}"; the file already says {file_value}, and {file_value} wins.',
+        engineer: '  The profile would have supplied {profile_value} for `{key}`; the file already says {file_value}, and {file_value} wins.',
+        business: "  Your organisation's settings suggest {profile_value} for `{key}`, but the saved file says {file_value}, so {file_value} stays.",
+        part: true,
+        longParams: ['file_value', 'profile_value'],
+    },
+    'init.compose.warning': {
+        reach: 'business',
+        developer: '  warning: {warning}',
+        engineer: '  Warning: {warning}',
+        business: '  Note: {warning}',
+        part: true,
+        // A compose warning (up to 200 characters) ends with its remedy: never cut at the echo cap.
+        longParams: ['warning'],
+    },
+    'init.compose.action': {
+        reach: 'business',
+        developer: 'Action: {action}',
+        engineer: 'Action: {action}',
+        business: 'What happens if you say `yes`: {action}',
+        part: true,
+    },
+    // ─── Answers the session filled in itself ──────────────────────────────────
+    'init.auto_answer.derived': {
+        reach: 'business',
+        developer: '  {id} = {value} (derived)',
+        engineer: '  {id} = {value} (worked out from your other answers)',
+        business: '  {id} = {value} (worked out from your other answers)',
+        part: true,
+    },
+    'init.auto_answer.org_profile': {
+        reach: 'business',
+        developer: '  {id} = {value} (set by the org profile)',
+        engineer: "  {id} = {value} (set by your organisation's profile)",
+        business: "  {id} = {value} (set by your organisation's settings)",
+        part: true,
+    },
+    // ─── Words for values the compose summary and auto-answer echoes show ──────
+    // The developer text is the raw value the code always printed; the driver looks these up for
+    // business and engineer only (`init.word.<kind>.<value, hyphens as underscores>`). Not part of
+    // the `init.step|chrome|compose|auto_answer` asking set.
+    'init.word.source.profile_seed': {
+        reach: 'business',
+        developer: 'profile-seed',
+        engineer: "your organisation's settings",
+        business: "your organisation's settings",
+        part: true,
+    },
+    'init.word.source.project_answer': {
+        reach: 'business',
+        developer: 'project-answer',
+        engineer: 'your answer',
+        business: 'your answer',
+        part: true,
+    },
+    'init.word.source.resolved_host': {
+        reach: 'business',
+        developer: 'resolved-host',
+        engineer: 'the detected host',
+        business: 'the detected host',
+        part: true,
+    },
+    'init.word.source.resolved_tag': {
+        reach: 'business',
+        developer: 'resolved-tag',
+        engineer: 'the latest published version',
+        business: 'the latest published version',
+        part: true,
+    },
+    'init.word.source.package_identity': {
+        reach: 'business',
+        developer: 'package-identity',
+        engineer: 'the package details',
+        business: 'the package details',
+        part: true,
+    },
+    'init.word.source.contract': {
+        reach: 'business',
+        developer: 'contract',
+        engineer: "pp-core's defaults",
+        business: "pp-core's defaults",
+        part: true,
+    },
+    'init.word.source.existing_file': {
+        reach: 'business',
+        developer: 'existing-file',
+        engineer: 'the saved file',
+        business: 'the saved file',
+        part: true,
+    },
+    'init.word.action.create': {
+        reach: 'business',
+        developer: 'create',
+        engineer: 'create the file',
+        business: 'create the file',
+        part: true,
+    },
+    'init.word.action.update': {
+        reach: 'business',
+        developer: 'update',
+        engineer: 'update the file',
+        business: 'update the file',
+        part: true,
+    },
+    'init.word.action.unchanged': {
+        reach: 'business',
+        developer: 'unchanged',
+        engineer: 'leave the file as it is',
+        business: 'leave the file as it is',
+        part: true,
+    },
+    'init.word.action.none': {
+        reach: 'business',
+        developer: 'none',
+        engineer: 'nothing to write',
+        business: 'nothing to write',
+        part: true,
+    },
+    'init.word.step.project_name': {
+        reach: 'business',
+        developer: 'project_name',
+        engineer: 'project name',
+        business: 'project name',
+        part: true,
+    },
+    'init.word.step.project_slug': {
+        reach: 'business',
+        developer: 'project_slug',
+        engineer: 'project short name',
+        business: 'project short name',
+        part: true,
+    },
+    'init.word.step.client_name': {
+        reach: 'business',
+        developer: 'client_name',
+        engineer: 'client name',
+        business: 'client name',
+        part: true,
+    },
+    'init.word.step.client_slug': {
+        reach: 'business',
+        developer: 'client_slug',
+        engineer: 'client short name',
+        business: 'client short name',
+        part: true,
+    },
+    'init.word.step.client_vault': {
+        reach: 'business',
+        developer: 'client_vault',
+        engineer: 'client standards location',
+        business: 'client standards location',
+        part: true,
+    },
+    'init.word.step.description': {
+        reach: 'business',
+        developer: 'description',
+        engineer: 'description',
+        business: 'description',
+        part: true,
+    },
+    'init.word.step.provider': {
+        reach: 'business',
+        developer: 'provider',
+        engineer: 'provider',
+        business: 'provider',
+        part: true,
+    },
+    'init.word.step.visibility': {
+        reach: 'business',
+        developer: 'visibility',
+        engineer: 'visibility',
+        business: 'visibility',
+        part: true,
+    },
+});

package/pp-core/bin/lib/messages/progress.cjs

@@ -0,0 +1,110 @@
+"use strict";
+/**
+ * Catalog slice: progress and stats table messages (Phase 41, plan 41-08). Data only.
+ *
+ * ADR-457 build-at-publish: compiles to the gitignored
+ * `pp-core/bin/lib/messages/progress.cjs`. Imports nothing but the entry type.
+ *
+ * Only the `table` format of `progress` and `stats` is display text; the json
+ * and bar formats are machine output and never read this slice. The `developer`
+ * text of every entry is the wording the untouched code printed
+ * (tests/fixtures/message-oracle.json pins it byte for byte). The status cell of
+ * each row is not here: it is the canonical word run through
+ * `label('phase.status', …)` at the last step of the render (D-13).
+ *
+ * `engineer` and `business` follow pp-core/references/audience.md: business
+ * says "stage" for phase and "release" for milestone. The pipe columns of a
+ * header entry and the separator row under it must keep the same shape. The
+ * header codes hold the header row, a newline, and the separator row. The
+ * `Ref:` line is added by the renderer once, at the end of the table.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.progress = void 0;
+exports.progress = Object.freeze({
+    // ─── progress table ────────────────────────────────────────────────────────
+    'progress.table': {
+        reach: 'business',
+        developer: '# {version} {name}',
+        engineer: '# Milestone {version}: {name}',
+        business: '# Release {version}: {name}',
+        explain: 'This table shows how far the current release has come: one overall progress line, then one row per stage with the plans finished and where the stage stands. The status words in the last column are the same words the work itself uses, written out in plain language.',
+    },
+    'progress.table.progress': {
+        reach: 'business',
+        developer: '**Progress:** [{bar}] {done}/{total} plans ({percent}%)',
+        engineer: '**Progress:** [{bar}] {done} of {total} plans complete ({percent}%)',
+        business: '**How far along:** [{bar}] {done} of {total} plans done ({percent}%)',
+        part: true,
+    },
+    'progress.table.header': {
+        reach: 'business',
+        developer: '| Phase | Name | Plans | Status |\n|-------|------|-------|--------|',
+        engineer: '| Phase | Name | Plans done | Status |\n|-------|------|------------|--------|',
+        business: '| Stage | Name | Plans done | Status |\n|-------|------|------------|--------|',
+        part: true,
+    },
+    // ─── stats table ───────────────────────────────────────────────────────────
+    'stats.table': {
+        reach: 'business',
+        developer: '# {version} {name} — Statistics',
+        engineer: '# Milestone {version}: {name} (statistics)',
+        business: '# Release {version}: {name} (how things stand)',
+        explain: 'This table sums up the current release: how many stages and plans are done, how many requirements are met, one row per stage, and when the work last moved. The status words in the table are the same words the work itself uses, written out in plain language.',
+    },
+    'stats.table.progress': {
+        reach: 'business',
+        developer: '**Progress:** [{bar}] {done}/{total} phases ({percent}%)',
+        engineer: '**Progress:** [{bar}] {done} of {total} phases complete ({percent}%)',
+        business: '**How far along:** [{bar}] {done} of {total} stages done ({percent}%)',
+        part: true,
+    },
+    'stats.table.plans': {
+        reach: 'business',
+        developer: '**Plans:** {done}/{total} complete ({percent}%)',
+        engineer: '**Plans:** {done} of {total} complete ({percent}%)',
+        business: '**Plans:** {done} of {total} done ({percent}%)',
+        part: true,
+    },
+    'stats.table.phases': {
+        reach: 'business',
+        developer: '**Phases:** {done}/{total} complete',
+        engineer: '**Phases:** {done} of {total} complete',
+        business: '**Stages:** {done} of {total} done',
+        part: true,
+    },
+    'stats.table.requirements': {
+        reach: 'business',
+        developer: '**Requirements:** {done}/{total} complete',
+        engineer: '**Requirements:** {done} of {total} complete',
+        business: '**Requirements:** {done} of {total} met',
+        part: true,
+    },
+    'stats.table.header': {
+        reach: 'business',
+        developer: '| Phase | Name | Plans | Completed | Status | Wall-clock |\n|-------|------|-------|-----------|--------|------------|',
+        engineer: '| Phase | Name | Plans | Completed | Status | Elapsed time |\n|-------|------|-------|-----------|--------|--------------|',
+        business: '| Stage | Name | Plans | Plans done | Status | Time taken |\n|-------|------|-------|------------|--------|------------|',
+        part: true,
+    },
+    'stats.table.git': {
+        reach: 'business',
+        developer: '**Git:** {count} commits',
+        engineer: '**Commits:** {count}',
+        business: '**Changes saved:** {count}',
+        part: true,
+    },
+    'stats.table.git_since': {
+        reach: 'business',
+        developer: ' (since {date})',
+        engineer: ' (since {date})',
+        business: ' (since {date})',
+        part: true,
+    },
+    'stats.table.last_activity': {
+        reach: 'business',
+        developer: '**Last activity:** {date}',
+        engineer: '**Last activity:** {date}',
+        business: '**Last activity:** {date}',
+        part: true,
+    },
+});