Fleet changelogs · dev.ecs0.net
rdmbair15m5-changelog-20260922-0100-ticket-lifecycle-app-docs-and-hook-worktree-resolution

rdmbair15m5-changelog-20260922-0100-ticket-lifecycle-app-docs-and-hook-worktree-resolution

Resolved ISSUE-20260906-15 (ticket CLI lifecycle metadata clearing & folder movement), ISSUE-20260905-09 (Docs/ case normalization across 10 app repos), and ISSUE-20260831-23 (project_state_hook.py v1.4 worktree awareness and fleet deployment).

Scope


1. Ticket Store Lifecycle Resolution (ISSUE-20260906-15)

Problem

In ~/dev/issues/bin/ticket line 3687, cmd_status set meta['resolved_at'] when transitioning to resolved or closed, but failed to clear resolved_at or verifier when reopening tickets back to open, in-progress, blocked, or needs-decision. This created contradictory metadata states where active in-progress tickets retained historic resolution timestamps and verifier tags. Furthermore, reopened ticket markdown files remained stranded in resolved/ rather than moving back to open/.

Remediation


2. App Repositories Docs Case Normalization (ISSUE-20260905-09)

Problem

Ten app repositories tracked documentation under a capitalized Docs/ directory while generator scripts (scripts/generate_project_prds.py and scripts/extract_project_metadata.py) wrote to lowercase docs/project_prd.html. On APFS case-insensitive filesystems this was invisible to git status, but broke case-sensitive environments (Docker containers, Linux CI, and git ls-files --error-unmatch).

Remediation


3. SessionStart Hook Worktree Awareness (ISSUE-20260831-23)

Problem

The SessionStart advisory hook (fleet/ops/project-state/project_state_hook.py) printed stale session ages when work occurred on a branch worktree (e.g. reporting SESSION-STATE.md written 46h ago from the primary checkout when active branch work had published a fresh state file 5h ago). Successor agents were misled into distrusting current records or repeating completed work.

Remediation


4. Verification Evidence & Artifacts


5. Rollback / Undo