1.0.0

TaskNotes Views 1.0.0

Added

• Added Linear-inspired project progress widgets to TaskNotes project notes in Live Preview and Reading view.
• Added TaskNotes project detection using its relationship index, with configured project tag and property markers as fallbacks.
• Added project-task discovery through TaskNotes' public query API for tasks whose projects property links to the current project.
• Added Apache ECharts line charts for total scope, ideal target progress, scheduled work, started work, and completed work.
• Added cumulative project summary metrics for scope, scheduled, started, and completed work, including percentages and compact duration or unitless formatting.
• Added hover details for scheduled, started, and completed events, including task names prefixed with their individual scope values.
• Added configurable project start and end frontmatter properties, defaulting to scheduled and due.
• Added optional date-range derivation from the earliest task scheduled or started date and the latest task due date.
• Added configurable task scope, started, and scheduled properties so projects can use time estimates, story points, or other numeric scope values.
• Added configurable in-progress statuses while automatically respecting statuses TaskNotes categorizes as completed or skipped.
• Added duration-aware formatting for estimates in minutes and hours, plus unitless formatting for values such as story points.
• Added a weekend setting that controls whether ideal target progress advances on Saturdays and Sundays.
• Added recurring-task projections that treat each recurrence as a logical work item within the reporting window.
• Added overlays for materialized recurring occurrences so their actual project assignment, estimate, status, schedule, start, and completion state override virtual projections without double-counting.
• Added support for recurring complete_instances and skipped_instances, including template estimates for non-materialized completed occurrences.
• Added optional project-capacity estimation from six weeks of vault-wide completed work, using recency-weighted weekly velocity scaled to the project duration.
• Added an insufficient-history safeguard requiring at least three completed scoped work items spanning three weeks before showing estimated capacity.
• Added a localized, muted notice when historical data is insufficient to estimate capacity.
• Added searchable declarative Obsidian settings through getSettingDefinitions(), with a legacy display() implementation for compatibility.
• Added a TaskNotes-style localization system for settings, progress metrics, chart labels, errors, dates, and units.
• Added localized validation and load errors that identify the configured project start and end frontmatter properties.
• Added development scripts for type checking, testing, linting, production builds, and copying plugin artifacts into test vaults.
• Added automated release-note promotion, release indexing, release metadata validation, artifact attestation, and draft GitHub release creation.
• Added comprehensive README documentation and a project progress screenshot.

Changed

• Changed the initial fake chart into a data-driven progress view backed by TaskNotes tasks and project frontmatter.
• Changed progress visualization to Linear's upward cumulative style: the target rises toward total scope while scheduled, started, and completed work accumulate in the same direction.
• Changed the target line to remain flat on weekends by default and made weekend progress optional.
• Changed project date resolution so explicit project frontmatter dates take precedence independently, with task-derived dates used only for missing or invalid boundaries.
• Changed started work to use the configured started property and fall back only to completion date; scheduled and started dates are treated as independent events.
• Changed actual started and completed series to terminate at the current date instead of projecting flat values into the future.
• Changed the chart to draw a thin vertical marker at the current date.
• Changed the completed area fill to blue so it remains visually distinct from the yellow started area.
• Changed chart and metric colors so Scope, Target, Scheduled, Started, and Completed remain distinguishable in lines, summaries, and hover markers.
• Changed hover details to omit Scope and Target because they do not represent task events on a particular date.
• Changed the Scope summary to display Scope / Capacity with a utilization percentage only when a velocity estimate is available.
• Changed insufficient-capacity rendering to retain the normal Scope metric and place the explanation beneath the widget title.
• Changed numeric display values to use at most one decimal place.
• Changed the project widget title to append Progress to the project name.
• Changed the project license from 0BSD to MIT so redistributed copies or substantial portions must retain the copyright and permission notice.

Fixed

• Fixed project task loading failures caused by calling TaskNotes' subtask relationship API on project notes that are not themselves tasks.
• Fixed the settings page failing to open by providing the required legacy display() method alongside declarative settings.
• Fixed ISO datetime values not being normalized correctly for started and completion dates.
• Fixed started progress appearing on a task's scheduled date instead of its configured startedAt date.
• Fixed completed TaskNotes statuses not contributing to started work when no explicit in-progress status matched.
• Fixed recurring parents and their materialized occurrences being counted twice.
• Fixed materialized recurring occurrences moved to another project remaining in the original project's progress totals.
• Fixed skipped recurring occurrences contributing to scope, started, or completed totals.
• Fixed Scope and Target hover markers using colors that did not match their chart lines.
• Fixed actual progress lines extending beyond today and obscuring the distinction between measured and projected progress.