runtime: normalize structured secret errors
This commit is contained in:
@@ -2,18 +2,18 @@
|
||||
|
||||
## Current
|
||||
|
||||
### `feat/typed-timestamps`
|
||||
### `feat/error-structure-normalization`
|
||||
|
||||
Status: in_progress
|
||||
|
||||
DoD:
|
||||
- domain and registry models use typed timestamps instead of `String`
|
||||
- SQL row decoding uses timestamp types directly where possible
|
||||
- API serialization stays RFC 3339 compatible
|
||||
- runtime and API errors expose structured context where stable fields exist
|
||||
- secret/runtime failure classes are mappable without parsing ad hoc message text
|
||||
- opaque third-party details remain only where no stable structure exists
|
||||
|
||||
## Next
|
||||
|
||||
- `feat/error-structure-normalization`
|
||||
- `feat/correlation-id-propagation`
|
||||
|
||||
## Backlog
|
||||
|
||||
|
||||
Reference in New Issue
Block a user