Guarantee durable visible runtime logging
This commit is contained in:
@@ -1,6 +1,20 @@
|
||||
|
||||
# Changelog
|
||||
|
||||
## [2.3.1] - 2026-08-26
|
||||
### Added
|
||||
- A real runtime-log write/read roundtrip to the WMI-free installer self-test and a durable startup verification record naming the active daily file.
|
||||
- Regression coverage for startup fallback, append-time failover without record loss and total storage failure diagnostics.
|
||||
- A dedicated PROD storage-validation runbook in Markdown and plain text.
|
||||
|
||||
### Changed
|
||||
- Runtime logging now verifies actual writes and uses the deterministic fallback order ProgramData, LocalAppData, executable-local `Logs`, then Temp.
|
||||
- **Log Folder** opens the currently verified path; fallback and total failure diagnostics include attempted paths and exceptions in the Operation Log grid.
|
||||
|
||||
### Fixed
|
||||
- Successful directory creation can no longer be mistaken for working file logging when the subsequent append is denied.
|
||||
- Runtime append failures are no longer swallowed silently; the failed record is retried on the next local candidate and a durable/visible warning is emitted.
|
||||
|
||||
## [2.3.0] - 2026-08-26
|
||||
### Added
|
||||
- Process-local, assembly-identity-checked resolution and preflight for ScheduledTask `scheduler:` receive locations, including automatic BizTalk/adapter directory and registry discovery plus an explicit configuration override.
|
||||
|
||||
Reference in New Issue
Block a user