Files
canina/specs/003-stage-seo-schema/verification.md
T

6.1 KiB

Verified readiness — 2026-10-28

Baseline 312fcc2acc. Concurrent backend/worker changes deliberately excluded.

Actual trusted-SSH rehearsal succeeded using schema-only actual Stage dump (106701 bytes, SHA256 e19674dfef4b17d1c9df8fd436e766cae3e47cba3c25aa6de02176e453054197), no private row data. Restored into network-none disposable PostgreSQL16, exact reviewed SQL applied twice. Complete two-table/enum catalog matched independently built reference. Catalog hash b4289a3ab06ede914bb41996925361c8ad42974b4810c02b050fee477442b0e4. Historical live Prisma ledger unchanged. Disposable/lock container absence checked after completion.

Evidence: /opt/data/cache/scratch/stage-seo-rehearsal-20261028/{receipt.json,catalog.json,stage-schema.dump}. This is schema compatibility/restore evidence, NOT full-data recovery or CI execution. SQL SHA256 de1386398026c6373ce8692fb165b904e189f830d7b20914d8a4b512a47f9d16. Stage database observed 16399383 bytes; host available ~11GB. Final TCP readiness used throughout restore, not temporary init socket.

Gitea 1.22.6 push support established in existing release investigation, normal deploy filters main/develop only. Dedicated operation refs currently absent. Runner git/python3/docker present; real runner HTTPS ls-remote returned develop 00ba4360cf. Shared host deployment inode lock was acquired by real helper and released. Current runner image and pinned Stage PG16 image available on daemon. No application, production, cron, commerce-mode, or operational config mutation.

Readiness: local tooling and sanitized restore rehearsed. Parent must review committed safety before any push. Supported next path is non-force dedicated operation-ref push and actual Actions terminal log at exact SHA. Apply additionally needs authorized repository secret provisioning for exact reviewed SHA and real full Stage data restore (implemented but not executed). No generic migration chain or historical ledger mutation. No claim of remote push rights from read access.

Graphify queried before edit and before commit in isolated /opt/data/cache/scratch/seo-qa-graph (4304 nodes, stale graph binding e7ded849f6, original hash 6a73473cee9e207543fdeeb668bea544f766200a1b16b8a3a9ce18d4e42e51af). Navigation only; migration/workflow contracts checked directly. New tooling absent from old graph; no generated graph committed.

Initial RED: operation test import failed because operation.py did not exist; catalog child also recorded initial RED. Final GREEN recorded in command output. Initial unit coverage was binding/typed catalogs/transaction guards. Actual successful sanitized restore supplies independent integration evidence.

Independent fault-injection review — baseline c62d983

Independently read /opt/data/cache/scratch/stage-seo-rehearsal-c62d983/receipt.json and recomputed dump size/hash, canonical sorted catalog hash and SQL hash against the actual existing files: all match. The receipt binds c62d9836e95c3fd1a5bc196bb759b6416d0c4908; dump 106701 bytes, SHA256 d9d310a4f6a5255600a3b2bd459aefa50fbf8a4d12fe66cc4af12d759fc59f57; catalog b4289a3ab06ede914bb41996925361c8ad42974b4810c02b050fee477442b0e4. Evidence directory mode700 and dump mode600. This verifies artifact consistency, not independent observation of the original run, full-data recovery or current live schema.

New tests exercise actual main() with an explicitly synthetic in-process transport double: backup process failure, empty dump, restore failure, TCP-readiness exhaustion (60 probes), transport timeout, clone catalog mismatch and missing lock-acquisition marker all prevent live apply and clean only captured IDs in reverse order. Existing contended lock is never removed. Cleanup error attempts every captured ID; stderr remains observable but is not treated as proof cleanup succeeded. Successful path asserts full dump (not schema-only), exit-on-error TCP restore, two clone applies before the single Stage apply and private backup permissions. Missing/stale/newline-reviewed SHA, wrong event/source SHA, non-CI and wrong destination refs all fail before Docker.

Behavioral RED: 17 tests ran, one failure because a successful pg_dump process returning zero bytes was accepted by main(). Minimal fix refuses an empty backup immediately. Post-fix suite: python -m unittest discover -s scripts/stage-schema -v, 17 passed. Transport doubles prove control flow only, not real full-data restore or CI execution. No application builds were needed: owned changes are Stage tooling/specs only; application/catalog mode, secrets, runtime and deployments untouched.

Existing credential/admin path (metadata only)

Pinned SSH inspection confirms gitea_main Gitea 1.22.6 and existing active administrator parsa. Gitea admin CLI supports user/token administration but has no repository-secret subcommand; no token was generated or credential read. Public instance Swagger confirms GET /repos/{owner}/{repo}/actions/secrets and PUT/DELETE /repos/{owner}/{repo}/actions/secrets/{secretname}. Easiest least-change route is the existing administrator's authenticated repository Settings → Actions → Secrets UI at https://git.parsaaghayi.ir/parsa/canina/settings/actions/secrets, setting only STAGE_SCHEMA_REVIEWED_SHA to the final reviewed full commit SHA. This is an existing account/admin path, not evidence that a saved reusable API token is available; do not mint an extra token or change any password merely for this operation. No secret values inspected or modified.

Release still requires parent review and a frozen tested SHA: non-force push that exact commit to the dedicated rehearsal ref, inspect real terminal CI success, then bind the same reviewed SHA through existing repository-secret administration and push the identical commit to the dedicated apply ref. That CI must complete private full-data backup/restore before Stage DDL, retain receipt/backup and verify Stage scoped catalog/ledger/cleanup. Current sanitized receipt alone is not sufficient. No develop/main application push, runtime restart, generic migrate deploy or production operation is authorized by this review.