Commit Graph

3 Commits

Author SHA1 Message Date
Shahab Tajik
d344f08be8 Ensure WD Version properly revives if recreated after deletion (#9382)
## What changed?
- Ensure the TQs receive and apply the right version data after revive.
- Made delete propagation to always happen serial to other propagations.
It ensures all other propagations are cancelled before starting delete
propagation.
- Deprecate the `deleted` flag in version data and the GC logic around
it. Now we use the good old forgetVersion path which immediately removes
the version data from TQ.
- Ensure version state is reset after revive, in case the recreation
happened before workflow close.
- Also, now workflows CaN based on SDK suggestion if no pending Signal
or Update is present.

## Why?
The version could stuck at deleted state from TQ POV if revived before
the (now deprecated) GC logic cleans it up.

## How did you test it?
- [ ] built
- [ ] run locally and tested manually
- [ ] covered by existing tests
- [x] added new unit test(s)
- [x] added new functional test(s)

## Potential risks
None

---------

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-26 16:01:17 -07:00
Alex Stanfield
f3d37d9067 Update AGENT.md (#8881) 2026-01-03 18:39:29 -06:00
Yimin Chen
36f02e458d Add AGENTS.md (#8505)
## What changed?
Add AGENTS.md for AI coding agents.

## Why?
AI coding agents perform better with clear instructions in AGENTS.md

## How did you test it?
- [ ] built
- [ ] run locally and tested manually
- [ ] covered by existing tests
- [ ] added new unit test(s)
- [ ] added new functional test(s)

## Potential risks
No
2025-10-20 17:22:30 -07:00