Files
canina/specs/002-seo-performance-tracking/tasks.md
T

41 lines
5.3 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Tasks: SEO tracking (unverified tasks remain open)
No checked task means implementation failure; unchecked means independent evidence is not recorded here. Department workers may implement in parallel, but final validation uses one integrated SHA. Acceptance row IDs refer to `acceptance-matrix.md`.
## Scope / prerequisites
- [x] T001 PMO: inspect initial feature documents and actual installed Spec Kit 1.2.3; run `specify check` and explicit-feature prerequisite check (exit 0). Presence checks do not certify business quality.
- [x] T002 QA: expand omissions and maintain independent acceptance matrix and read-only release investigation.
- [ ] T003 Research/SEO + Growth + Medical: document many actions/targets/keywords/goals, evidence and units; resolve only genuinely unresolved business choices with Parsa (Q03, Q10–Q13).
## Tests before implementation (backend/UI/worker may proceed in non-overlapping files)
- [ ] T010 Engineering/DBA: RED then GREEN real HTTP auth, roles, DTO boundaries, Persian search/stable pagination and database contracts (Q01–Q04).
- [ ] T011 Engineering + Content/SEO: RED then GREEN concurrent feedback, stale directive and real downstream execution blocking (Q05–Q06).
- [ ] T012 Engineering/DBA + worker: isolated PostgreSQL history/restart/concurrent idempotent ingestion, payload conflicts and partial availability (Q07–Q09).
- [ ] T013 Frontend/UX: RED then GREEN list/navigation/detail, nullable metrics, goals/history, feedback success/failure/conflict and mobile keyboard tests (Q14).
- [ ] T014 Worker + DevOps: test provider error/timeout/quota/pagination/canonical URL handling and durable department alert dedupe/delivery recovery (Q10–Q13, Q15).
## Integrated implementation / real acceptance
- [ ] T020 Engineering/DBA: implement reviewed many-action/goal schema and API, versioned feedback/history, per-metric/source provenance and idempotency; prepare separate schema review/backup/rollback, do not apply remotely in code rollout.
- [ ] T021 Frontend/UX: integrate actual mounted page/sidebar and API contract; expose all accepted scope and unknown limitations.
- [ ] T022 Worker + Research/SEO: real GSC/GA4 collection and persistent snapshots; documented approved Clarity report input or explicit unavailable status; no fake metrics.
- [ ] T023 Growth/Commerce: prove subscription/cart/checkout/navigation event collection and lawful article-to-order join; document unsupported/unknown where absent, no total-order attribution shortcut.
- [ ] T024 Content/Medical + SEO: demonstrate current CEO directive reaches real article/SEO execution and stale work is prevented at finalization.
- [ ] T025 QA/PMO: run every matrix row independently; save real source response, HTTP/database/browser and department delivery artifacts. Keep blocked rows open and distinguish fixture-only coverage.
- [ ] T026 QA: full backend tests/build; admin tests/typecheck/build; worker tests against integrated SHA, with exact commands/counts/exit codes and RED/GREEN logs.
## Local integration evidence (2026-10-28; partial scope, not matrix closure)
- [x] I001 Port worker source, 17 tests and docs into `scripts/seo-performance/` without credentials/state/cache.
- [x] I002 Exercise actual Nest module over TCP with shared auth guards and disposable PostgreSQL: create finding, feedback revision, stale action 409, correct action link, worker list, SQLite reopen, snapshot POST/GET, identical network retry and changed-payload conflict. Test-only JWT identity; production authentication remains open.
- [x] I003 Read real Google GSC/GA4 blackseed article measurements and persist through worker/HTTP/PG. Preserve Clarity/commerce/scroll as unavailable/null. Sanitized receipt: `scripts/seo-performance/evidence/real-http-receipt.json`.
- [x] I004 Run focused backend (4 suites/16 tests), worker (17 tests) and backend build successfully. Full backend still fails existing WikiService assertion (815 pass/1 fail/8 skip); no claim that T026 or broad matrix passes.
See `scripts/seo-performance/VERIFICATION.md` for baseline, commands, setup failure and open boundaries. Existing T010–T026 remain open where their wider acceptance is not fully exercised. No new implementation fix or behavioral RED/GREEN claimed because integration found no contract mismatch.
## Authorized release only (not authorized by this audit)
- [ ] T030 DevOps: resolve unreadable local deploy key through approved provisioning or authorized trusted-host Git transport; verify host pins and remote refs/ancestry without disabling verification.
- [ ] T031 Engineering/DBA: obtain separate schema-operation authorization; apply/reconcile only reviewed compatible schema with backup/rollback evidence if required.
- [ ] T032 Integration owner: clean reviewed owned files, exact SHA and non-force push to develop only after real tests; observe official exact-SHA Actions run through final log.
- [ ] T033 QA + DevOps: verify both Stage image/container SHA labels, manifest and authenticated real browser/provider behavior. Never reset/clean dirty operational checkout.
- [ ] T034 PMO: collect all department evidence; no Stage/main/Production claims from local tests; separately seek authorized main promotion only after complete Stage acceptance.
- [ ] T035 DevOps: deliver worker invocation/dry-run documentation and proposed per-job cadence to Parsa. Do NOT create or activate cron; manual individual configuration is Parsa's preference.