- Add error logging to catch blocks in intent-router.js and pipeline-reporter.js
- Remove redundant devId+devInfo fallback in handleBingshuoComment (now handled by parseIntent)
- Fix email step progress reporting to use steps.email.outcome instead of steps.persona.outcome
- Standardize last_synced field access
Co-authored-by: qinfendebingshuo <207279273+qinfendebingshuo@users.noreply.github.com>
Bug A: syslog-issue-pipeline.yml now posts individual progress comments
for each step (1-8) instead of a static table that never updates.
zhuyuan-issue-reply.yml syslog-ack simplified to receipt confirmation.
Bug B: zhuyuan-issue-reply.js now uses intent-router.js to parse @铸渊
queries. Pipeline status queries (#92闭环状态) are routed correctly
instead of dumping team overview data.
Co-authored-by: qinfendebingshuo <207279273+qinfendebingshuo@users.noreply.github.com>
When a developer submits a SYSLOG via the 🚀 开发者入口, the system now:
1. Posts an immediate "📡 系统已收到" acknowledgment with full progress checklist (via zhuyuan-issue-reply.yml syslog-ack job)
2. Posts real-time progress updates as each pipeline stage completes (via syslog-issue-pipeline.yml)
3. Updates the progress comment to show all stages completed on success
4. Updates the progress comment to show error status on failure
Root cause: syslog-issue-pipeline.yml was never triggered by issues events (0 out of 36 runs were issue-triggered). The syslog-ack safety net in zhuyuan-issue-reply.yml ensures developers always get immediate feedback even if the main pipeline fails to trigger.
Co-authored-by: qinfendebingshuo <207279273+qinfendebingshuo@users.noreply.github.com>
- Add pm2-server-diagnose.yml workflow for SSH-based PM2 diagnosis
- Add server-diagnose-report.js script for Notion ticket creation
- Fix port conflict: guanghulab (src/index.js) now uses port 3001
- Update ecosystem.config.js to align with deploy workflow process names
Co-authored-by: qinfendebingshuo <207279273+qinfendebingshuo@users.noreply.github.com>
Problem: When developers submit SYSLOG via the 🚀 开发者入口, zhuyuan-issue-reply.yml
intercepts the issue and responds with "已记录。霜砚会在下次巡检时处理" instead of letting
syslog-issue-pipeline.yml handle the full auto-processing loop.
Root causes:
1. zhuyuan-issue-reply.yml triggers on ALL new issues with no exclusion for SYSLOG
2. syslog-issue-pipeline.yml only detects via 'syslog' label which may not exist in repo
3. zhuyuan-issue-reply.js has no guard against SYSLOG issues, falls through to generic fallback
Fixes:
- zhuyuan-issue-reply.yml: Exclude issues with syslog/bingshuo-deploy labels, SYSLOG/系统日志
in title, or '### 广播编号' in body (template field marker)
- syslog-issue-pipeline.yml: Detect SYSLOG issues by label OR title OR body pattern
- zhuyuan-issue-reply.js: Add isSyslog guard in handleIssueTrigger() as defense-in-depth
Co-authored-by: qinfendebingshuo <207279273+qinfendebingshuo@users.noreply.github.com>
铸渊 (ZhùYuān)
bingshuo-neural-system
冰朔
copilot-swe-agent[bot]
铸渊[bot]