Admin-only dry-run control

NinjaPipe CRM Realignment Runner

A governed runner surface for the SchoolManager CRM realignment. The operating model is form-first: Companies are schools, Contacts are people, and native contact-company links must be proven before live repair. This page is intentionally dry-run-first and no-delete.

Open NinjaPipe Forms Follow-Up Command Center Registry

Mutation postureNo-delete

Default modeDry-run

Primary dataCurrent form

Live repairSeparate gate

Execution Boundary

This dashboard route is the admin control surface, not the missing deployed NinjaPipe frontend source. The real embedded route inside schoolmanager.ninjapipe.app still requires the maintainable NinjaPipe frontend repository or deployment control. Until then, this route keeps the dry-run procedure visible, reviewable, and tied to the owned internal Dashboard Center.

Dry-Run Sequence

Run the checks in this order. They are designed to produce counters and review classifications, not raw CRM exports. Live confirmation phrases do not belong in this phase.

Form Mapping Audit

File: src/manual-console-scripts/ninjapipe-form-mapping-audit.js
Config: window.NINJAPIPE_FORM_MAPPING_AUDIT_CONFIG
Mode: read-only
Allowed output: summary, targetSubmissionExactCount, warnings, errors, mapping-risk counts
Blocked output: raw response values, browser storage, auth tokens, cookies, names, phones, emails, CRM IDs

Form Intake Reconciliation Dry Run

File: src/manual-console-scripts/ninjapipe-form-intake-reconciliation.js
Config: window.NINJAPIPE_FORM_INTAKE_RECONCILIATION_CONFIG
Mode: dry-run only
Allowed output: summary counts, planned contact/company update counts, warning/error counts, skipped counts
Blocked output: plannedContactUpdates, plannedCompanyUpdates, private values, CRM IDs, liveConfirmation phrases

No-Contact Submission Review Dry Run

File: src/manual-console-scripts/ninjapipe-no-contact-submission-review.js
Config: window.NINJAPIPE_NO_CONTACT_SUBMISSION_REVIEW_CONFIG
Mode: dry-run only
Allowed output: summary, classificationCounts, evidenceCounts, safe link counts, review-only counts
Blocked output: raw names, raw contact details, submission IDs, CRM IDs, liveConfirmation phrases

Stop Rules

Confirm the live form response count is 373 or higher.
Stop if any dry run reports errors.
Stop if any result implies deletion, automation activation, follow-up redesign, or nonblank overwrite.
Treat ambiguous, no-match, incompatible, and insufficient-evidence rows as review-only.
Prepare a separate live approval record only if dry-runs show safe blank-link repairs and no destructive writes.

Current Acceptance Target

The runner is successful when the 373-response cohort and older CRM records are represented in the same form-first model, safe automatic repairs are either completed through a later approved live pass or reduced to zero, and remaining ambiguity is review-only. Follow-up fields, tasks, lists, and automations remain preserved for the later follow-up phase.

Generated 2026-06-25T01:25:07.625Z