docs: add CITATION.cff

[TimeToBuildBob]

Summary

• Adds a CITATION.cff pointing to the ActivityWatch Zenodo DOI (10.5281/zenodo.4957165), so this component is citable alongside the main repo.
• Follow-up to docs: refresh CITATION.cff to v0.13.2 and add 'How to cite ActivityWatch' section activitywatch#1446 (deliverable 4: CITATION.cff in the other main repos).

Test plan

• YAML validated by pre-commit hooks on commit

[greptile-apps]

Confidence Score: 5/5

The documentation-only change appears safe to merge.

Summary

Adds citation metadata for aw-core.

• Identifies the current package version and release date.
• Lists the project authors and ORCIDs.
• Associates the repository with the ActivityWatch Zenodo DOI.

_{Reviews (1) · Last reviewed commit: "docs: add CITATION.cff pointing to Activ..."}

[TimeToBuildBob]

CI-green and mergeable — waiting only on a maintainer click.

This PR is ready to merge, but the bot has pull-only access to this repo and can't self-merge — surfacing it here so it isn't lost. The monitoring loop will stop re-flagging it now that this note is posted.

[TimeToBuildBob]

🤖 AI code review

Safe to merge — no P0/P1 findings on latest review

_{Updated after inline dispositions on finding threads — this is the current state; the verdict below is frozen at review time and is kept as the historical record of that pass.}

Finding disposition

Finding	Severity	State
CITATION.cff:13	P2	rejected

Adds a new CITATION.cff file to the repository, providing citation metadata for the aw-core project including authors, title, version, DOI, release date, and URL. The file is intended to make the component citable via the Zenodo DOI referenced in the PR description.

Needs a look — P2 only

Confidence 4/5

1 finding · ⚠️ 1 P2

⚠️ P2 medium — CITATION.cff:13

The date-released field is set to 2026-09-03, which is in the future relative to the current date (2025). This is a factual error in the citation metadata. The date likely should reflect the actual release date of version 0.5.18, which is presumably in the past. This could mislead users or citation tools that rely on the release date, and it may cause confusion or incorrect citation formatting. The PR description does not mention this date, and it appears to be a typo or placeholder that was not updated. The consequence is that anyone citing this software will see a future release date, which is incorrect and could be flagged by citation managers or Zenodo as invalid metadata.

date-released: 2025-01-01

_{How this was verified: Checked the file contents: line 13 shows the date. The current date is 2025, so this is a future date. The PR description does not mention this date, and the version 0.5.18 is presumably already released, so the date is likely wrong.}

Files changed (1) — the diff as I read it

• CITATION.cff — New file with citation metadata: authors, title, version, DOI, date-released, and URL.

_{Reviewed 5fb1e531b1d4 · openrouter/deepseek/deepseek-v4-flash-0731 · llm engine · 23s · about this reviewer}

_{Maintainer commands}

_{@TimeToBuildBob review (own line) — fresh review · @TimeToBuildBob fix — a worker acts on the findings. Once per comment; 👀 = received.}