[Findit] #144 fix never landed — fixit card t_87675fee completed prematurely without fix #153
Labels
No labels
blocked:depends-p1
blocked:gate-research
blocked:lint-failed
blocked:needs-decision
blocked:needs-human
blocked:verify-failed
bug
data-loss
documentation
enhancement
feature-request
in-progress
needs-decompose
needs-triage
pwa
quickfix
security
security/high
security/medium
test
test-coverage
triage-approved
vault
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Mark/kimi_agent_kin_app_sync#153
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The post-deploy probe for issue #144 found that the fix never landed. The fixit card t_87675fee was marked as completed but no code was ever committed and the issue remains open.
Background
Issue #144 reports that the "Add Your First Person" button on the People page's empty state does not open the AddPersonDrawer (2 swallowed JS exceptions).
Fixit card t_87675fee was created to fix this bug. It completed with outcome
completed.What actually happened
The fixit card's runner (kilo-gsd dispatched via kilo-gsd-monitor.sh) crashed during Phase 1 (Research) with a
KeyboardInterrupt— the innertmux_kill()call sent Ctrl-C to itself:No fix was written, no commit was made, no branch was created. The fixit card was marked done prematurely after launching the async monitor — the outer dispatch exited before the monitor produced any result.
Issue #144 persists
closed_at: None)bug,triage-approvedWhat needs to happen
Issue #144 still requires a real fix. The "Add Your First Person" button on the People page's empty state does not open the AddPersonDrawer. See issue #144 body for full reproduction steps and technical notes.
References
Update: Issue #144 was closed by Mark on 2026-07-24 with the note 'Fixed by React duplicate resolution (optimizeDeps.exclude + watch.ignored).' The
resolve.dedupeconfig is already onmain. Since the bug is closed, this findit issue is superseded.