* fix(epic): do not treat duplicate/wontfix closes as complete
GetEpicsEligibleForClosure counted any closed child as complete work.
An epic whose only child was closed as duplicate (or wontfix/superseded)
was flagged "complete-but-unclosed" and doctor suggested bd close — even
when the epic still had unfinished scope (GH#5026).
- Fetch close_reason with status; only completing closes count for eligibility
- IsNonCompletingClose for duplicate/wontfix/superseded/obsolete keywords
- Soften doctor/mol stale copy: review scope before closing
Fixes#5026
* fix(epic): word-boundary close-reason matching + conformance coverage (GH#5026)
Review follow-ups from maphew on #5138:
- IsNonCompletingClose now matches close_reason on word boundaries via a
precompiled regexp instead of raw strings.Contains. Bare "dup" is dropped
(redundant with duplicate/dupe, only added false positives on "dedup").
Bare "obsolete" is dropped in favor of "obsoleted" — "removed obsolete
migration shim" is completing work, not a redirect, and was silently
making such epics ineligible forever with no explanation.
- testAuditEpicsEligiblePartial (conformance, runs on every backend) gains
an ee-4 epic whose only child closes with reason "duplicate of ee-1",
asserting {Total:1 Closed:1 Eligible:false} — the dcr-tf2 regression from
#5026 end to end. Its doc comment now states the invariant this PR
actually enforces (Total == completing-closed), not the one it broke.
- cmd/bd/info.go and cmd/bd/doctor/maintenance.go no longer advertise the
retired "complete-but-unclosed" framing.
Generated CLI docs (docs/CLI_REFERENCE.md, docs/cli-reference/) are left
untouched: docs/cli-docs.pin freezes them to the released v1.1.0 tag, so
regenerating with the pinned build (matching CI's check-doc-flags job) is
a no-op regardless of source changes on this branch, and overriding the
pin pulls in ~100 files of unrelated accumulated drift. Verified via
scripts/check-doc-flags.sh against a CI-equivalent CGO_ENABLED=0 build.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015AfaSMkMRF5BTzuPNFnqHY
* fix(epic): match hyphenated wont-fix and curly-apostrophe won't fix (GH#5138)
Maintainer review on GH#5138 found the close-reason regexp missed two
forms of the already-handled wontfix keyword: a hyphen between "wont"
and "fix" (the ` ?` quantifier only tolerates a space, not a hyphen),
and "won't fix" written with the U+2019 typographic right single
quote instead of the ASCII apostrophe.
Extend the regex directly rather than normalizing the whole
close-reason string: `wont[- ]?fix` accepts a hyphen, a space, or
neither, and `won['\x{2019}]t fix` accepts either apostrophe form.
Scoping the hyphen tolerance to just this keyword pair (rather than
folding all hyphens to spaces) avoids the risk of turning unrelated
hyphenated prose into a false match.
Adds table cases for both forms plus a negative case confirming
ordinary hyphenated prose ("not-yet-planned") still doesn't match.
* style: gofmt maintenance.go after comment split the struct alignment
The GH#5026 wording comment inside the DoctorCheck literal splits gofmt's
alignment group, so Name/Status align independently of Message. CI's
"Check gofmt" caught this on the rebase; main's copy is clean, so the
violation is ours.
Whitespace only: `git diff -w` is empty.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* fix(epic): compose wont-fix separators, sync epic_closeable classifier (GH#5138 review)
bee-ghosttrack's desk review on PR #5138 raised two asks:
1. The hyphen and curly-apostrophe fixes didn't compose: "won't-fix" and
"won't-fix" (curly quote) still matched as completing. The apostrophe
alternative in nonCompletingCloseRegexp required a literal space after
"fix"; give it the same [- ]? hyphen tolerance the plain "wont[- ]?fix"
alternative already had.
2. epic_closeable (internal/workapi/detail.go) computed closeable as raw
total==closed, disagreeing with issueops.GetEpicsEligibleForClosureInTx's
real classifier — an epic whose only child closed "duplicate of X" read
epic_closeable=true in `bd show --json`. Moved IsNonCompletingClose from
issueops into the leaf internal/types package (issueops already imports
workapi, so workapi importing issueops back would cycle) and had
applyEpicProgress apply the same classifier. That also surfaced a second
bug on the way: shallowDep, which every dependent row passes through
before applyEpicProgress ever sees it, was dropping CloseReason along
with the other free-form text fields — so the classifier was reading an
always-empty string. Fixed by keeping CloseReason (short, not a hub-scale
blob) in the shallow copy.
Regression test in workapi added and verified to fail without the
shallowDep fix and pass with it (both outputs recorded in review).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* fix(epic): apply the eligibility classifier to bd show and doctor --deep (#5138 review)
Review iteration 1 (synthesis: request_changes, 1 major + 1 nit).
Major (Change Impact / Blast Radius) — two surfaces still computed epic
closeability from their own raw closed counts, so after this PR they
contradicted the eight sites that read the shared EpicStatus.EligibleForClose:
- cmd/bd/show_format.go: printEpicChildProgress gates only the
"— eligible for close" suffix on types.IsNonCompletingClose. The
closed/total figure stays raw, matching the deliberate raw ClosedChildren
convention pinned by the conformance test.
- cmd/bd/doctor/deep.go: checkEpicCompleteness routes through
issueops.GetEpicsEligibleForClosureInTx instead of its own SQL, so one
classifier remains and `bd doctor --deep` agrees with `bd doctor`'s Stale
Molecules check by construction. Side effects, both improvements: the local
LIMIT 20 is gone (the reported count is now exact), and the shared query's
isTableNotExistError tolerance replaces a LEFT JOIN that required the
optional wisps/wisp_dependencies tables unconditionally.
- cmd/bd/doctor.go: the --deep help text no longer says "all children closed".
Nit (Behavioral Correctness) — internal/types/non_completing_close.go spells
the keyword "not[- ]?planned", giving it the same per-keyword separator
tolerance the "wont fix" pair already had. The comment no longer rests the
space-only spelling on the "not-yet-planned" counterexample, which an
intervening word blocks under either spelling.
Bazel: gazelle had never been run for this PR's new files, so //internal/types
omitted non_completing_close.go and the Bazel build failed with
"internal/workapi/detail.go:275: undefined: types.IsNonCompletingClose".
`bazel run //:gazelle` adds those rows and the new cmd/bd test src.
Tests (each new pin mutation-proved: reverting the fix reds exactly the
intended case and nothing else):
- cmd/bd/show_format_test.go (new): first coverage for printEpicChildProgress;
asserts both halves — raw progress preserved, suffix gated.
- cmd/bd/doctor/deep_test.go: a duplicate-closed-child epic is not reported
ready to close and ships no `bd close` Fix line; the three pre-existing
cases pass unchanged.
- internal/types/non_completing_close_test.go: "not-planned"/"notplanned"
classify as non-completing; "not-yet-planned" still does not.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Gas City Adopt-PR <adopt-pr@gascity.local>