Add date-scoped FRICHMOND checklist with pending-only carry-over; remove Profile Plans/Pendings

[Copilot]

This PR adds a structured checklist to daily FRICHMOND entries and aligns carry-over behavior with longitudinal task tracking: completed tasks stay on the original date, while only pending items move forward. It also removes the replaced Plans and Pendings fields from the Profile tab.

• FRICHMOND checklist (daily entry model + UI)

  • Added DailyChecklistItem and DailyUpdate.checklist.
  • Added checklist editor under Plan in FRICHMOND:
    • freeform item add
    • pending/completed toggle
    • remove item
  • Completed items render crossed out in-date to preserve historical state.

• Carry-over semantics

  • Copy latest entry now carries FRICHMOND text fields plus pending checklist items only.
  • When opening a date with no saved FRICHMOND entry, checklist initializes from pending items of the latest prior saved entry.

• Profile tab replacement

  • Removed Profile-tab Plans and Pendings textboxes, per new checklist ownership in FRICHMOND.

• Reporting and in-app guidance alignment

  • FRICHMOND summary export now includes checklist lines:
    • Checklist pending: ...
    • Checklist completed: ...
  • Updated in-app How to use and README tab descriptions to reflect:
    • Profile no longer owns Plans/Pendings
    • FRICHMOND now includes checklist behavior.

• Version

  • Bumped app version to 1.3.9 for this user-visible workflow change.

// src/types.ts
export interface DailyChecklistItem {
  text: string
  completed: boolean
}

export interface DailyUpdate {
  // ...
  plans: string
  checklist: DailyChecklistItem[]
  lastUpdated: string
}

• https://github.com/user-attachments/assets/f3c2fee8-0b40-4c03-8666-c9a99e6d1854
• https://github.com/user-attachments/assets/cb290583-fcb2-47f1-bb0c-377346fba572

Original prompt

Implement issue "Checklist feature - FRICHMOND tab" in repo

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[CSfromCS]

@copilot handle merge conflicts

[Copilot]

@copilot handle merge conflicts

I checked commit 9a5196d and there are no local conflict markers in this branch. I can’t resolve GitHub-side merge conflicts directly from here because I don’t have permission to pull/rebase against the base branch. Please update/rebase the branch from GitHub, then I can handle any follow-up code fixes if conflicts surface.