fix: refresh public dashboard and BI telemetry
This commit is contained in:
@@ -4,6 +4,15 @@ Use this index for searchable, traceable evidence records.
|
||||
|
||||
| Date | Topic | Status | Source | Detail |
|
||||
|---|---|---|---|---|
|
||||
| 2026-08-03 | Booking source and company-report retry semantics | Source contract confirmed; reuse visibility gap identified; live acceptance pending restart | [Evidence topic](topics/2026-08-03-company-report-retry-semantics.md) | Byte-identical XLSX uploads reuse the activated source; same rows with different file bytes are new drafts. Same report snapshots reuse complete publication pairs, changed Finance/Booking pins create new versions, and an activated subset changes Booking detail coverage while retaining Finance rows. The current API/UI do not expose whether a retry reused an existing artifact. |
|
||||
| 2026-08-03 | Company-report retry after reported 8766 restart | Resolved by controlled listener replacement and live 5/5 rerun | [Evidence topic](topics/2026-08-03-company-source-runtime-diagnosis.md) | PID 11176 was replaced by PID 54127. Job `05cc547d…` succeeded all five August `01-10` companies, reused the prior version/artifact identities, and all five authenticated downloads returned hash-matching 200 responses. No Booking/Finance source or fact changed. |
|
||||
| 2026-08-03 | Remove redundant company-report Excel provenance module | Implemented; Web/company checks pass | [Evidence topic](topics/2026-08-03-company-report-status-copy-fix.md) | The job-detail source card and history source column are removed because reports consume the Booking database snapshot; upload/review source UI and server-side provenance remain available. |
|
||||
| 2026-08-03 | Company-report source and publish-failure copy | Simplified; source display superseded by module removal | [Evidence topic](topics/2026-08-03-company-report-status-copy-fix.md) | The end-user source display was later removed. Publish failures now say the data was processed, the official Excel save failed, and the report service should be restarted before generating again; internal duplicate-reuse rules are not shown. |
|
||||
| 2026-08-03 | Channel BI freshness after August publication | Diagnosed and repaired; focused checks pass | [Evidence topic](topics/2026-08-03-channel-bi-freshness.md) | Active August V02 is `更新至 2026-08-02` with 268 rows, and a fresh analytics snapshot returns the same watermark. Desktop and public H5 now check lightweight month metadata every five seconds and reload only after selected-month `updated_at` changes; hidden views pause and transient failures preserve the last good snapshot. |
|
||||
| 2026-08-03 | Daily commit waiting for monthly worker | Recovered; persistent supervision pending | [Evidence topic](topics/2026-08-03-daily-monthly-worker-pending.md) | User-authorized detached worker recovery consumed events 15–20. July V05 is active at 987 rows and August V01 is active at 111 rows with registered workbook/result artifacts; all six checked daily-commit events are published, XLSX integrity passes, Web health is ready, and only reboot-persistent worker supervision remains open. |
|
||||
| 2026-08-03 | Monthly worker logging and observability gap | Recommendation pending implementation | [Evidence topic](topics/2026-08-03-monthly-worker-observability.md) | Worker output is sparse Screen stdout, Web request logs go to stderr, and Web readiness excludes worker liveness. Durable outbox/task-trace facts exist but lack heartbeat/process status and monthly-specific wording. Recommended next step is structured retained logs plus heartbeat, status projection and supervisor alerting; no code or runtime change was made. |
|
||||
| 2026-08-03 | Company report source label and live runtime | New runtime accepted; historical null-source jobs remain unchanged | [Evidence topic](topics/2026-08-03-company-source-runtime-diagnosis.md) | New job `05cc547d…` records active Booking batch 7 metadata and succeeds 5/5 after PID 54127 replacement. Older jobs with `source: null` remain historical records and were not guessed or backfilled. |
|
||||
| 2026-08-03 | Daily trace does not explain company-report publication failure | Logging assessment pending implementation | [Evidence topic](topics/2026-08-03-daily-trace-does-not-explain-company-publish.md) | The supplied Daily trace proves Finance commit and outbox publication but has no company-report job linkage or publish-stage detail; it also shows unknown execution metadata and an unmasked full source hash. Recommend separate Daily/monthly/company traces, runtime identity and hash masking; no code/runtime change was made. |
|
||||
| 2026-08-03 | Public mobile H5 dashboard boundary | Implemented; deployment/restart pending | [Evidence topic](topics/2026-08-03-public-h5-dashboard.md) | Anonymous H5 page/assets and purpose-built `/api/public/h5/*` aggregate routes are allowed. The projection omits `source_monthly_sha256`; desktop, generic/legacy APIs, detailed health, jobs/traces, downloads and writes remain protected. `test_arr_web*` discovery passes 71 tests; no live service or business data was changed. |
|
||||
| 2026-08-03 | ARR job trace semantics for internet deployment | Implemented; live deployment acceptance pending | [Evidence topic](topics/2026-08-03-arr-job-trace-semantics.md) | Trace projection adds `execution_scope`, `processor_mode` and `remote_dispatch`; `artifact_callback` is identified as ARR fixed-processor runtime execution and legacy `direct_mcp` as remote Agent/MCP delivery. “本地处理” copy is removed, pending downstream explicitly follows Finance commit, and persisted `local-...` delivery identities are retained. Focused trace/Web tests pass; no live task or business write occurred. |
|
||||
| 2026-08-03 | Booking Excel to company-report traceability | Implemented; authenticated browser acceptance pending | [Evidence topic](topics/2026-08-03-company-source-report-traceability.md) | New report jobs persist a safe source summary captured at submission; current source, job detail and history expose the filename/batch context. Identical active uploads refresh context without re-extraction or automatic generation. Full discovery passes 360 tests with 10 optional skips; no live mutation or restart occurred. |
|
||||
|
||||
Reference in New Issue
Block a user