← back to Newmor Onboard
README.md
54 lines
# newmor-onboard (TK-10670)
Refresh the existing Newmor line under DWNM-, distributed by LBI Boyd.
Steve confirmed September 8: **showroom line; no material prices required**.
Customer outcome: product discovery and showroom inquiry. No cost-sheet or priced-goods-variant prerequisite.
Steve approved the linked showroom memo on September 9. **116 verified colorways are now live,
Online Store only**, with no material price or material purchase control. Existing Sample variants
and their prices are unchanged. Seven showroom markers and six exact-source Arbour images were added.
Browse: https://www.designerwallcoverings.com/collections/newmor-wallcoverings
Final state: **116 ACTIVE + 189 DRAFT + 237 ARCHIVED = 542**. The 189 drafts are the original
180 holds plus nine Arona candidates whose current range could not be verified. All prices, variant
identities, product content and non-showroom metafields remain unchanged. The broader DWNM/specification
refresh remains separately gated; the parent ticket is not complete.
See [launch report](artifacts/LAUNCH-REPORT-2026-09-09.md), [live manifest](artifacts/LIVE-NEWMOR-2026-09-09.csv),
[R4 evidence](verification/e2e-proof.json), and [independent review](verification/independent-review.md).
The unsent nine-code range request is in [Arona follow-up](artifacts/ARONA-RANGE-FOLLOWUP.md).
The original 125-ID approval scope is preserved in artifacts/SHOWROOM-PLAN.md and
data/newmor-showroom-plan-2026-09-08.json; neither is a new authorization to repeat mutations.
Operational guard: do not overwrite data/live-2026-09-09/shopify-before.json or theme/ originals.
Use `node scripts/final-verify.mjs` for fresh read-only state checks. `preflight.mjs --saved` is
offline only. Rollback applies to all touched journal records and remains an explicitly authorized action.
The initial KOT-23 activation briefly inherited old sales channels; it was rolled back immediately,
then republished with a verified zero-channel activation barrier. External ingestion during that interval
was not audited. Current visible and configured publications are Online Store only for all 116.
Cadence: Newmor is explicitly excluded from the hourly importer; no local newmor-agent or dedicated schedule found.
General Instagram automation exists, but a dedicated Newmor rotation was not verified. No schedules changed.
All specifications belong in metafields; preserve richer existing values. RECONCILIATION.md and METAFIELD-MAP.md
contain historical findings, not current executable worklists. The old quote-terms email is superseded.
## TK-11424 — Norman scraper + spec refresh (2026-09-13)
Built the Norman/newmor-agent daemon (`agent/server.js`, pm2 `newmor-agent`, **:9695**, `GET /health`,
Basic-auth `GET /api/results` + `POST /api/refresh`) and the scraper it runs
(`scripts/spec-pdf-refresh.py`). Recaptured fire_rating/application/match_type/coverage/repeat_v from
Newmor's PDF spec sheets (NOT present as scrapable HTML — see the script's docstring for the PDF
de-garbling technique) into `newmor_catalog` (fill-only-never-clobber; restore-map at
`artifacts/TK-11424-restore-map.json`). Coverage: fire_rating 617→1112, application 0→636,
match_type 0→556, coverage 0→535, repeat_v 0→134, finish confirmed absent from source (left empty,
not fabricated) — out of 1294 rows / 288 patterns. `finish` has no source data anywhere in Newmor's
catalog; do not re-attempt a keyword scan for it without re-verifying against fresh PDFs first (a
naive keyword search over the de-garbled text throws false positives on short words).
The live Shopify metafield backfill (the ticket's "...THEN backfill to live") is GATED — drafted to
`~/.claude/yolo-queue/pending-approval/TK-11424-newmor-spec-metafield-backfill.md`, pending Steve's
call on the "Inquire for more Information" placeholder question. `scripts/backfill-metafields.mjs`
needs its CANDIDATES list extended with the 5 new keys before that step can run (dry-run first).