Mark/kimi_agent_kin_app_sync

Fork 0

Feature: Conflict & repair tracking for romantic partners (#46 slice 4) #50

New issue

Closed

opened 2026-05-30 14:15:23 +00:00 by Mark · 1 comment

Mark commented

2026-05-30 14:15:23 +00:00

Owner

Goal

Add optional conflict/repair tracking on interactions — log tough conversations, track repair attempts, and detect reconnection patterns.

Data Model Changes

interface Interaction {
  // existing fields...
  isConflict?: boolean;       // tag for hard conversations
  repairAttempt?: boolean;    // logged as a follow-up to a conflict
  conflictResolved?: boolean; // marked when the conflict was resolved
}

Scope

Add isConflict, repairAttempt, conflictResolved to Interaction type + schema
Dexie migration for new fields
Log interaction form: optional "Difficult conversation" toggle
After logging a conflict, prompt to log a repair attempt later
Person detail: conflict/repair timeline showing pattern
Simple pattern detection: average days to repair after conflict
No scores or judgments — just surfacing the data

Acceptance Criteria

Interaction model supports conflict/repair fields
Conflict toggle on log interaction form
Repair attempt logging prompted after conflicts
Person detail shows conflict/repair timeline
Average repair time computed from data
Typecheck passes

Dependencies

Requires #47 (romantic relationship type + romanceFields)

Decomposed from #46

## Goal Add optional conflict/repair tracking on interactions — log tough conversations, track repair attempts, and detect reconnection patterns. ## Data Model Changes ```typescript interface Interaction { // existing fields... isConflict?: boolean; // tag for hard conversations repairAttempt?: boolean; // logged as a follow-up to a conflict conflictResolved?: boolean; // marked when the conflict was resolved } ``` ## Scope - Add `isConflict`, `repairAttempt`, `conflictResolved` to Interaction type + schema - Dexie migration for new fields - Log interaction form: optional "Difficult conversation" toggle - After logging a conflict, prompt to log a repair attempt later - Person detail: conflict/repair timeline showing pattern - Simple pattern detection: average days to repair after conflict - No scores or judgments — just surfacing the data ## Acceptance Criteria - [ ] Interaction model supports conflict/repair fields - [ ] Conflict toggle on log interaction form - [ ] Repair attempt logging prompted after conflicts - [ ] Person detail shows conflict/repair timeline - [ ] Average repair time computed from data - [ ] Typecheck passes ## Dependencies - Requires #47 (romantic relationship type + romanceFields) --- _Decomposed from #46_

Mark referenced this issue

2026-05-30 14:16:07 +00:00

Feature: Romantic relationship tracking — intimacy logging, date night planning, black book integration #46

Mark referenced this issue

2026-05-30 16:08:48 +00:00

Feature: Romantic relationship type + romanceFields data model (#46 slice 1) #47

Mark closed this issue

2026-05-30 20:50:02 +00:00

Mark commented

2026-05-30 20:50:04 +00:00

Author

Owner

Implemented in commit. Added isConflict, repairAttempt, conflictResolved fields to Interaction type, conflict toggle in log form, and conflict/repair timeline with average repair time calculation.

Mark referenced this issue from a commit

2026-06-08 01:11:50 +00:00

feat: add conflict & repair tracking for romantic partners (closes #50)

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Mark/kimi_agent_kin_app_sync#50

No description provided.

Rows
Columns