# NousResearch/hermes-agent · Kanban cards with unresolvable phantom session IDs

## Open now

- Nothing open on GitHub.

A bug where kanban cards can be stamped with a session ID that does not exist in any state.db, along with related fix attempts targeting this phantom provenance issue.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #114785. Verify it addresses your case.
- **Recommended:** read PR #114785 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-114785`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #114092: \[Bug\] Kanban cards can be stamped with a session id that exists in no state.db (phantom provenance)

## Prior & competing PRs

- **#114785: fix(kanban): cards no longer carry a session id that no state.db resolves (#114092, salvage #114098)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/kanban_db.py`, `tests/tools/test_kanban_provenance.py`, `tools/kanban_tools.py`, `website/docs/user-guide/features/kanban.md`
- **#114098: fix(kanban): reject phantom session provenance**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `c619a145f111`, `#114785`, `#114092`, `#114098`

## Fix status

- Merged to main in PR #114785 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-18`.
