2.4 KiB
name, description
| name | description |
|---|---|
| erp-diagnostics-maintenance | Use for maintainer-only diagnosis of ERP deployment, route interfaces, form mappings, API probes, performance, or customer resolution; default to no-ERP and read-only checks. |
ERP Diagnostics Maintenance
Scope
This is a maintainer-only diagnostic Skill. It selects existing health checks and probes, reports evidence, and keeps diagnosis separate from customer order execution. It must not create, update, export, or submit a live ERP order as a diagnostic step.
Default no-ERP workflow
Start with the repository tests and:
npm run health:no-erp
node tools/erp_deployment_health_check.js --config config/erp-deployment.example.json --no-erp
Use fixture data and static inspection whenever possible. A no-ERP result may prove configuration, dependency, path, and code health; it does not prove a live ERP session or a successful save.
Tool selection
- Deployment/session environment: erp_deployment_health_check.js.
- Read-only route/API surface: erp_all_routes_api_probe.js and erp_team_single_api_probe.js.
- Form and mapping inspection: erp_inspect_single_form.js and erp_inspect_team_batch_modify.js.
- Split route inspection: erp_split_parent_inspect.js and erp_split_child_inspect.js.
- Split route probing: erp_split_parent_probe.js and erp_split_child_traveler_audit.js.
- Performance evidence: erp_performance_profile.js.
- Customer mapping: erp_customer_resolver.js.
Only use a connected probe when the maintainer gives explicit approval, the tool's scope is understood, the target is non-production or approved, and the result cannot trigger a save. Record the exact command, config, scope, and evidence in the maintenance handoff.
Prohibited diagnostic shortcuts
- Never bypass captcha or ask an operator to weaken login/session safety.
- Never save a sample order, call a submit endpoint, or use live submit as a health check.
- Never claim that HTTP 200 or a probe response proves ERP business success.
- Never delete profile locks, kill Chrome globally, or modify production mappings to make a probe pass.
- Never expose credentials, cookies, traveler PII, or internal paths in a customer-facing reply.
Output
Return the diagnostic scope, no-ERP/live boundary, command/tool selected, evidence, observed failure, and next maintainer action. If the request is actually an order, route it back to erp-coordinator rather than executing from this Skill.