Mark/kimi_agent_kin_app_sync

Fork 0

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

New issue

Closed

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

Mark commented

2026-05-30 14:14:38 +00:00

Owner

Goal

Add romantic, partner, and spouse to the RelationshipType enum and add an optional romanceFields object to Person.

Data Model Changes

// types.ts - RelationshipType union
export type RelationshipType =
  | "Family"
  | "Friend"
  | "Colleague"
  | "Mentor"
  | "Acquaintance"
  | "Romantic"
  | "Partner"
  | "Spouse"
  | "Other";

// New optional field on Person
export interface RomanceFields {
  anniversary?: string;       // ISO date string
  milestones: RomanceMilestone[];
  loveLanguageObserved?: string; // inferred from data, not self-reported
}

export interface RomanceMilestone {
  type: string;   // "first_date", "first_trip", "moving_in", "engagement", "wedding", "custom"
  date: string;   // ISO date string
  label: string;  // user-visible label
}

Scope

Update types.ts with new RelationshipType values
Update schemas.ts zod schemas to match
Add romanceFields?: RomanceFields to Person type + schema
Add RomanceFields and RomanceMilestone interfaces
Add migration to Dexie db for the new fields (default to undefined)
Update any UI dropdowns that render RelationshipType to show the new values

Acceptance Criteria

Person.relationshipType accepts "Romantic", "Partner", "Spouse"
Person.romanceFields is optional, defaults to undefined
Zod import/export schemas validate the new fields
Dexie migration runs cleanly (existing data untouched)
Relationship type picker in UI shows new options
Typecheck passes

Dependencies

None — this is the data model foundation that other romantic features build on.

Decomposed from #46

## Goal Add `romantic`, `partner`, and `spouse` to the `RelationshipType` enum and add an optional `romanceFields` object to `Person`. ## Data Model Changes ```typescript // types.ts - RelationshipType union export type RelationshipType = | "Family" | "Friend" | "Colleague" | "Mentor" | "Acquaintance" | "Romantic" | "Partner" | "Spouse" | "Other"; // New optional field on Person export interface RomanceFields { anniversary?: string; // ISO date string milestones: RomanceMilestone[]; loveLanguageObserved?: string; // inferred from data, not self-reported } export interface RomanceMilestone { type: string; // "first_date", "first_trip", "moving_in", "engagement", "wedding", "custom" date: string; // ISO date string label: string; // user-visible label } ``` ## Scope - Update `types.ts` with new `RelationshipType` values - Update `schemas.ts` zod schemas to match - Add `romanceFields?: RomanceFields` to `Person` type + schema - Add `RomanceFields` and `RomanceMilestone` interfaces - Add migration to Dexie db for the new fields (default to undefined) - Update any UI dropdowns that render `RelationshipType` to show the new values ## Acceptance Criteria - [ ] `Person.relationshipType` accepts "Romantic", "Partner", "Spouse" - [ ] `Person.romanceFields` is optional, defaults to undefined - [ ] Zod import/export schemas validate the new fields - [ ] Dexie migration runs cleanly (existing data untouched) - [ ] Relationship type picker in UI shows new options - [ ] Typecheck passes ## Dependencies None — this is the data model foundation that other romantic features build on. --- _Decomposed from #46_

Mark referenced this issue

2026-05-30 14:14:58 +00:00

Feature: Date night planning & logging with quality ratings (#46 slice 2) #48

Mark referenced this issue

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

Feature: Relationship milestones + countdowns for romantic partners (#46 slice 3) #49

Mark referenced this issue

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

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

Mark referenced this issue

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

Feature: Intimacy logging (opt-in, off by default) (#46 slice 5) #51

Mark referenced this issue

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

Feature: Romantic mood/energy tags + pattern detection (#46 slice 6) #52

Mark referenced this issue

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

Feature: Date night suggestions from cadence data (#46 slice 7) #53

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 commented

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

Author

Owner

✅ Completed. Changes made:

Added Romantic, Partner, Spouse to RelationshipType enum
Added RomanceFields and RomanceMilestone interfaces
Added romanceFields optional field to Person type/schema
Added romantic-related interaction fields (isDateNight, qualityRating, plannedBy, isConflict, repairAttempt, conflictResolved, intimacyLevel) for issues #48, #50, #51
Updated UI dropdowns in AddPersonDrawer.tsx, People.tsx, PersonDetail.tsx
Added CSS badge styles for romantic types
Added Dexie DB migration (v4)
All typechecks and tests pass

✅ Completed. Changes made: - Added `Romantic`, `Partner`, `Spouse` to `RelationshipType` enum - Added `RomanceFields` and `RomanceMilestone` interfaces - Added `romanceFields` optional field to `Person` type/schema - Added romantic-related interaction fields (`isDateNight`, `qualityRating`, `plannedBy`, `isConflict`, `repairAttempt`, `conflictResolved`, `intimacyLevel`) for issues #48, #50, #51 - Updated UI dropdowns in `AddPersonDrawer.tsx`, `People.tsx`, `PersonDetail.tsx` - Added CSS badge styles for romantic types - Added Dexie DB migration (v4) - All typechecks and tests pass

Mark closed this issue

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

Mark referenced this issue

2026-05-30 16:24:51 +00:00

Feature: Date night planning & logging with quality ratings (#46 slice 2) #48

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#47

No description provided.

Rows
Columns