Skip to content

MamNajem history-copy evidence

Rename note (2026-10-17): project 84799693 is now mamnajem/landing-frontend; historical names and revisions below are retained as evidence.

  • Run ID: 20260725T070221Z-068ccbb1a63b1fc6
  • Recorded at: 2026-07-25T10:34:46+02:00
  • Status: DONE_WITH_CONCERNS
  • GitLab group: mamnajem, ID 138222962, private
  • Source mirror root: /tmp/mamnajem-source-mirrors.JVfKY9edgB
  • Final migration archive: /home/szymek/pro/mamnajem-migration-archive/20260725T070221Z-068ccbb1a63b1fc6 remains absent
  • No donor worktree, donor branch/tag, application source file, execution ledger, production target branch, target source tree, or non-GitLab cloud resource was modified.

Frozen-input gate

  • source-commit-ledger.sha256: exit 0; ledger SHA-256 8c2deb6be4c0a7840a78796a31c78945e661af108b048406202020863dd7124a.
  • mamnajem-naming-contract.sha256: exit 0; all three frozen files matched.
  • Group ID 138222962: private, default branch intent integration, Auto DevOps disabled, requests disabled, share lock enabled, xSzymo active at Owner access level 50.
  • All six target paths returned HTTP 404 before creation.
  • Every source mirror matched its frozen scoped-ref and all-object inventory SHA-256 and passed git fsck --full with exit 0.

Target projects and active history

Repository Target ID Donor ID Active target SHA / tree Preserved donor production SHA Heads Original tags -> target tags Notes Source OIDs -> target OIDs
architecture REDACTED_PROJECT_ID REDACTED_PROJECT_ID integration 71efbcf781ed0f3c4a18d6321a8a009a23fb616c / 1e0abd2bc510a554e4bb2ef4c0042ca1c3e03e57 7f17a6cf52ea529b86aaabe8bc68338ecd8dbe83 integration 0 -> 19 0 2551 -> 2570
backend REDACTED_PROJECT_ID REDACTED_PROJECT_ID integration 86100b77fd024fd85ea95b0b9940e3c5826cf5b6 / 599b079a2653edc09e304858aa36883d65b02ed9 76076259951564db28085d74aff27c9020638119 integration 2 -> 528 0 21920 -> 22446
docs REDACTED_PROJECT_ID REDACTED_PROJECT_ID integration 47162b927f287e7590fa26c7778e8a129a79b058 / f05787f12458d9aef6a60867ecfc0a5394b3e50f absent in donor integration 0 -> 128 0 1232 -> 1360
mobile-frontend REDACTED_PROJECT_ID REDACTED_PROJECT_ID develop and integration 9529e4bd13153171f49f91852e53f442f01d6602 / c71d6ee1efea032f85ea334b3aea12ca253701fb 164b883dd0b530bc0738d95fb35d90921429d26a develop, integration 2 -> 180 0 33323 -> 33501
web-frontend REDACTED_PROJECT_ID REDACTED_PROJECT_ID integration fafb456312e8906120ac614f706704a584901fe2 / 3750a3e46b2288bcb7381e1b76a73691dfa9f399 018b7d32f0d4496fa521f8910b344664146fd980 integration 0 -> 1 0 249 -> 250
web-admin REDACTED_PROJECT_ID REDACTED_PROJECT_ID integration dc8c107425f9b8c39c461bb24fccddfcf7134bd2 / dc55cf34652ad7424091eeb5a5445eb29ad0fe79 99cbcd331d0192dd24950a9c8a2da47c1057e666 integration 0 -> 3 0 557 -> 560

Every target symbolic HEAD is refs/heads/integration. All six target production heads are absent. The five donor production tips peel exactly from history/source/production.

Ref and object inventory hashes

Repository Source scoped refs SHA-256 Target refs SHA-256 Source all-object SHA-256 Target all-object SHA-256 Non-active head map count / SHA-256 Internal-ref map count / SHA-256
architecture c8d3251170b8be29cd4544bfdee8ebec7a53c82db6a74e59b82dcc5a67fbe3c5 97ef71f8367eb4123ea57859b7541c9e838ad6468c5a192249c425b9a7c8b505 402046ded7973f9916e74628ffbb7618402c95a3d764f7b47ab59469f1b7b468 80440f68b82c1d61efb6d76f97147ec2c7e58660d0bf6c98f1cd79fa228ffeed 3 / 2761e5361e80d742d7086189edec4c97dbdb19cccd9d0c80a04eacbb0e23b81c 16 / cf4a86e60551caa89a913624f794df5af2f73ceda9c5e4097390ff336691d3ad
backend 5876826f48b4f546d72af398a8bda26cd0b2831f7a6a1cabf4b106aef7687b39 75ccdc023ff25dd5911fb211a2b45984ea528a783f80275d060c2d4374b9e831 733f250602d093bb73ca8eb9786858b21316fb7e6062213f3f6edeccecbce7cc 97c26bf5e9f5dcc252c7f12040fae2e845682031e34c79c3e2b8ec1a38311127 10 / d6b7d6ae0c48a7dfe63cbd4163260cc3d8f93b02a9bdc3a4c6562c7c5ef41c13 516 / 1d0a4f65a295b2e8bd7c17777cb8e9be81d1130dc6d63c674e1b3bc6ceca0dee
docs 092bae9c9c89fded7b562f2d2e0f6f601953bd511d41d22f6d24bd6550d6de81 ea649d83c38908b3ef4d5ca36ac8603e1c9f2ef60a28b28cc66f9356a9479c19 5adaed145e391dd1c0da9902bd67c6ae9478c6dcbad2046392d9da1161658581 734f2281533223f12e138a78edfe99d21fe9d201e44e956db13a5c0fed438c37 0 / e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 128 / 9bb2b351ddeb54781f6907a2a3ef2cf79ad200bd9777ccb544fd31c70a9474e7
mobile-frontend 9d8cdb56666db30d455e50049bfb1c701522783d0fc24a98448f4de4f5ba7304 67ab80bdfe2417ddd8d9199f402ce65dfc7d2c82b9206fa7d30cb57a491b6923 3a6897445089c90c8d731ca324a546b754d4365cf61200aafac68544815ef54b 2139ddb79ebcecdde6bd29358f113d3ad5bd2c4e5191d69f275dda38ff5c7138 11 / f35f2c1a1792954c5b18dd0f4a40d93697d06824a30328641c5de67a3ff10234 167 / a930cd0dc547074e8636a3a29a2c529eb104df82ed774de8fa28fe4a5a2df2c5
web-frontend b85cfbd62d8a7134aa7499fc29fd4e070ca1209cfa21287ad3621c34c120c10a 973ac89b7868471403a2258b097967430903becdb23fcded137e96098255d4ea 5cd6578c26aa20c968cdd7fd63c1bf1bc633629452a1cfae72f5e20ddd8b9ab9 e55e3cef068a6ba314d7c3c8428825962cd92a98cfd166076292d890c91111c9 1 / befcf9cb797506136c500575efbb6d16c01cdfbb969f152fbf8838fe63e24ba1 0 / e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
web-admin c9e5b01c4a820994520a07855003826c65701bf1b945158d3522e8c811578d6a eb22432bfb6abf411a83a9512b00b9759374c0d0625c90333e41d99ed2ac654b e4cc54a93bf06f9d07d46cb9eac32a6abe80f90cc49f342e944c51456e6ebd51 f3ceda1715a0bfbc4d29ed4d7932904184e823fdbec7aef886f80e02638e4396 1 / 7903de097fcec771472521adb215024e192b36bba39ae0a908a509df441576a0 2 / a3581f7cbe85ccadce3dbc9ac19de50ce1c4020b3d8657b7d4d1e1bffb961f22

The 829 GitLab-internal donor refs (refs/merge-requests/* and deployment refs) were not pushed under their internal names. Their exact tips are reachable through annotated history/source/internal/... tags. This was required to make every frozen rev-list --objects --all object reachable without leaking GitLab-internal refs.

Git LFS

git lfs fetch --all origin completed in all six untouched source mirrors. An exhaustive all-ref blob scan found zero canonical LFS pointers and zero local LFS objects in every repository. Source pointer, source object, target pointer, and target object inventories therefore each contain zero rows and have SHA-256 e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855. git lfs fsck also exited 0 in every source and fresh target mirror, but was not treated as an all-ref proof because its default scope is HEAD.

Recovery staging

Staging root: /home/szymek/pro/mamnajem-bootstrap-evidence/migration-staging/20260725T070221Z-068ccbb1a63b1fc6/git-history/.

Repository Bundle SHA-256 Bundle refs / objects LFS ustar SHA-256 Archived LFS objects
architecture 68819c1ff5676105725a0d31bd137841dc05a99b954786a765f55d227778008c 20 / 2551 22ada03fe582cc6960b30fbd21c2177697932cc0f03ba101af8c07498d6e8b27 0
backend e11da78604688ed438eea6faed3d37e1943dffd3ae3d3c308b84e373bd875b0f 529 / 21920 22ada03fe582cc6960b30fbd21c2177697932cc0f03ba101af8c07498d6e8b27 0
docs a709467aa609d9b620bc2d96376edc0f4811252ade11f9b225f0a516f7789c49 129 / 1232 22ada03fe582cc6960b30fbd21c2177697932cc0f03ba101af8c07498d6e8b27 0
mobile-frontend e8172dbb4325aa4db4c5f60f6f91328a12a3d8d60fe771fddbd03acc779987bf 182 / 33323 22ada03fe582cc6960b30fbd21c2177697932cc0f03ba101af8c07498d6e8b27 0
web-frontend f001cb1bbce044a03311746aaf687d71b0e8248f5ac40ebcb10cdb5bd510654f 2 / 249 22ada03fe582cc6960b30fbd21c2177697932cc0f03ba101af8c07498d6e8b27 0
web-admin 6f22aa63231f98f058878e89422b5173b8b6701f158e99cefe16a214737df6bb 4 / 557 22ada03fe582cc6960b30fbd21c2177697932cc0f03ba101af8c07498d6e8b27 0

Each bundle was verified and fetched into a fresh empty bare repository, with exact all-ref and object-inventory equality plus git fsck --full. Each uncompressed ustar uses sorted names, epoch mtime, numeric owner/group 0/0, and contains only lfs/objects; extraction and per-OID SHA-256 verification passed. The 12-file relative-path manifest SHA-256 is 7c56178a483dbcde1793ae3935ebd8d89f66904b0612b05600f7adca322cd3ba. Staging files are mode 0400 and staging directories mode 0500.

Governance

  • All targets are private, default to integration, use merge method ff, require pipeline success for merge, and keep both builds_access_level=disabled and forking_access_level=disabled.
  • integration is protected with push/merge access 40, force-push disabled, and no delegated unprotect access in all six projects. Mobile develop has the same exact protection.
  • The absent production name is preprotected in all six projects with push access 0, merge access 40, force-push disabled, and no delegated unprotect access; no production branch was created.
  • history/source/* and every exact original donor tag are protected with create access 0 (No one).
  • Effective project members are coditiostudio and xSzymo, both active Owner level 50; no effective member below Owner exists.
  • The exact owner identities are coditiostudio ID REDACTED_PROJECT_ID and xSzymo ID 1308375.
  • The group and every project have zero access tokens and zero deploy tokens; every target also has zero forks and zero project shares, and the group has zero shared projects/groups.
  • GitLab rejected project-level branch/tag access level 50. The current tier also rejected a protected-tag allowed_to_create rule for the exact xSzymo user. The non-weakened fallback is access 0, so an Owner recovery action must first change the protection rule.
  • A live exact-user protected-branch unprotect probe also failed with HTTP 400: Unprotect access levels user must be blank. The fallback therefore delegates unprotect access to nobody; Owners retain the platform-level recovery path.
  • GitLab has no protected-notes API. All six copied note counts are zero, CI is disabled, and no lower-privilege project member exists. Any future note mutation invalidates this evidence and requires full parity restoration.
  • With builds_access_level=disabled, GitLab returns HTTP 403 from each target pipelines-list API. The consolidated gate required that exact response and independently re-read builds_access_level=disabled from every project.

Governance quality-review correction

  • Recorded at 2026-07-25T13:26:24+02:00 against run ID 20260725T070221Z-068ccbb1a63b1fc6.
  • The versioned schema-v2 contract pins the exact group/project IDs, exact active heads and SHAs, exact Owner IDs, all mutable settings, exact protected branch/tag access arrays, absent-but-preprotected production, and all zero-resource invariants.
  • The apply tool supports --dry-run, --apply, and --verify. It checks Owner authority and immutable identities before planning mutations, never creates a repository branch, and does not delete tokens or memberships.
  • Dry-run reported DRY_RUN_OK actions=0; two consecutive apply passes each reported APPLY_OK actions=0. The standalone live verifier then passed all six projects, proving the current state is already converged and the fix loop is idempotent.
  • All list checks fetch every GitLab page and fail closed on permission errors. The verifier checked exact group membership, group projects/shares/tokens/deploy tokens, project heads/protections/tags/tokens/deploy tokens/forks/shares, and donor archival.
  • Ordinary automation pushes must use npm run push:mamnajem -- <mamnajem/project> <remote> <source:destination>.... The wrapper permits only exact active head refspecs and rejects all tags, notes, deletes, forced refspecs, wildcards, production, and feature branches.
  • CI remains disabled. The committed CI contract requires a token-only HTTPS live verification job and explicit evidence/run-ID variables; it fails when those inputs are missing.

Donor archive state

Only after target parity, recovery staging, governance, and post-governance reachability passed, all donors were archived through GitLab and re-read:

Donor Project ID Archived
mamnajem/architecture REDACTED_PROJECT_ID true
mamnajem/backend REDACTED_PROJECT_ID true
mamnajem/docs REDACTED_PROJECT_ID true
mamnajem/mobile-frontend REDACTED_PROJECT_ID true
mamnajem/web-frontend REDACTED_PROJECT_ID true
mamnajem/web-admin REDACTED_PROJECT_ID true

Command and exit-code record

Command family Exit Result
sha256sum -c source-commit-ledger.sha256 0 frozen ledger verified
sha256sum -c mamnajem-naming-contract.sha256 0 naming YAML, validator, and tests verified
source and target git fsck --full 0 all repositories and verification mirrors passed
source git lfs fetch --all origin; target-prep and fresh-target LFS fetch/push 0 completed; exhaustive inventories contain zero pointers/objects
six glab repo create ... --private --defaultBranch integration --skipGitInit plus immediate CI disable 0 six empty private projects created before any ref push
six explicit git push --atomic refspec pushes 0 only approved heads, tags, and notes namespace; never --mirror
first fresh-clone object-subset assertion 1 exposed 23 architecture objects reachable only from omitted GitLab-internal refs; corrected with preservation tags
corrective internal-preservation atomic tag pushes 0 all 829 internal-ref tips preserved without pushing internal refs
redundant backend post-correction git lfs push --all rescan 130 stopped with controller approval after initial all-ref push and zero-pointer proof; no LFS object existed to transfer
first LFS tar attempt 2 source lacked a physical empty lfs/objects directory; partial files preserved outside staging, canonical empty hierarchy used without touching source mirrors
six git bundle create --all, bundle verify/fetch, and LFS ustar extraction checks 0 all recovery pairs verified
protected branch/tag access level 50 attempts 1 / HTTP 400 unsupported by GitLab project APIs
exact-owner protected-tag user rule attempt 1 / HTTP 400 unsupported on current tier
protected-tag create_access_level=0 fallback 0 stronger deny-all mutation rule applied
exact-owner protected-branch unprotect rule probe 1 / HTTP 400 platform rejected user-scoped unprotect; no delegated unprotect access retained
governance quality-review dry-run 0 DRY_RUN_OK actions=0
governance quality-review apply, first and second pass 0 both returned APPLY_OK actions=0; no live mutation was necessary
governance quality-review standalone verifier 0 exact group/project IDs, heads, settings, protections, owners, zero resources, and archived donors passed
post-governance fresh clones and source-object subset checks 0 all target objects reachable; production absent
six donor archive API calls and re-reads 0 all donors archived=true
consolidated fresh-clone gate after donor archival 0 all six live ref snapshots exact; object inventories exact and source-complete; git fsck --full, exhaustive zero-LFS inventory, pinned Git LFS 3.4.1 fetch/fsck, recovery bundle verification, governance, donor archive, and final-archive-absence checks passed

Raw per-repository maps, inventories, governance snapshots, and evidence checksum files are under history-copy/ with mode 0600. No commit was created because this task did not modify target source.