controlm-chain-admin 0.1.0__tar.gz → 0.1.2__tar.gz

{controlm_chain_admin-0.1.0 → controlm_chain_admin-0.1.2}/.claude/skills/bootstrap/SKILL.md

@@ -68,25 +68,32 @@ git add -A && git commit -m "chore: production baseline"
 This first commit is the only one made on `main` by hand: from now on `main` mirrors
 production and every change goes through a release.
 
-### 3. The other environments, one release
+### 3. The values of the other environments, one release
+
+The full exports of the other environments also carry the releases that are installed there
+but not in production yet. Take only their *values* from them (machines, users, mails, the
+environment's name in texts, variables): the jobs stay as production has them, and the
+releases come later from their deliveries (step 6).
 
 ```bash
-ctmchain release start baseline
-ctmchain receive ../exports/uat/<uat>.xml --full        # preview: the decisions
+ctmchain release start environments
+ctmchain receive ../exports/uat/<uat>.xml --values-only   # preview: the decisions
 ```
 
-A full export of an environment other than production leaves production alone by default.
 Read the decisions with the person, by section, before `--apply`:
 
-- **groups** (the same difference in many jobs, or a machine, user, mail or variable): a new
+- **groups** (a machine, user, mail or variable, or the environment's name in a text): a new
   constant with a value per environment. Give them readable names with
-  `--choose 'group:...=new:<name>'`, or in the *Import* page of `ctmchain serve`.
-- **exceptions** (a value that differs in one job), **children** (conditions or ON blocks
-  that differ: ignored by default), **removed / added / absent** (jobs and folders only one
-  environment has or lacks).
+  `--choose 'group:...=new:<name>'`, or in the *Import* page of `ctmchain serve` (box *Only
+  the values of <env>*).
+- everything else is left out by default: changes of jobs (**differences**, **children**),
+  jobs the environment lacks (**removed**: kept) and folders or jobs only it has
+  (**added**: left out). A difference the person knows is the environment's own (a job that
+  is Dummy there, another command line) may be made an **exception** instead.
 
-Then `--apply`, `ctmchain export --env uat` to look at the result, and commit. Same for bench
-and test. Receiving the same export again shows what still differs.
+Then `--apply`, look at `ctmchain export --env uat`, and commit. Same for bench and test (they
+only learn the values of the constants that exist by now). Production is untouched:
+`ctmchain export --env prod --jobnames original` is still byte for byte the prod export.
 
 ### 4. The conventions agreed for these chains
 
@@ -104,13 +111,33 @@ and test. Receiving the same export again shows what still differs.
   environment, a letter in place of the application's first letter): not fixed on the way
   in. `ctmchain validate` lists them with suggested fixes, to correct in later releases.
 
-### 5. Close the baseline
+### 5. Close the environments release
 
 ```bash
-ctmchain release installed prod     # nothing to install: the baseline only describes them
+ctmchain release installed prod     # nothing to install: it only describes the environments
 ctmchain release close
 ```
 
+### 6. The releases already on their way, from their deliveries
+
+For each release installed somewhere but not in production yet, ask, numbered: its name,
+the delivery XML of each of its parts, and the environments it is installed in. Then, from
+`main`, one release each:
+
+```bash
+ctmchain release start <name>
+ctmchain receive ../exports/deliveries/<name>.xml --stat   # a delivery: its differences
+ctmchain receive ../exports/deliveries/<name>.xml --apply  # are the release's changes
+ctmchain commit -m "feat: release <name>"
+ctmchain release installed uat                             # each environment it is in
+```
+
+A folder two releases both changed comes whole in each delivery: when the first one is closed
+into `main`, *Update from main* in the other merges them. Check each release with
+`ctmchain receive ../exports/<env>/<env>.xml` (preview only) on the release branch: what is
+left is what differs for another reason (often conditions whose names differ per
+environment).
+
 Then the everyday flow of the data repository's own `CLAUDE.md` (written by `init`):
 deliveries through `ctmchain receive`, a full prod export now and then to catch up with
 production, releases installed environment by environment.

{controlm_chain_admin-0.1.0 → controlm_chain_admin-0.1.2}/BACKLOG.md

@@ -213,6 +213,13 @@ or addresses anywhere in this public repository.
     take` and the boxes of the *Compare* page; one attribute, variable, condition, group, job,
     folder, condition name, constant value or exception at a time, conflicts value by value.
 13. **PyPI release 0.1.0 — DONE (2026-11-03)**: Trusted Publishing from the `v0.1.0` tag.
+14. **Similar condition names — DONE (2026-11-03), released in 0.1.1**, asked by the author:
+    `validate` reports names that differ only by a copy's suffix or by case (`similar-names`)
+    and offers to number them (`number-similar`: `…_OK1`, `…_OK2`).
+15. **Only the values of an environment — DONE (2026-11-03), released in 0.1.2**, asked by
+    the author for the company (uat and bench carry releases production does not have yet):
+    `receive --values-only`, `skip` for added folders and jobs, *adopt* decisions; the
+    `bootstrap` skill builds the releases on their way from their deliveries.
 
 Later, unordered: `envs` variants of sub-elements; second-environment import with learning; `diff`
 of environments and XML files with `xmldiffreport`; mapping editor; upstream graph explorer

{controlm_chain_admin-0.1.0 → controlm_chain_admin-0.1.2}/CHANGELOG.md

@@ -6,6 +6,52 @@ All notable changes to this project are documented here. The format follows
 
 ## [Unreleased]
 
+## [0.1.2] - 2026-11-03
+
+### Added
+
+- `receive --values-only` and the *Only the values of <env>* box of the Import page: an export
+  of an environment whose jobs carry releases production does not have yet gives its
+  machines, users, mails, variables and its name in texts (new constants or their values) and
+  nothing else by default (differences and children ignored, jobs and folders it lacks kept,
+  folders and jobs only it has left out).
+- *added* decisions have the option `skip` ("Leave out"): the folder or job does not enter the
+  repository.
+- *adopt* decisions: where the repository still has production's value of a constant and the
+  export has the constant (a job no earlier export of that environment had), use the
+  constant; production does not change. Also inside texts (`[P77][PROD]` and
+  `@{env.subject}`).
+- The `bootstrap` skill takes only the values from the full exports, then builds the releases
+  on their way from their deliveries; the data repository's `CLAUDE.md` mentions
+  `--values-only`.
+
+### Fixed
+
+- A job numbered by `--dedupe-jobnames` (`X2`) that a full export of another environment names
+  otherwise lost its original JOBNAME when kept: production's export changed.
+- Values taken inside the children of a job (a mail of an ON block) were put back when the
+  job's children were kept as they were.
+
+## [0.1.1] - 2026-11-03
+
+### Added
+
+- `validate` reports `similar-names` (warning): conditions whose names differ only by the
+  suffix a copy of a chain appended (`…_OK-U26`, `…_OK-U26-U31`) or by case (`_OK`, `_Ok`).
+  The fix `number-similar` gives them the common name with a number (`…_OK1`, `…_OK2`, …) in
+  every job that uses them; a condition with an end outside the repository keeps its name.
+  Names made of their own jobs (`A-TO-LOAD-S1`, `A-TO-LOAD-S2`) are not reported.
+
+### Changed
+
+- A numbered standard name (`A-B_OK2`, `A-TO-B2`) is a standard name for `validate`.
+
+### Fixed
+
+- Resolving several findings at once failed ("a batch cannot contain another batch") when a
+  fix was itself several changes (numbering repeated JOBNAMEs or similar names): a batch now
+  runs the changes of a batch inside it in its place.
+
 ## [0.1.0] - 2026-11-03
 
 First release on PyPI.
@@ -182,5 +228,7 @@ First release on PyPI.
 - On Windows, unknown `/api/...` paths and missing assets were answered with the app instead of
   404 (the static files handler sees `\` separators there).
 
-[Unreleased]: https://github.com/bilouro/controlm-chain-admin/compare/v0.1.0...HEAD
+[Unreleased]: https://github.com/bilouro/controlm-chain-admin/compare/v0.1.2...HEAD
+[0.1.2]: https://github.com/bilouro/controlm-chain-admin/compare/v0.1.1...v0.1.2
+[0.1.1]: https://github.com/bilouro/controlm-chain-admin/compare/v0.1.0...v0.1.1
 [0.1.0]: https://github.com/bilouro/controlm-chain-admin/releases/tag/v0.1.0

{controlm_chain_admin-0.1.0 → controlm_chain_admin-0.1.2}/DESIGN.md

@@ -287,6 +287,27 @@ still exports prod byte for byte; uat comes out identical in 257 of 329 folders
 production has them, listed by `validate`). Sub-element variants (an ON block for one
 environment only) remain open.
 
+**Only the values of an environment** (2026-11-03, asked by the author for the company, where
+the full exports of uat and bench carry releases production does not have yet):
+`receive --values-only` (the *Only the values of <env>* box of the Import page) takes from an
+export what makes a constant — machines, users, mails, variables, the environment's name in a
+text — and leaves everything else out by default: differences and children ignored, jobs it
+lacks kept (*removed*: `keep`), folders it lacks kept (*absent*: `keep`), folders and jobs only
+it has left out (*added*: `skip`, also offered in any full export; with values only it is a
+decision in a delivery too); a repeated difference of another attribute is ignored rather than
+made exceptions. The releases then come from their deliveries, one release branch each (the
+`bootstrap` skill, step 6). Two decisions came with it, for every receive: *adopt* (one per
+constant) — a job no earlier export of the environment had still has production's value of a
+constant where this export has the constant, in the whole value or inside a text
+(`[P77][PROD]` for `[P77][@{env.subject}]`): using the constant leaves production as it was, so
+it is the default (it replaces the exceptions a full export made there); and values taken
+inside children whose shape is kept (a release's new condition on the job that sends the mail)
+stay taken. A job numbered by the deduplication (`P77_F2`) that another environment names
+otherwise keeps its original JOBNAME when it is kept. On the real exports: prod first, then
+uat and bench with values only, give 42 + 15 constants, no exception, prod byte for byte, uat
+identical in 234 of 329 folders (the rest are its releases and its own folders) and bench in
+287 of 341.
+
 ## 6. Import
 
 - Lossless by default: re-importing the XML produced by `export` yields no changes
@@ -363,6 +384,20 @@ environment only) remain open.
   back (`restore-word`). A MEMNAME that merely differs from its JOBNAME is not reported: on the
   real chain 647 of them are script names. On the uat data: 39 replaced words, 4 letters in
   place of the P, 1 foreign letter, 2 foreign resources (107 before `leading_only`).
+- Similar names (implemented 2026-11-03, asked by the author: "detecta nomes similares no
+  validate e sugere nomes como nome1, nome2"): `similar-names` (warning, one finding per
+  family) groups the conditions whose names are equal once the suffixes a copy appended
+  (`-<letter><digits>`, repeated: `…_OK-U26-U31`) are removed and case is ignored; a family
+  whose every name is made of its own producer and consumer is left out (`A-TO-LOAD-S1`,
+  `A-TO-LOAD-S2` only look alike because the jobs do). The fix `number-similar` renames them,
+  shortest name first, to the stem of the first with a number (`…_OK1`, `…_OK2`; a number
+  another condition has is skipped) in every job that uses them; a condition with an end
+  outside the repository keeps its name, as a job outside may use it. `validate` accepts a
+  numbered standard name (`A-B_OK2`, `A-TO-B2`), so a numbered copy that still embeds the
+  original's jobs shows as `stale-name`, with its standard name offered. On the real chain:
+  51 families, 115 conditions; one family is left after the fix (its other members only have
+  a producer). Fixes that are several changes may now be resolved together: a `batch` runs a
+  batch inside it in its place.
 - `diff A B`: plain `git diff` of the base is the first-class review tool. For XML↔XML semantic
   comparison the tool depends on `xmldiffreport` (key-aligned, N-way, Markdown/HTML report).
 - `show --envs <node>`: the node resolved in every environment, side by side, differences
@@ -686,7 +721,7 @@ the first import.
 Quality
 - `validate [--env <env>] [--strict]` — graph, naming, overlay and resolution checks; exit code = highest severity.
 - `resolve [CODE=KIND...] [--apply] [--stat]` — implemented: fixes for the findings (see §8); without arguments, the fix kinds per code.
-- `receive <xml> [--env ENV] [--full|--partial] [--choose ID=OPTION ...] [--apply] [--stat] [--format text|json]` — implemented: an export of one environment (some folders or all) taken into the checked-out release (§5): the decisions with their defaults, then the change set. A group's id holds `=`: `--choose 'group:RUN_AS=a>b=new:user.batch_user_proc'`.
+- `receive <xml> [--env ENV] [--full|--partial] [--values-only] [--choose ID=OPTION ...] [--apply] [--stat] [--format text|json]` — implemented: an export of one environment (some folders or all) taken into the checked-out release (§5): the decisions with their defaults, then the change set. `--values-only`: the environment's values and nothing else by default. A group's id holds `=`: `--choose 'group:RUN_AS=a>b=new:user.batch_user_proc'`.
 - `env learn <xml> [--env ENV] [--only PREFIX ...] [--apply]` — implemented: only the values of the constants in that environment (`--only user.` keeps some constants, e.g. when the export is anonymised).
 - `set-exception <env> <node> [--set ATTR=VALUE] [--unset ATTR] [--var %%NAME=VALUE] [--drop NAME]` — implemented: an exception of one environment for one job or folder (§5), previewed, `--apply` writes `envs/<env>/overrides.json`.
 - `rename-constant <old> <new>` — implemented: placeholders, `chain.json`, environment values and exceptions follow.

{controlm_chain_admin-0.1.0 → controlm_chain_admin-0.1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: controlm-chain-admin
-Version: 0.1.0
+Version: 0.1.2
 Summary: Manage BMC Control-M job chains as a git-friendly JSON repository: XML import/export, links between jobs, environment-neutral base, validation and refactorings.
 Project-URL: Homepage, https://github.com/bilouro/controlm-chain-admin
 Project-URL: Documentation, https://github.com/bilouro/controlm-chain-admin#readme
@@ -85,8 +85,9 @@ export into:
   other branch (one attribute, one job without its folder, one condition) can be taken into
   yours, conflicts shown value by value.
 - **Validation and refactorings** that the Control-M UI does not offer: dangling or stale
-  conditions, chains broken by renames, renaming a sub-application across a folder, moving
-  a job, inserting a job in a chain.
+  conditions, chains broken by renames, condition names that differ only by a copy's suffix
+  or by case (numbered as the fix), renaming a sub-application across a folder, moving a job,
+  inserting a job in a chain.
 - **Byte-identical export.** Untouched definitions export exactly as they were imported.
 
 ## Install
@@ -111,8 +112,9 @@ python -m venv .venv && .venv/bin/pip install -e ".[dev,web]"
 ```
 
 The `bootstrap` skill (`.claude/skills/bootstrap/SKILL.md`) takes it from there, for a person
-or Claude Code: the gate, then a new chain repository built from the full export of each
-environment, production first.
+or Claude Code: the gate, then a new chain repository: production first, the values of the
+other environments from their full exports, then the releases on their way from their
+deliveries.
 
 ## Quickstart
 
@@ -136,6 +138,7 @@ ctmchain package main release/2026-11 --env uat --repo ./my-chains  # import fil
 ctmchain release installed uat --repo ./my-chains                   # tag uat/2026-11-1
 ctmchain receive delivery.xml --repo ./my-chains                    # a team's folders, made neutral
 ctmchain receive uat_full.xml --full --repo ./my-chains             # all of uat: constants, what only uat has
+ctmchain receive uat_full.xml --values-only --repo ./my-chains      # only uat's machines, users, mails
 ctmchain take release/2026-10 --list --repo ./my-chains             # what another release changed
 ctmchain take release/2026-10 --item job:P77_CHAIN/P77_D --repo ./my-chains   # one job of it; --apply
 ctmchain release close --repo ./my-chains                           # once installed in prod

{controlm_chain_admin-0.1.0 → controlm_chain_admin-0.1.2}/README.md

@@ -39,8 +39,9 @@ export into:
   other branch (one attribute, one job without its folder, one condition) can be taken into
   yours, conflicts shown value by value.
 - **Validation and refactorings** that the Control-M UI does not offer: dangling or stale
-  conditions, chains broken by renames, renaming a sub-application across a folder, moving
-  a job, inserting a job in a chain.
+  conditions, chains broken by renames, condition names that differ only by a copy's suffix
+  or by case (numbered as the fix), renaming a sub-application across a folder, moving a job,
+  inserting a job in a chain.
 - **Byte-identical export.** Untouched definitions export exactly as they were imported.
 
 ## Install
@@ -65,8 +66,9 @@ python -m venv .venv && .venv/bin/pip install -e ".[dev,web]"
 ```
 
 The `bootstrap` skill (`.claude/skills/bootstrap/SKILL.md`) takes it from there, for a person
-or Claude Code: the gate, then a new chain repository built from the full export of each
-environment, production first.
+or Claude Code: the gate, then a new chain repository: production first, the values of the
+other environments from their full exports, then the releases on their way from their
+deliveries.
 
 ## Quickstart
 
@@ -90,6 +92,7 @@ ctmchain package main release/2026-11 --env uat --repo ./my-chains  # import fil
 ctmchain release installed uat --repo ./my-chains                   # tag uat/2026-11-1
 ctmchain receive delivery.xml --repo ./my-chains                    # a team's folders, made neutral
 ctmchain receive uat_full.xml --full --repo ./my-chains             # all of uat: constants, what only uat has
+ctmchain receive uat_full.xml --values-only --repo ./my-chains      # only uat's machines, users, mails
 ctmchain take release/2026-10 --list --repo ./my-chains             # what another release changed
 ctmchain take release/2026-10 --item job:P77_CHAIN/P77_D --repo ./my-chains   # one job of it; --apply
 ctmchain release close --repo ./my-chains                           # once installed in prod

{controlm_chain_admin-0.1.0 → controlm_chain_admin-0.1.2}/src/controlm_chain_admin/__init__.py

@@ -1,3 +1,3 @@
 """controlm-chain-admin — manage BMC Control-M job chains as a git-friendly JSON repository."""
 
-__version__ = "0.1.0"
+__version__ = "0.1.2"

{controlm_chain_admin-0.1.0 → controlm_chain_admin-0.1.2}/src/controlm_chain_admin/cli.py

@@ -253,6 +253,12 @@ def build_parser() -> argparse.ArgumentParser:
         dest="full",
         help="some folders only, e.g. a delivery",
     )
+    rec.add_argument(
+        "--values-only",
+        action="store_true",
+        help="take the values of the environment (machines, users, mails, its name in texts) "
+        "and leave the rest out by default: for an environment with releases production has not",
+    )
     rec.add_argument(
         "--choose",
         action="append",
@@ -564,8 +570,8 @@ def cmd_env_help(args: argparse.Namespace) -> int:
 
 _SHOWN_PER_KIND = 20
 _DECISION_ORDER = (
-    "learn", "set-value", "group", "constant", "unmatched", "value", "children", "removed",
-    "added", "absent",
+    "learn", "set-value", "adopt", "group", "constant", "unmatched", "value", "children",
+    "removed", "added", "absent",
 )  # fmt: skip
 
 
@@ -581,6 +587,9 @@ def _decision_line(decision: intake_mod.Decision) -> str:
         return f"{head}  {decision.constant}: {decision.expected} -> {decision.incoming}{uses}"
     if decision.kind in ("value", "constant"):
         return f"{head}  {decision.current} -> {decision.incoming}"
+    if decision.kind == "adopt":
+        uses = _plural(decision.count, "use")
+        return f"{head}  {decision.incoming} where the repository has {decision.current} ({uses})"
     if decision.kind == "unmatched":
         uses = _plural(decision.count, "use")
         return (
@@ -607,6 +616,7 @@ def _print_intake(intake: intake_mod.Intake) -> None:
         f"Folders: {len(intake.folders)} ({statuses['new']} new, {statuses['changed']} changed, "
         f"{statuses['same']} unchanged)"
         + (", full export" if intake.full else ", some folders only" if intake.partial else "")
+        + (", values only" if intake.values_only else "")
     )
     if intake.decisions:
         print(
@@ -630,12 +640,12 @@ def cmd_receive(args: argparse.Namespace) -> int:
     repo = load_repo(args.repo)
     data = args.xml.read_bytes()
     choices = _pairs(args.choose, "ID=OPTION", last=True)  # ids may hold "=", options do not
-    intake = intake_mod.analyze(repo, data, args.env, args.full)
+    intake = intake_mod.analyze(repo, data, args.env, args.full, args.values_only)
     if args.format == "text":
         _print_intake(intake)
     if args.apply:
         workspace_mod.ensure_editable(repo)
-    change = intake_mod.receive(repo, data, intake.env, choices, intake.full)
+    change = intake_mod.receive(repo, data, intake.env, choices, intake.full, args.values_only)
     if args.format == "json":
         result = refactor_mod.apply(repo, change) if args.apply and change.edits else None
         body = {"intake": intake.to_json(), "change": change.to_json(), "applied": bool(result)}

{controlm_chain_admin-0.1.0 → controlm_chain_admin-0.1.2}/src/controlm_chain_admin/core/fixes.py

@@ -26,10 +26,12 @@ from controlm_chain_admin.core.repo import ChainRepo, read_json
 from controlm_chain_admin.core.validate import (
     Finding,
     NameRules,
+    copy_stem,
     embeds_endpoints,
     parse_condition_name,
     replaced_words,
     resources,
+    similar_names,
     validate,
 )
 
@@ -101,6 +103,7 @@ class _Index:
     jobs: dict[str, list[str]]  # folder -> job ids
     repo: ChainRepo | None = None
     names: NameRules | None = None
+    similar: dict[str, list[Link]] = field(default_factory=dict)  # stem -> similar conditions
 
 
 def _index(repo: ChainRepo) -> _Index:
@@ -114,7 +117,16 @@ def _index(repo: ChainRepo) -> _Index:
         for job in ids:
             by_name.setdefault(job.split(DUPLICATE_SEPARATOR)[0], []).append(NodeRef(folder, job))
     used = {link.name: link.id for link in links.values()}
-    return _Index(links, standard_names(links), used, by_name, jobs, repo, NameRules.of(repo))
+    return _Index(
+        links,
+        standard_names(links),
+        used,
+        by_name,
+        jobs,
+        repo,
+        NameRules.of(repo),
+        similar_names(links),
+    )
 
 
 def _waiting(finding: Finding, link: Link, index: _Index) -> list[Fix]:
@@ -277,6 +289,50 @@ def _numbering(finding: Finding, index: _Index) -> list[Fix]:
     ]
 
 
+def _numbering_similar(finding: Finding, index: _Index) -> list[Fix]:
+    stem, family = finding.name, index.similar.get(finding.name, [])
+    kept = [link for link in family if link.external]
+    taken = {name.upper() for name in index.used}
+    renames: list[tuple[Link, str]] = []
+    number = 1
+    for link in (link for link in family if not link.external):
+        while True:
+            name = f"{stem}{number}"
+            if copy_stem(name) != name:  # the stem ends with -<letter>: keep the number apart
+                name = f"{stem}_{number}"
+            number += 1
+            if name.upper() not in taken:
+                break
+        renames.append((link, name))
+    if not renames:
+        return []
+    op, params = _operation(
+        [("rename-link", {"link": link.id, "name": name}) for link, name in renames]
+    )
+    explanation = (
+        f"Gives each condition the common name with a number at the end ({stem}1, {stem}2…), "
+        "in every job that uses it, so that no two names differ only by a suffix or by case."
+    )
+    explanation += "".join(
+        f" {link.name} keeps its name: a job outside this repository may use it." for link in kept
+    )
+    return [
+        Fix(
+            "number-similar",
+            "Number the similar names",
+            "; ".join(f"rename {link.name} -> {name}" for link, name in renames),
+            explanation,
+            op,
+            params,
+            tuple(
+                Effect(str(node), "change", "condition name", link.name, name)
+                for link, name in renames
+                for node in _users(link)
+            ),
+        )
+    ]
+
+
 def _rename_to(link: Link, name: str, index: _Index, kind: str, title: str, why: str) -> list[Fix]:
     if name == link.name or index.used.get(name, link.id) != link.id:
         return []  # nothing to do, or the name belongs to another link
@@ -367,6 +423,8 @@ def _name_fixes(finding: Finding, index: _Index) -> list[Fix]:
 def _fixes(finding: Finding, index: _Index) -> list[Fix]:
     if finding.code == "duplicate-jobname":
         return _numbering(finding, index)
+    if finding.code == "similar-names":
+        return _numbering_similar(finding, index)
     if finding.code in (
         "foreign-letter",
         "letter-for-p",

{controlm_chain_admin-0.1.0 → controlm_chain_admin-0.1.2}/src/controlm_chain_admin/core/guide.py

@@ -23,7 +23,9 @@ Environments: {environments}. Production is {production}: `{trunk}` mirrors it.
    it) and closed into `{trunk}` once {production} has it (`ctmchain release close`).
 3. Exports come in through `ctmchain receive <xml>` or the *Import* page: preview, decide,
    `--apply`, commit. A full export of an environment other than {production} leaves
-   {production} alone by default; a delivery (some folders) changes the release.
+   {production} alone by default; a delivery (some folders) changes the release. When that
+   environment has releases {production} has not, take only its values (`--values-only`, box
+   *Only the values* of the *Import* page): the releases come from their deliveries.
 4. Never hand-edit `index.json` (derived) or `meta/` (volatile attributes, export header);
    edit through `ctmchain` or the web UI, which preview every change.
 5. Exports are big: read them with scripts and counts, never whole.
@@ -45,6 +47,7 @@ Environments: {environments}. Production is {production}: `{trunk}` mirrors it.
 ctmchain release status                        # branch, releases, what may be edited
 ctmchain receive exports/uat/delivery.xml      # preview the decisions of an export
 ctmchain receive exports/uat/delivery.xml --apply
+ctmchain receive exports/uat/full.xml --values-only   # machines, users, mails of uat only
 ctmchain take release/<other> --list           # what another release changed, item by item
 ctmchain validate                              # broken chains, dirty names, suggested fixes
 ctmchain export --env uat -o uat.xml