You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Review documentation gaps for product defects and missing capabilities #213
Documentation reports can expose missing capabilities or runtime defects. Resolving the prose alone can leave the underlying user need unexamined.
Add a shared contributor rule: assess the user need and product contract before choosing documentation, a bug fix or a feature; record the decision and link implementation work. Current limitations should be documented honestly while implementation is pending. A workaround does not complete an accepted product requirement.
Acceptance: the organization guide states this review responsibility without requiring every limitation to become a feature or adding a separate tracking system.
Workflow #863: opt-in durable cleanup under an immutable total cap.
These seven wrappers are closed as superseded, not as implemented product fixes. Their useful current-behavior corrections and final documentation are retained in the implementation acceptance. Prepared durable-workflow/durable-workflow.github.io#307 and durable-workflow/sdk-python#169 explicitly remain interim truth, not delivery of #215.
Existing shared #216 owns safe signal/update retries exposed by closed Document safe signal and update retries after ambiguous responses durable-workflow.github.io#266. Corrected its baseline: released Core 2.7.2/Server 2.9.7 already deduplicate ordinary updates; signal deduplication, portable key reuse, intent conflicts and remaining lifecycle/readback behavior are the actual work. External business-effect idempotency remains necessary.
Server #518 remains a P1 product fix, including safe get_version evolution under the default policy. Keeping old workers is not its resolution.
This creates eight correctly owned new product tickets, expands two existing SDK tickets, and reuses the existing clock/update/timeout/identity defects instead of duplicating them. Every new ticket states evidence limits and concrete implementation/qualification acceptance.
Retry-default decision: keep one attempt for current 2.x applications. Automatically repeating external effects is a compatibility change; finite retries do not establish idempotency. durable-workflow/durable-workflow.github.io#301, durable-workflow/durable-workflow.github.io#304 must accurately show explicit bounded retry/backoff and total budgets. No automatic retry-default change was accepted for this train.
The shared contributor rule is delivered through #214 at 3e950f03fb64a78667702c5fe909ec0a5d5eee9c. This audit closes triage, not the newly accepted implementations. Product tickets remain open until their real acceptance is delivered.
Activity
rmcdaniel commentedon Oct 20, 2026
Applied the product-review rule to the documentation backlog
Reviewed all 24 then-open documentation-labelled issues across the Website/PHP/Python SDK repositories, plus the five recently closed guidance issues durable-workflow/durable-workflow.github.io#258, durable-workflow/durable-workflow.github.io#264, durable-workflow/durable-workflow.github.io#266, durable-workflow/durable-workflow.github.io#281, durable-workflow/durable-workflow.github.io#284. The separate closed website dependency-security issue durable-workflow/durable-workflow.github.io#261 was also checked; it already had a real dependency fix and qualified publication.
Docs wrappers superseded by actual product work
These seven wrappers are closed as superseded, not as implemented product fixes. Their useful current-behavior corrections and final documentation are retained in the implementation acceptance. Prepared durable-workflow/durable-workflow.github.io#307 and durable-workflow/sdk-python#169 explicitly remain interim truth, not delivery of #215.
Further product corrections and features
get_versionevolution under the default policy. Keeping old workers is not its resolution.This creates eight correctly owned new product tickets, expands two existing SDK tickets, and reuses the existing clock/update/timeout/identity defects instead of duplicating them. Every new ticket states evidence limits and concrete implementation/qualification acceptance.
Genuine documentation retained
durable-workflow/durable-workflow.github.io#169, durable-workflow/durable-workflow.github.io#256, durable-workflow/durable-workflow.github.io#257, durable-workflow/durable-workflow.github.io#259, durable-workflow/durable-workflow.github.io#262, durable-workflow/durable-workflow.github.io#267, durable-workflow/durable-workflow.github.io#270, durable-workflow/durable-workflow.github.io#274, durable-workflow/durable-workflow.github.io#276, durable-workflow/durable-workflow.github.io#278, durable-workflow/durable-workflow.github.io#280, durable-workflow/durable-workflow.github.io#283, durable-workflow/durable-workflow.github.io#301, durable-workflow/durable-workflow.github.io#308 remain documentation or executable-example work on existing capabilities, with a recorded reason in each issue. Related actual defects remain linked, including durable-workflow/server#504 and durable-workflow/server#514 and durable-workflow/workflow#856 and durable-workflow/workflow#859. Removed the stale claim that delivered SQS chunking durable-workflow/workflow#851 is still open. durable-workflow/durable-workflow.github.io#277 is closed as actually delivered through durable-workflow/durable-workflow.github.io#291 and verified public publication; no unsupported sticky-owner hold was invented.
Retry-default decision: keep one attempt for current 2.x applications. Automatically repeating external effects is a compatibility change; finite retries do not establish idempotency. durable-workflow/durable-workflow.github.io#301, durable-workflow/durable-workflow.github.io#304 must accurately show explicit bounded retry/backoff and total budgets. No automatic retry-default change was accepted for this train.
The shared contributor rule is delivered through #214 at
3e950f03fb64a78667702c5fe909ec0a5d5eee9c. This audit closes triage, not the newly accepted implementations. Product tickets remain open until their real acceptance is delivered.