Define the SchedPlus v1.0 visual launch roadmap

[ZFordDev]

Purpose

SchedPlus has completed the v0.9 offline task-management roadmap, and the issue tracker currently has no open work or v1.0 milestone. The README promises an offline-first 1.0 visual launch, with accounts, synchronization, web, mobile, and online backup remaining optional future additions.

This parent issue should define what 1.0 means before implementation issues are created.

Proposed v1.0 boundaries

• Preserve full offline use with no account requirement.
• Treat optional accounts, synchronization, online backup, web, and mobile clients as post-1.0 work unless explicitly brought into scope.
• Focus 1.0 on a dependable desktop product and a coherent visual launch.
• Keep Standard, Lite, Full, and CLI editions compatible with the existing shared database and task model.

Decisions required

• Define the visual and interaction quality bar for the Standard PyQt interface.
• Decide whether Lite receives visual parity work or stability-only support for 1.0.
• Define the supported operating-system and package acceptance matrix.
• Define accessibility and keyboard-navigation acceptance checks.
• Define first-run, empty-state, populated-state, and recovery-state acceptance checks.
• Define required screenshots, Store listing assets, website material, and release documentation.
• Define performance and reliability expectations for startup, task lists, reminders, backup, restore, and upgrades.
• Confirm which features are explicitly deferred until after 1.0.

Deliverables

• Approved v1.0 scope and non-goals.
• Concrete child issues with independent acceptance criteria.
• A release-order/dependency checklist.
• README and DocsHub roadmap wording updated to link to the approved plan.

Current evidence

The v0.8 and v0.9 parent issues used this same parent-first structure successfully. Creating feature issues before these decisions would invent requirements that are not present in the current roadmap.

[ZFordDev]

Initial child issues from roadmap consultation

The first product direction review established PyQt as the flagship interface. Lite remains intentionally basic, while CLI expands only where scripting provides clear value.

• Make the PyQt calendar Today action obvious and verified #191 Make the existing calendar Today action obvious and verified
• Design and add a Kanban planning view to the PyQt workspace #192 Design and add a Kanban planning view to the PyQt workspace
• Import standard iCalendar event files into SchedPlus #193 Import standard iCalendar event files into SchedPlus
• Evaluate optional live Google Calendar synchronization #194 Evaluate optional live Google Calendar synchronization
• Design optional local profiles as a future account foundation #195 Design optional local profiles as a future account foundation
• Add PyQt theme presets and documented custom theme files #196 Add PyQt theme presets and documented custom theme files

Key boundaries:

• Offline iCalendar import is separate from live provider sync.
• Google synchronization remains a feasibility decision, not a committed dependency.
• Local profiles do not claim to provide authentication or security.
• Accounts and online services remain optional.
• The advanced planning and theme work targets PyQt; Lite stays intentionally basic.