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

8.9 KiB
Raw Blame History

Read-only release-path investigation

2026-10-28 UTC. No push, server edit, reset/clean, migration, deployment, cron action or external mutation performed. Local changes are feature documents plus an isolated scratch Graphify copy. Concurrent workers changed application files independently.

Verified transport and source facts

  • Initial local application HEAD 13f4fdc58dff96f192c612a8d38f33d314f70fad, later 39f5b705c57ca4bf807210e8b887cb8bced7926b during audit; do not bind final integration acceptance to a moving HEAD.
  • origin is /opt/data/cache/scratch/blog-freshness-develop.bundle, not the authoritative network remote. gitea is canina-gitea:parsa/canina.git.
  • /opt/data/.ssh/config:1–8 default parsa-host config disables host checking. Audit explicitly overrode it with -o StrictHostKeyChecking=yes -o UserKnownHostsFile=/opt/data/.ssh/known_hosts. ssh-keygen -F '[172.22.0.1]:2234' found existing pinned ED25519 entry; strict connection succeeded. No TOFU/keyscan trust was introduced.
  • Through that strictly pinned host channel, read /data/ssh/*.pub inside gitea_main (mount /opt/services/git/gitea/gitea -> /data). Verified Gitea ED25519 key fingerprint SHA256:9SzVGbc5GOahn2qgjN64w1VIG/z/AHJBPCsm1oZa81g; public key ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMvMyQsjrxAOKL2E+rbeMKZJyLUwTqe78+2tJQmjcOJR.
  • This exact public key already matches hashed entry 2 in user-owned /opt/data/.ssh/known_hosts (uid 10000, mode 0644), resolved by ssh-keygen -F '[git.parsaaghayi.ir]:222'. Existing gitea config instead points to root-owned /opt/data/.ssh/gitea_known_hosts (0600), inaccessible to current runtime.
  • Local read-only git ls-remote gitea with GIT_SSH_COMMAND='ssh -F /opt/data/.ssh/config -o StrictHostKeyChecking=yes -o UserKnownHostsFile=/opt/data/.ssh/known_hosts -o HostKeyAlgorithms=ssh-ed25519' passed host verification but failed Load key /opt/data/.ssh/canina_gitea: Permission denied then publickey authentication. Host trust is resolved; local private-key permission/provisioning is the remaining transport blocker. Do not print/copy secret key bytes or disable checking.
  • Host-side default Git SSH also disables checking (ssh -G), so audit did not rely on that default. Host /root/.ssh/known_hosts has the same verified Gitea ED25519 key. Explicit strict host-side GIT_SSH_COMMAND='ssh -o StrictHostKeyChecking=yes -o UserKnownHostsFile=/root/.ssh/known_hosts -o HostKeyAlgorithms=ssh-ed25519' git -C /opt/services/canina/stage ls-remote origin refs/heads/develop refs/heads/main succeeded: both refs 00ba4360cf7b161995ee94f220b61f9547e01723. This proves read access, not push permission.
  • Gitea reports v1.22.6. No API token or browser password was requested.

Actual server checkout / runtime observations

Always use git -C /opt/services/canina/stage; never --git-dir from an unrelated cwd. Correct read-only git -C ... status --short really reports numerous staged modifications/deletions plus generated docker-compose.yml, nginx.conf changes and untracked .revalidation.env. These are not the previous bogus all-files-deleted result, but they still make the checkout unsafe for manual cleanup/reuse. It is on develop, HEAD bb81f2c9449357428dd04ba97e921590a4163048, not current remote/runtime SHA. Preserve all of it.

Running Stage labels both identify 00ba4360cf7b161995ee94f220b61f9547e01723:

  • backend image sha256:091a59b7ee5424465406603c2ade96689fdb9726109257630546538b2a1deba8;
  • frontend image sha256:a1609a9033be42d5cff7b998340fe5d869eb75f56b53596ba835ceee5129e12f. These are provenance observations, not SEO feature acceptance. Host checkout lacks the remote object (git cat-file -t 00ba... fails); no fetch was done. Its old HEAD workflow is obsolete and branch-download based. To avoid falsely interpreting that old checkout as active release source, exact remote-SHA files were independently fetched read-only over HTTPS and their SHA256 matched local inspected files:
Source URL suffix under https://git.parsaaghayi.ir/parsa/canina/raw/commit/00ba4360cf7b161995ee94f220b61f9547e01723/ SHA256
.gitea/workflows/deploy.yml 0ed605208bf6c904db01ef2463490748029242db4fa5e172b2be364215936e69
scripts/deploy.sh 346b63cdce43a3e990e2e56670fe65465cb334768cfd46adfc0893d375ecf896
scripts/release-cache-stage.sh 6c90100399cb4b967c8ebf3afa1ae838157da293e6e4e61717d342cb49fcd829

Source-verified official CI contract

Line references are to matching local files in /opt/data/content-maintenance/engine/worktree-concurrency-tdd at audit time; exact remote-SHA URLs above establish remote provenance.

  • .gitea/workflows/deploy.yml:3–17: push to develop/main, runner label canina, DEPLOY_SHA=${{ github.sha }} and Actions flag. Lines 27–35 download dispatcher/release scripts by exact commit SHA and invoke dispatcher with branch.
  • scripts/deploy.sh:4–6: normal develop → release-cache-stage.sh, main → release-cache-prod.sh. Alternate backend-only path is not the normal workflow and must not be used as a shortcut.
  • scripts/release-cache-stage.sh:6: Actions context + 40-char SHA required. Lines 74–98 acquire daemon helper + host inode lock with read-only descriptor; host lock metadata verified 0644 root.
  • Lines 100–129 fetch/check exact origin/develop, archive immutable isolated cache-releases/<SHA>.attempt.*, generate source hash manifest, deliberately preserve operational HEAD/config.
  • Lines 131–161 provision private runtime configuration, copy operational nginx, validate Compose/runtime. Lines 163–170 build and force-recreate only backend/frontend (--no-deps, no orphan prune), verify image/container revision labels.
  • Lines 171–234 check running/restart state and bounded public /api/blogs?page=1&limit=1, frontend /, nginx host readiness and final image parity. These are readiness checks, not authenticated SEO QA.
  • Normal script contains no application npm test run and no migration/seed. No new schema is applied by this path. Any required migration needs separate explicit authorization/backup/DDL review. Worker delivery/cron is not included in this code CI path.
  • The inspected main dispatcher uses code-only prod script too; this audit authorizes neither main push nor Production release. No historical Gate1/Gate2 or unused receipt helper is added as a requirement.

Actionable secure path (not executed)

  1. Keep current verified user-owned /opt/data/.ssh/known_hosts; use the strict SSH override above, or have an authorized administrator provision an accessible least-privilege deploy credential. Do not chmod root-owned key files from this audit, copy keys into artifacts, run blind keyscan, or set checking=no.
  2. Alternative after authorization: package reviewed committed SHA locally; transfer into a new isolated user-owned server staging area through the pinned host transport, and use the existing server deploy key with explicit verified known_hosts. Never modify /opt/services/canina/stage worktree. Successful strict read refs do not prove server key push rights; confirm authorized credential scope before attempting release.
  3. Re-read authoritative refs and fetch into isolated local/integration repo once access is provisioned; check ancestry/full diff and integrate concurrent worker changes on develop without force. Save actual test/build and schema compatibility results at one final SHA.
  4. Only after release authorization and separate schema readiness: non-force push final develop SHA to authoritative Gitea transport. Observe supported push-triggered Actions run at exact SHA and terminal log; do not assume workflow_dispatch API support.
  5. Verify source manifest, backend and frontend image/container labels, actual Actions log/image correlation and authenticated Stage acceptance matrix rows. Old operational HEAD is intentionally not release parity. Keep scheduling disabled/uncreated until Parsa configures individual jobs.

Spec/Graphify validation actually exercised

specify --version →1.2.3; specify check exit 0 (CLI ready, agent integration not established). Explicit SPECIFY_FEATURE=002-seo-performance-tracking SPECIFY_FEATURE_DIRECTORY=<this directory> .specify/scripts/bash/check-prerequisites.sh --json --require-spec --require-tasks --include-tasks exit 0. Installed checker can persist feature path metadata; it was not rerun through setup-plan (which would overwrite plan).

Graph copied before querying to /opt/data/cache/scratch/seo-qa-graph/graphify-out/graph.json, source hash 6a73473cee9e207543fdeeb668bea544f766200a1b16b8a3a9ce18d4e42e51af, built_at_commit=e7ded849f6b1e3bdab2a20d89b3ec7dd0df79cab (stale vs working source). Isolated graphify query 'SEO tracking research finding feedback snapshot deploy stage release' --budget 1200 succeeded, 4304 graph nodes, 199 traversal nodes, output truncated; navigation only, not completeness evidence. Material findings confirmed directly in current controller/service, AnalyticsDeferred and release source. Concurrent original graph cache dirtiness was observed, not reset.