Build Toggl Track

The build, in order

1. 1

   Local foundation and data contract

   hideshow

   Create the runnable local foundation for a private manual time tracker with editable history and clear reports, including the real schema and acceptance fixture.

   1. 1.1Create and start the local application

      Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch.

      Files app.pyrequirements.txt.env.example.gitignore

      terminalcopy

      python -m venv .venv
      python -m pip install Flask Flask-WTF python-dotenv waitress tzdata
      python -m pip freeze > requirements.txt
      python -m flask --app app run --host 127.0.0.1

   2. 1.2Implement storage and seed the named fixture

      For database-backed state create schema.sql and db.py using this model: projects(id,name,client); tags(id,name); entries(id,project_id,description,start_utc,end_utc,revision); entry_tags(entry_id,tag_id); edits(id,entry_id,before_json,after_json,reason,at). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: Two one-hour entries on separate projects and one running timer crossing local midnight. Re-running init must not erase data.

      Files schema.sqldb.pymanage.pyfixtures/README.md

      terminalcopy

      python manage.py init
      python manage.py seed

   3. 1.3Protect the local request boundary

      Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now.

      Files app.pytemplates/base.htmltest/test_foundation.py

   done when · tick each as it passes

   • The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000.
   • Restarting preserves the seeded records or canonical files; running init again deletes nothing.
   • A cross-origin state-changing request to an admin route is refused.

   watch out

   • The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation.

   next phase
2. 2

   One running timer

   hideshow

   One running timer for Toggl Track: Implement start/stop and a database constraint or transaction guard allowing at most one open entry.

   1. 2.1Implement start/stop and a database constraint or transaction guard allowing at most one open entry.

      Implement start/stop and a database constraint or transaction guard allowing at most one open entry.

      Files features/one_running_timer.pytemplates/one_running_timer.html

   2. 2.2Persist start instants in UTC and calculate elapsed display from the clock; provide a manual-entry form.

      Persist start instants in UTC and calculate elapsed display from the clock; provide a manual-entry form.

      Files features/one_running_timer.py

   3. 2.3Exercise the acceptance fixture

      Use Two one-hour entries on separate projects and one running timer crossing local midnight. Check: Two simultaneous Start requests leave one running entry. Then check: Reloading the page preserves the elapsed timer. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser.

      Files test/test_one_running_timer.py

      terminalcopy

      python -m unittest discover -s test

   done when · tick each as it passes

   • Two simultaneous Start requests leave one running entry.
   • Reloading the page preserves the elapsed timer.

   watch out

   • The browser tick is a display refresh, not a trustworthy duration counter.

   next phase
3. 3

   Corrections and boundaries

   hideshow

   Corrections and boundaries for Toggl Track: Allow edits with a reason and before/after history; reject negative durations and flag overlaps for explicit review.

   1. 3.1Allow edits with a reason and before/after history; reject negative durations and flag overlaps for explicit review.

      Allow edits with a reason and before/after history; reject negative durations and flag overlaps for explicit review.

      Files features/corrections_and_boundaries.pytemplates/corrections_and_boundaries.html

   2. 3.2Split report allocations at local day boundaries using a selected IANA timezone while preserving the original UTC entry.

      Split report allocations at local day boundaries using a selected IANA timezone while preserving the original UTC entry.

      Files features/corrections_and_boundaries.py

   3. 3.3Exercise the acceptance fixture

      Use Two one-hour entries on separate projects and one running timer crossing local midnight. Check: The midnight-spanning entry contributes the correct seconds to each local day. Then check: Editing end before start fails without changing history. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser.

      Files test/test_corrections_and_boundaries.py

      terminalcopy

      python -m unittest discover -s test

   done when · tick each as it passes

   • The midnight-spanning entry contributes the correct seconds to each local day.
   • Editing end before start fails without changing history.

   watch out

   • Do not silently delete overlap time; users may intentionally record parallel work.

   next phase
4. 4

   Project reports

   hideshow

   Project reports for Toggl Track: Sum integer seconds by project, client and tag with clear date/timezone filters; avoid double-counting in the overall total.

   1. 4.1Sum integer seconds by project, client and tag with clear date/timezone filters; avoid double-counting in the overall total.

      Sum integer seconds by project, client and tag with clear date/timezone filters; avoid double-counting in the overall total.

      Files features/project_reports.pytemplates/project_reports.html

   2. 4.2Export CSV of raw entries plus JSON edit history and document that rounding occurs only in display.

      Export CSV of raw entries plus JSON edit history and document that rounding occurs only in display.

      Files features/project_reports.py

   3. 4.3Exercise the acceptance fixture

      Use Two one-hour entries on separate projects and one running timer crossing local midnight. Check: Two one-hour entries total exactly 7200 seconds. Then check: An entry with two tags is counted once in the all-project total. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser.

      Files test/test_project_reports.py

      terminalcopy

      python -m unittest discover -s test

   done when · tick each as it passes

   • Two one-hour entries total exactly 7200 seconds.
   • An entry with two tags is counted once in the all-project total.

   watch out

   • Leave employee surveillance, payroll calculations and automatic invoicing out of this manual tracker.

   next phase
5. 5

   Portable delivery and clean-start proof

   hideshow

   Finish the Toggl Track replacement with a documented first-run path and a recoverable export.

   1. 5.1Write the user-facing runbook

      Document prerequisites, every configuration variable, data locations and the three domain workflows: One running timer; Corrections and boundaries; Project reports. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them.

      Files README.md.env.example

   2. 5.2Create and rehearse a recoverable backup

      Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for toggl-track. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Two one-hour entries on separate projects and one running timer crossing local midnight. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy.

      Files OPERATIONS.mdscripts/backup.py

   3. 5.3Reproduce the first-run experience

      Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete.

      Files README.mdverification.md

      terminalcopy

      python -m pip install -r requirements.txt
      python -m unittest discover -s test

   done when · tick each as it passes

   • A new folder reaches the documented fixture outcome using only README instructions.
   • A backup restored in isolation preserves the proof data and can be opened.

   watch out

   • Export without an import or restore rehearsal is not verified portability.