Skip to content

STALE conflates forgotten work with deliberate removal #5

@kborovik

Description

@kborovik

Live case: T1 closed x ("add CI"), then commit 97cef80 deliberately removed the workflow. CHECK tasks flags STALE — same verdict as work that silently vanished. The remedy hint ("uncheck status") is wrong here: the task was done, then intentionally retired; unchecking would re-queue work nobody wants.

Compact's prong 2 has a SUPERSEDED body-replace for closed §T whose §V cite died, but nothing covers artifact-removed-on-purpose. Options: extend SUPERSEDED to operator-confirmed deliberate removals; or a check-side gate (AskUserQuestion: forgotten vs retired) routing to amend-body instead of uncheck. Either way the verdict-to-remedy map needs the second path.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions