Intimacy Logging toggle persists but has no UI surface to set intimacy level #190

New issue

Open

opened 2026-09-21 13:03:04 +00:00 by Mark · 0 comments

Mark commented

2026-09-21 13:03:04 +00:00

Owner

Symptom

Settings -> Privacy -> Intimacy Logging is a switch (label: "Enable logging of intimacy level for romantic interactions"). Toggling it ON writes intimacyLoggingEnabled=true to Capacitor Preferences and persists across navigation -- verified via storage shim during the 2026-09-20 privacy vault shakedown.

However, there is no UI surface to actually set an intimacy level for any interaction. Toggling the switch enables a code path that no form, drawer, or post-save flow exposes.

Repro

Settings -> Privacy -> Intimacy Logging -> toggle ON.
Navigate to #/log (Log Interaction).
Save an interaction for any romantic contact.
Observe: no field, dropdown, or "intimacy level" control appears in the form, post-save drawer, or person detail.

What's missing

The store has setIntimacyLoggingEnabled (src/lib/store.ts:1257) and the field is read somewhere -- but no LogInteraction.tsx input, no PersonDetail.tsx drawer, and no interaction-edit affordance surfaces the intimacy field when this is enabled. Either:

The form/input was never built (feature shipped half-implemented), or
A conditional render hides the input behind a flag that doesn't fire.

Source pointer

Settings toggle: src/pages/Settings.tsx:1025-1036
Store action: src/lib/store.ts:1257
Likely targets to inspect: src/pages/LogInteraction.tsx, src/pages/PersonDetail.tsx, any intimate-state-engine.ts consumer

Severity

Data-shape gap. User enables a feature believing data will be captured; data is not captured. Settings UI is misleading.

Suggested verification

Search the codebase for consumers of intimacyLoggingEnabled and intimacyLevel. If no consumer renders an input when the flag is true, the feature is half-built. File either:

a UI issue (add the missing input/drawer), or
a product issue (remove the toggle until the UI ships).

## Symptom `Settings -> Privacy -> Intimacy Logging` is a switch (label: "Enable logging of intimacy level for romantic interactions"). Toggling it ON writes `intimacyLoggingEnabled=true` to Capacitor Preferences and persists across navigation -- verified via storage shim during the 2026-09-20 privacy vault shakedown. However, **there is no UI surface to actually set an intimacy level for any interaction**. Toggling the switch enables a code path that no form, drawer, or post-save flow exposes. ## Repro 1. `Settings -> Privacy -> Intimacy Logging` -> toggle ON. 2. Navigate to `#/log` (Log Interaction). 3. Save an interaction for any romantic contact. 4. Observe: no field, dropdown, or "intimacy level" control appears in the form, post-save drawer, or person detail. ## What's missing The store has `setIntimacyLoggingEnabled` (`src/lib/store.ts:1257`) and the field is read somewhere -- but no `LogInteraction.tsx` input, no `PersonDetail.tsx` drawer, and no interaction-edit affordance surfaces the intimacy field when this is enabled. Either: - The form/input was never built (feature shipped half-implemented), or - A conditional render hides the input behind a flag that doesn't fire. ## Source pointer - Settings toggle: `src/pages/Settings.tsx:1025-1036` - Store action: `src/lib/store.ts:1257` - Likely targets to inspect: `src/pages/LogInteraction.tsx`, `src/pages/PersonDetail.tsx`, any `intimate-state-engine.ts` consumer ## Severity Data-shape gap. User enables a feature believing data will be captured; data is not captured. Settings UI is misleading. ## Suggested verification Search the codebase for consumers of `intimacyLoggingEnabled` and `intimacyLevel`. If no consumer renders an input when the flag is true, the feature is half-built. File either: - a UI issue (add the missing input/drawer), or - a product issue (remove the toggle until the UI ships).