2.6 KiB
2.6 KiB
Evidence Index
Use this index for searchable, traceable evidence records.
| Date | Topic | Status | Source | Detail |
|---|---|---|---|---|
| 2026-08-28 | Legacy project memory migration | Verified byte-for-byte | Archive index | Final root planning files were hashed, copied, and compared before retirement. |
| 2026-08-28 | Current release capability and real-validation boundary | Current integrated evidence | Lifecycle release gate | Defines active conclusions and links immutable evidence. |
| 2026-08-28 | Release artifact hashes and sources | Machine-verified | Release manifest | Seven current artifacts and their source/hash metadata. |
| 2026-08-28 | AgentBus reconnect and runtime switch | Verified at observation time; time-sensitive | Archived legacy progress | Repeated 4/4-ready samples after authorized restart; live status must be rechecked when needed. |
| 2026-08-30 | Chrome extension 0.5.163 and ACK deployment constraints |
Source/release verified; not deployed by this task | ACK and release task | Records synchronized versions, package/source comparison, PostgreSQL/OSS requirements, migration ordering, and current single-replica constraint. |
| 2026-08-31 | WeChat attachment correlation | Repository verified; not deployed by this task | Attachment-correlation task | Strict conversation fallback and placeholder-only failure preserve the waiting task and prevent accidental task creation. |
| 2026-08-31 | Privacy-safe server diagnostics | Repository verified; not deployed by this task | Diagnostics task | Structured lifecycle diagnostics, redaction, bounded Docker retention, and read-only server inspection command. |
| 2026-08-31 | Production attachment failure | Root cause verified from supplied log | Log-inspection task | The original task remained waiting; the later structured attachment failed because DNS returned a private/reserved address. |
When To Add Evidence
Add a topic file when a task depends on logs, commits, test output, external docs, bug reproduction, experiments, or postmortem-level reasoning.
Keep task progress in 30-worklog/; keep reusable workflow lessons in 60-reflection/.