ops(stage): version isolated SEO schema rehearsal and CI operation
This commit is contained in:
1 parent
312fcc2acc
commit
c62d9836e9
10 files changed
+520
No files matched your search
@@ -0,0 +1,2 @@
|
||||
# Plan
|
||||
Python Docker runner fixes source container to canino_db_stage and verifies database caninodb_stage. Dedicated Gitea 1.22 push refs ops/seo-schema-stage-rehearse and ops/seo-schema-stage-apply are disjoint from develop/main. Explicit CI repository secret reviewed SHA controls apply; rehearsal needs event/source binding only. CI downloads archive by immutable SHA. PostgreSQL 16 image pinned to actual Stage image. Full backup bytes remain mode600 in runner private evidence directory. Transactions use advisory locks and bounded timeouts.
|
||||
@@ -0,0 +1,2 @@
|
||||
# Stage SEO schema operation
|
||||
Stage-only dedicated push refs rehearse then apply reviewed SQL, never generic migration chain. Bind exact 40-character event SHA and SQL digest. Preserve all operational configuration and concurrent application edits. Rehearse sanitized actual Stage schema clone; before live application require private full Stage backup and full restore. Validate complete scoped native catalog; leave Prisma historical ledger untouched and record separate operation receipt. No Production access or automatic application deployment.
|
||||
@@ -0,0 +1,5 @@
|
||||
# Tasks
|
||||
- [ ] RED safety tests then implement runner/workflow.
|
||||
- [ ] Exercise actual Stage schema-only sanitized clone restore and SQL catalog parity.
|
||||
- [ ] Inspect supported Gitea push path; commit owned files only; no push pending parent safety review.
|
||||
- [ ] Future authorized CI: full Stage backup/restore then apply and typed readback, retaining receipt.
|
||||
@@ -0,0 +1,15 @@
|
||||
# Verified readiness — 2026-10-28
|
||||
|
||||
Baseline 312fcc2acc8f07dcf20d3d6ee0165ba8e619122e. 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 00ba4360cf7b161995ee94f220b61f9547e01723. 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 e7ded849f6b1e3bdab2a20d89b3ec7dd0df79cab, 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. Unit coverage is binding/typed catalogs/transaction guards, not simulated full CI/restore-failure injection. Actual successful sanitized restore supplies independent integration evidence.
|
||||
Reference in new issue
Block a user