Archive axisrow/profile after rollout soak period

[axisrow]

Summary

axisrow/profile is currently retained as migration history (isArchived: false). Per the workflow defined in README.md:10:

axisrow/profile is retained as migration history and will be archived after the rollout soak period.

This issue tracks the explicit archive gate so the step happens once the rollout criteria are verifiably met — not on a guess.

Context

• PR Fix migration rollout blockers #7 (Fix migration rollout blockers) was merged — migration blockers resolved.
• The repository is now the single source of truth for the site, profile data, and Pages workflows (README.md:3-11); axisrow/profile is kept only as migration history.
• Related supply-chain hardening (issue Supply-chain: hash-lock pip + pin GitHub Actions to SHAs in the credential-bearing publish job #5) and the build_pages artifact-boundary redesign (issue build_pages: eliminate arbitrary-path rmtree — redesign to canonical-only, fixed allowlist, fail-closed (no recursive deletion) #3 / PR fix(build_pages): eliminate arbitrary-path rmtree — canonical-only, allowlist, fail-closed #4) are already merged.

Archive checklist (all must be true)

• Both repository secrets installed and working: PAT_APP_ID, APP_PRIVATE_KEY.
• At least one successful manual publish through the new pipeline (publish.yml with the GitHub App installation token).
• Legacy Pages disabled / confirmed no longer the production source.
• Soak period passed with no incidents (no failed publishes, no token/secret issues, no rollback) — record the duration and start date.
• No outstanding references to axisrow/profile as an active source in the codebase or workflows.

When done

Archive axisrow/profile via gh repo archive axisrow/profile (or the GitHub UI). Do not delete it — it stays as migration history, just archived/read-only.

Out of scope

• Supply-chain Dependabot PRs (chore(deps)(deps): bump actions/upload-artifact from 4.6.2 to 7.0.1 #8–chore(deps)(deps): bump actions/deploy-pages from 4.0.5 to 5.0.0 #13) and any future artifact-boundary work — tracked separately.

[axisrow]

Soak-период начат 2026-07-23 после переключения Pages на GitHub Actions.

Базовая проверка:

• Pages API: build_type: workflow;
• ручной publish: https://github.com/axisrow/axisrow.github.io/actions/runs/30011854755 — success;
• production и Demoscene manifest: HTTP 200;
• служебные profile/**, тесты и package.json: HTTP 404;
• Telegram: https://t.me/prog_ai?direct;
• один Pages deployment на запуск.

axisrow/profile архивировать только после семи последовательных успешных ежедневных публикаций. Issue №1–8 остаются в старом репозитории как архивная история и не переносятся.

[axisrow]

Soak check — 2026-07-25

Result: do not archive axisrow/profile.

Blocking conditions:

• The no-change gate remains active until 2026-07-30.
• Publish profile and Pages has successful runs on only three distinct post-2026-07-23 UTC dates so far: 2026-07-23, 2026-07-24, and 2026-07-25. Seven consecutive successful daily runs are not yet confirmed. Latest successful runs: #18, #16, #14.

Verified now:

• Pages API: build_type=workflow, status built.
• Production / and /demoscene_classics/dist/manifest.json: HTTP 200.
• /profile/projects.json, /profile/sync/generate.py, /profile/tests/test_generate.py, and /package.json: HTTP 404.
• axisrow/profile#12 remains closed.
• Issues Add i18n support for English, Russian, and Chinese #1–chore(deps)(deps): bump actions/upload-artifact from 4.6.2 to 7.0.1 #8 remain in axisrow/profile; no issue was moved or modified by this check.

The live Telegram-link recheck became inconclusive after the initial public URL probes because the local proxy/DNS path was unavailable; it will be rechecked on the next daily run. No repository, branch, issue, or comment was deleted or changed.

[axisrow]

Soak check 2026-07-26 (Asia/Shanghai): archive gate is not eligible.

• Date gate: before 2026-07-30.
• Workflow gate: successful Publish profile and Pages runs currently cover only three distinct post-2026-07-23 UTC days — Jul 23 (30023418113), Jul 24 (30066772535), and Jul 25 (30143956526) — not seven consecutive daily runs.
• GitHub Pages API: build_type=workflow; axisrow/profile#12 remains closed.
• Production HTTP and Telegram-link checks are unconfirmed this run: the configured localhost proxy 127.0.0.1:10808 was unavailable, and direct probes could not resolve axisrow.github.io.

No repository, branch, code, PR, or axisrow/profile issues #1-8 was changed; no archival action was taken.