← back to Dw Signup Fulfillment
verification/tk11185-reconcile/RETIRED-COMMANDS.md
30 lines
# Retired TK-11185 theme commands
`scripts/gate2-theme-put.mjs` and `scripts/gate2-theme-rollback.mjs` are intentionally retired. Both print a superseded message and exit 78 before imports, credential reads, network requests, or forwarding. Extra flags do not reactivate them.
TK-11283 published the required full designer application and account/login flow. The former PUT checked only the main theme ID; the former rollback checked neither the main theme nor the current asset. Both could replace newer content with a historical snippet. Original files remain recoverable through `git show 5e609e8:scripts/gate2-theme-put.mjs` and the corresponding rollback path for historical review. Do not execute recovered historical scripts.
## Current supported procedure
Read current Shopify values using the guarded tool from any directory:
```sh
node ~/Projects/dw-signup-fulfillment/verification/tk11283/publish-theme.cjs --status
```
This mode performs Shopify GETs and saves current snapshots locally. Retired commands display this command; they never invoke it. Review [TK-11283 evidence](../tk11283/REVIEW.md), its preserved baselines, and current hashes before considering any change.
The unchanged `verification/tk11283/publish-theme.cjs` owns the current two-asset deploy/rollback workflow. Its `--apply` and `--rollback` modes mutate the live theme and require explicit authorization for the exact action. Preserve its baseline, theme identity, content-hash, review-evidence and post-write checks. Retirement is not permission to run either mode.
## Verification and limits
```sh
node --experimental-vm-modules verification/tk11185-reconcile/retired-check.cjs
```
The runner loads actual historical modules from Git in an isolated VM with synthetic `fs`/`os` imports and mocked Shopify responses. It starts with the current proposed designer-flow body and proves the historical commands overwrite it without inspecting its current value. No real credential or API is used.
It then invokes each real retired entrypoint with Node, including `--apply` and `--rollback`, from the repository and `/private/tmp`. A preload blocks and records application file/credential and network attempts; plain invocations verify normal startup. Assertions require exit78, a superseded message, zero app-file/network attempts, and an unchanged guarded tool. Results are in [retired-e2e-proof.json](retired-e2e-proof.json).
A repository-wide `rg` search found no callers of these exact filenames before retirement. This is local inventory only; external pasted commands or automation are not exhaustively inventoried. Exit78 deliberately reports failure to those callers and should not be retried. No customer/account/OTP journey changed. TK-11185's separate retained production smoke-record cleanup remains with the parent ticket; this report does not claim the whole ticket complete.