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
docs/features/active/2026-08-26-issue-468-residual-reflective-caller-risk-635/spec.md AC-9 states there are six variable-argument reflection call sites targeting the removed members' own type, but the actual derivation performed while implementing issue #635 found eight such sites. The approved acceptance-criterion text is numerically wrong.
Data source or fixture: docs/features/active/2026-08-26-issue-468-residual-reflective-caller-risk-635/spec.md line 352, and the item-635 orchestrator delegation report from /parallel-run bugs-635-440
Steps to Reproduce
Read AC-9 at docs/features/active/2026-08-26-issue-468-residual-reflective-caller-risk-635/spec.md:352-354: "Each of the six variable-argument reflection call sites that target the removed members' own type is named individually by file and line...".
Compare against the item-635 implementation's own derivation, which enumerated eight variable-argument sites (including GetField( calls taking a string name against typeof(QfcCollectionController)), not six.
The approved spec's AC-9 should state the correct count (eight) so the acceptance criterion matches what was actually required and verified.
Actual Behavior
AC-9 still reads "six" in the merged spec on main, while the actual evidence and the merged fix cover eight sites. The criterion text is stale relative to the verified requirement.
Logs / Screenshots
Attached minimal logs or screenshot
Snippet: parallel-run bugs-635-440 final report: "Item 635's spec.md AC-9 names six variable-argument reflection call sites; derivation yields eight. Discharged by superset, but the approved figure is stale - amending approved criterion text is yours."
Summary
docs/features/active/2026-08-26-issue-468-residual-reflective-caller-risk-635/spec.mdAC-9 states there are six variable-argument reflection call sites targeting the removed members' own type, but the actual derivation performed while implementing issue #635 found eight such sites. The approved acceptance-criterion text is numerically wrong.Environment
TaskMasterdocs/features/active/2026-08-26-issue-468-residual-reflective-caller-risk-635/spec.mdline 352, and the item-635 orchestrator delegation report from/parallel-run bugs-635-440Steps to Reproduce
docs/features/active/2026-08-26-issue-468-residual-reflective-caller-risk-635/spec.md:352-354: "Each of the six variable-argument reflection call sites that target the removed members' own type is named individually by file and line...".GetField(calls taking astring nameagainsttypeof(QfcCollectionController)), not six.Expected Behavior
The approved spec's AC-9 should state the correct count (eight) so the acceptance criterion matches what was actually required and verified.
Actual Behavior
AC-9 still reads "six" in the merged spec on
main, while the actual evidence and the merged fix cover eight sites. The criterion text is stale relative to the verified requirement.Logs / Screenshots
Impact / Severity
Source
From: docs/features/potential/2026-08-29-issue-635-spec-ac9-variable-argument-count-stale.md