[Mr-Neutr0n]

Fixes #214

Documented a temporary-folder recipe that writes a few fictional aware-timestamp periods through ActivityDatabase/ActivityState, with an expected-versus-actual report template linked to the existing demo generator.

Verification: python -m pytest — 158 passed, 7 skipped, 141 subtests passed (run locally; the branch is current with main).

---

This change was prepared with AI assistance under human direction and review.

[HafidIdrissi]

I read #214, CONTRIBUTING.md, the full documentation diff and the ActivityState/ActivityDatabase/report interfaces. The two aware fictional periods, explicitly temporary database/report, 15-minute active/idle expectations and link to the full generator fit the requested recipe. No unrelated runtime change is needed.

Before approval, execute the minimal recipe and generate its report with the configured venv, recording actual OS/Python, exact invocation, observed active/idle/category output, and confirmation that all files stayed in the temporary directory. Use the same explicit venv interpreter in the documented report command rather than an ambiguous global python. Preview the new section/anchor and links. This is docs-only: a full unrelated unit suite is not required. If you cannot run the recipe, identify that check and its reason explicitly instead of the current blank 'Could not run ...: .' sentence; a maintainer still needs to supply the actual recipe validation.

Tests 41046586024 now succeeds, so the description's execution-approval/no-CI statement is obsolete. I observed that status, not a local test execution. There was an earlier claim on #214; I have coordinated with that contributor to focus on assigned #257/#392 while this PR is reviewed. For future work, wait for scope confirmation and take one task at a time rather than starting several overlapping backlog PRs. I have not executed this recipe or a renderer locally.