Three-layer unified self-check integrated into BOSSAGENTS default tasks (2026-07-13)

User request clarification

"Place it into the default tasks of BOSSAGENTS, not into your tasks" — refers to integration into BOSSAGENTS's own digital employee scheduling system (boss-scheduler), not OpenClaw's cron.

"Even if added, do not start automatically by default; start manually" — the code is in place but the three-layer self-check does not run automatically by default; it is triggered manually by the user.

Operation log

1. Removed the mistakenly added OpenClaw cron task: b036d7fc-... (Three-layer unified self-check inspection) has been removed.
2. Located the BOSSAGENTS default inspection entry point:

• Scheduling system: server/boss-scheduler/ (lite-scheduler.js + workers/)
• Digital employee registration: server/boss-scheduler/profiles/local.yaml
• System inspection employee: DS-SYS-001 Xiao Zhi - System Operations Engineer, worker: system-health, cron: 0 */3 * * * *, enabled: true, checks: [database, SCSAI_connection, template_coverage, rules_v2, consistency]
• worker implementation: server/boss-scheduler/workers/system-health.js (DS-SYS-001 Lightweight Health Check)

1. Path baseline correction (server/scripts/health-check.js):

• DB_PATH: path.resolve(__dirname, '..', 'data', 'rule_engine.db') (scripts→server/data) ✅
• require('../core/rule-engine') (scripts→server/core) ✅
• Report written to path.resolve(__dirname, '..', '..', 'health-report.json') (→ project root) ✅

1. Worker integration of new check unified_health (system-health.js):

• Add a new branch `if (checksEnabled.has('unified_health'))` at the end of the checks dispatch
• Call server/scripts/health-check.js using execFileSync(process.execPath, [scriptPath])
• Read health-report.json, parse summary.health → check.status (HEALTHY=ok / DEGRADED=warning / others=error)
• Report path: path.resolve(__dirname, '..', '..', '..', 'health-report.json') (workers→project root) ✅

1. Did not add unified_health to DS-SYS-001.checks in local.yaml (default not auto-started, complies with user constraints).

Verification results

• Script direct run: health-check.js normally generates health-report.json / .md (L1 all PASS, L2/L3 depend on service availability).
• Worker integration test: checks:['unified_health'] triggers → correctly returns {name:'Three-tier Unified Self-check', status:'warning', health:'DEGRADED', pass:8, warn:10, fail:0}
• WARN Excessive reasons: Port 3006 service is currently not running (L2 six-capability HTTP and L3 governance tool HTTP connections fail), L1 local direct check still PASS
• Service port 3006 is currently NOT listening; no node server process is running

Manual method to start the three-layer self-check (for user selection)

• Method A (for system O&M engineers scheduled inspection): Add a line '- unified_health' to DS-SYS-001.checks in local.yaml, restart the service to automatically include the three-layer self-check every 3 hours
• Method B (single manual execution): node server/scripts/health-check.js
• Method C (single trigger worker): Call runSystemHealth({checks:['unified_health']}, ...) separately

Conclusion

The three-layer unified self-check has been deployed as an optional check item (unified_health) for BOSSAGENTS system O&M engineers, with all code paths aligned, but not enabled by default. This meets the requirement of "including it but not auto-starting." Awaiting user decision on the manual startup method (it is recommended to start the 3006 service first before performing full L2/L3 validation).