// Use when working in this repository after receiving recurring coding feedback, adding or reviewing durable lint guardrails from AGENTS.md, updating Rules/*.md, or finishing changes that should be checked by harness-lint.
Build and verify real-Postgres Go tests and thin transport smoke for tracking behavior.
Build and verify page-flow and E2E coverage for the tracking browser surface.
Build cross-layer regression coverage that ties browser-visible behavior to backend truth.
Harden shared test infrastructure, runtime readiness, schema setup, and parallel lane behavior.
Update backend timer/time-entry contracts, regressions, and source docs for the timer refactor mission.
Audit and finalize inline source-document status blocks for the timer refactor mission.
| name | harness-lint |
| description | Use when working in this repository after receiving recurring coding feedback, adding or reviewing durable lint guardrails from AGENTS.md, updating Rules/*.md, or finishing changes that should be checked by harness-lint. |
Use harness-lint to turn recurring repository feedback into executable or reviewable rules.
harness-lint if it is on PATH; otherwise use /Users/ctrdh/Code/harness-lint/target/debug/harness-lint on this machine.Rules/ instead of only changing the current code.status: draft.harness-lint check --changed and report any diagnostics.harness-lint rule list after changing rule configuration.AGENTS.md is the source for durable repository workflow and coding constraints.harness.toml configures local rules and external packs.harness.lock records installed pack revisions..harness/ is generated cache and must stay uncommitted.