Session boundaries and deferred work
| Key | Type | Default | Behavior |
|---|---|---|---|
session.jobClassGate |
boolean | true |
Keeps authoring commands (setup, plan, ci-audit, rebalance, rationalize-gantt, comprehend-plan) separate from execution commands (build-item, pr, review, release, push, create-story, create-defect, insert-story, insert-defect) in a Claude Code session. Run /clear when switching classes. From 3.18.0 doctor and update are neutral: they never arm or trip the gate, so running Doctor first never blocks the build that follows. |
defects.deferredContainerTitle |
string | "Deferred" (it was "Deferred defects" before 3.24.0) |
Names the one container directly under the plan root that holds deliberately postponed work worth filing: a bug through create-defect deferred <item#>, and from 3.24.0 any other follow-up (tech debt, a clean-up, hardening, a dated after-deploy step) through create-story deferred <item#>. A review finding below the bar (not a P1, not a security finding, not both likely to happen and material) is dismissed with its reason, never filed (from 3.10.0). |
defects.deferredContainerLegacyTitles |
string[] | ["Deferred defects"] |
From 3.24.0: earlier titles that still identify the container, so renaming the title never creates a second one. The built-in Deferred defects is always matched; a configured list only adds to it. Titles match after trimming, collapsing whitespace and ignoring case. An older plugin ignores this key and looks only for its own default, so a repository that sets either key, or relies on the new default, needs 3.24.0 or later. |
The session gate allows one build loop to work through multiple stories. For an intentional exception, pass --same-session, set session.jobClassGate: false, or set DEVSTRIDE_SESSION_GATE=0. The hook fails open on errors.
Deferred items link back to the reviewed item with a related-to relationship. They have no execution-order prefix, dependency-chain splice or delivery phase; the loop neither selects them automatically nor treats their container as a release unit, though an item there that you name by number is still built, as a one-off. rationalize-gantt dates each open one after the plan's last value leaf, and when a plan reaches zero remaining stories build-item's closing report lists what is still open in the container. If two containers match, the lowest-numbered one is used and the others are reported; a closed container is reopened and reused rather than duplicated. Newly discovered scope that belongs in the active plan still goes through insert-story.