chore(conductor): Archive track 'Fix recurring meetings visibility'

conductor/tracks/fix_recurring_visibility_20260219/index.md

@@ -1,5 +0,0 @@
-# Track fix_recurring_visibility_20260219 Context
-
-- [Specification](./spec.md)
-- [Implementation Plan](./plan.md)
-- [Metadata](./metadata.json)

conductor/tracks/fix_recurring_visibility_20260219/metadata.json

@@ -1,8 +0,0 @@
-{
-  "track_id": "fix_recurring_visibility_20260219",
-  "type": "bug",
-  "status": "new",
-  "created_at": "2026-02-19T00:00:00Z",
-  "updated_at": "2026-02-19T00:00:00Z",
-  "description": "Fix issue where recurring meetings are not showing up."
-}

conductor/tracks/fix_recurring_visibility_20260219/plan.md

@@ -1,24 +0,0 @@
-# Implementation Plan - Fix Recurring Meetings Visibility
-
-## Phase 1: Investigation & Reproduction [checkpoint: 8137d63]
-- [x] Task: Create validation test case 6122599
-    - [x] Add a test in `icalendar_test.ts` with a valid weekly recurring event starting in the past.
-    - [x] Assert that it returns multiple occurrences within the 30-day window.
-    - [x] Run the test to see if it fails (confirming the bug).
-- [x] Task: Investigate Object RRULE 6122599
-    - [x] The logs show `Invalid rrule type (object)`. This means `ts-ics` is parsing RRULE into an object, not a string.
-    - [x] Create a test case where `rrule` is an object (mocking `ts-ics` output).
-    - [x] Verify that it returns only 1 event (the bug).
-- [x] Task: Conductor - User Manual Verification 'Investigation & Reproduction' (Protocol in workflow.md)
-
-## Phase 2: Fix Logic [checkpoint: a4acfa1]
-- [x] Task: Support Object RRULE in `expandRecurrences` f7f6028
-    - [x] Modify `expandRecurrences` to handle `rrule` as an object.
-    - [x] It likely needs to be converted back to a string or used directly if `rrule` library supports it.
-    - [x] Run the new test case to confirm the fix.
-- [x] Task: Conductor - User Manual Verification 'Fix Logic' (Protocol in workflow.md)
-
-## Phase 3: Cleanup & Verification [checkpoint: 9d07e7a]
-- [x] Task: Full Regression Check f1bafb6
-    - [x] Run all tests in `icalendar_test.ts`.
-- [x] Task: Conductor - User Manual Verification 'Cleanup & Verification' (Protocol in workflow.md)

conductor/tracks/fix_recurring_visibility_20260219/spec.md

@@ -1,18 +0,0 @@
-# Specification: Fix Recurring Meetings Visibility
-
-## Overview
-Users report that all recurring meetings are missing from calendar views without any error messages. This suggests an issue with the expansion or indexing logic for recurring events, possibly introduced by recent changes.
-
-## Functional Requirements
-- **Visibility:** Recurring events must appear in the calendar views.
-- **Expansion:** The `expandRecurrences` function must correctly expand valid RRULE strings into occurrences within the specified window.
-
-## Implementation Steps
-1.  **Investigation:** Create a test case with a *valid* recurring event (unlike the previous invalid one) and verify if `expandRecurrences` produces the expected occurrences.
-2.  **Debugging:** Inspect the `filter` logic in `expandRecurrences` (specifically the `filterStart` and `windowEnd` logic).
-3.  **Fix:** Adjust the logic to ensure valid occurrences are returned.
-4.  **Verify:** Confirm the fix with the new test case.
-
-## Acceptance Criteria
-- [ ] A new test case with a valid recurring event passes and returns the expected number of occurrences.
-- [ ] Recurring events are visible in the calendar view (manual verification).