laboratory/docs/POST_MIGRATION_INTAKE.md

Post-migration contribution intake

Current reconciliation: 2026-10-18. The owner scheduled migration first on 2026-10-11; the Laboratory cutover was accepted on 2026-10-13. The roadmap owns current priority. This register preserves the original received heads and requirements alongside subsequent delivery; its historical criteria are not a request to repeat accepted work. The infrastructure rollout retains migration history.

Delivery disposition — 2026-10-18

Handoff	Source	Live	Google	Remaining / historical PR
Laboratory #119	Canonicals integrated through #128, 4d8d751b9d6d1f6155b264a71199300a220df893; reference/Explore social fix in Core d91fd57598366723548c6a4ca820182b5a79fb4e.	Accepted Core update 2026-10-15; fresh 2026-10-17 reads show exact Explore canonical and og:url, and 303 redirects for Cinnamon references 9037/8541/8006/8244 to their recorded upstream PRs. These fixes are complete.	No Google completion established by this reconciliation.	Check existing validations/requests and later crawl/indexing, then reconcile the original checklist; draft remains open at its received head.
Laboratory #120	#131, 4cc434a80a0f70ea3a448f387a09b699f04e8979, integrates profile privacy/encoding/types and the separate service/operator identity graph.	Accepted 2026-10-14 and retained in subsequent deployment.	No Google completion established. About data alone does not satisfy the root-site-name requirement.	Google follow-up and checklist return; draft remains open at its received head. No new root-routing selection.
Website #16	#19, 11f144e6d5d28f74b641dec13b034f0f1a85f320, integrates static metadata/identity.	Included in accepted Run 260930000000012 at ecb120bc11b8bfedd20a24b94e03943fc2e039d6 and retained in accepted Guide Run 260930000000014 at 6e70166d08c8b643aef6ca3620bcf4579cab8f7a; see the roadmap's immutable intent/outcome links.	No Google completion established.	Google follow-up and checklist return; draft remains open at its received head. No duplicate metadata build or publication.
Agent plugin #1	Foundation integration 4df68505 (2026-10-14); later public reader 903f70c6.	Public-reader installation and actual native Codex/ZCode read proofs complete.	Not applicable.	Original authenticated original-object transfer remains open, including binary objects, original IDs, atomic expected-head update, replay/uncertainty recovery and exact PR readback. Reader proof is not write proof.
Laboratory #122	Original documentation proposal retained at e50762a47e1742cd4b5e06b554a89b46c143ce08; read-only implementation in Core db1f8b91af0fe1663ba21c7c7dd929d391f5a9f2.	Production accepted 2026-10-18 at 00:50 UTC; the first ordinary native Actions binding was observed at 01:08–01:09 UTC and accepted at 01:15 UTC.	Not applicable.	Guarded rerun remains a later stage with its own server-side contract and acceptance cases. Reconcile the original WIP separately; read-only delivery does not close all original criteria.

The original PR119/120/16/122 metadata was read again on 2026-10-17; their open/WIP state does not undo delivery through later protected changes. The plugin foundation disposition comes from retained integration evidence; an anonymous 404 for its private PR proves no status. Public catalog submission and universal client/authenticated-write acceptance are not claimed.

Shipped project foundations and next proof

The Guide, public project path/brief and continuation Composer are shipped; the roadmap binds their source, accepted Run12 and real export proof. A fresh public-only agent completed its permitted continuation inspection on 2026-10-17 against the immutable authored handoff and candidate 297e240895027a52c96a9a640fd6851cfb7af165. This bounded agent trial correctly separated accepted/proposed work and resumed the single authorized inspection; it establishes no human usability result.

Guide clarification website #29 then completed source acceptance and protected integration at 6e70166d08c8b643aef6ca3620bcf4579cab8f7a, with the same native tree as reviewed head e6e83b56cad920c666a278214e9e84b1ccdc4633. That later corrected source was outside the earlier trial. The immutable Composer exports retain their historical Proposed status. Publication Run 260930000000014, attempt 1, rebuilt source 6e70166d08c8b643aef6ca3620bcf4579cab8f7a and was accepted on 2026-10-18 at 02:07 UTC, generation 93. The roadmap binds its immutable intent/outcome ledger and origin/public-file checks. Admission closed at 02:02:58 UTC, with rollback retained and not exercised. The desktop keyboard path Connect → Guide → brief was accepted live; no live mobile measurement or human usability study is claimed.

Native read-only Actions explanation is accepted separately. New native statuses carry an explicit trusted job/attempt association; explanation validates repository/source agreement and exposes the full source SHA, run/job/attempt, trigger and observation time. Legacy unbound statuses remain Unknown; context and target URL alone are insufficient. Reads and refresh enqueue nothing, and a related manual success cannot replace a failed required push check. This does not accept the later guarded-rerun contract.

Historical received revisions — 2026-10-11

PR metadata and every changed file were retrieved on 2026-10-11. All five PRs were open; the three SEO proposals and Laboratory #122 were drafts. File identities were checked against the retained intake receipts. This establishes which inputs were received, not an independent implementation or runtime review. PR heads can change; reconcile a fresh exact revision before implementation.

Contribution	Received head	Target and received base	Handoff at that head
Laboratory #119	421be683395c0232dbbd57a642af70a12e297934	main at bcabdd38fb15f79fc3e0170384f787b7f485ca4b	Canonical and reference corrections
Laboratory #120	cf86b8cde7ab2d8935c70ea1e93e8f24b28e1c20	main at bcabdd38fb15f79fc3e0170384f787b7f485ca4b	Public profile and Laboratory identity
Website #16	04e4688cadc80ba4f46956a4d6bb364abbdcb142	main at a7dc9410f6a7f954bc583b45ea4d0cb709b05367	Static page and organization metadata
Agent plugin #1	7b3ad4a794ef226797092c0f9128886b5425ace7	oss-oo/plugin-foundation-40cf522579cc at c002a7e1b204bd66e0ad2a59faaebb96556873db	Personal handoff, requirements, foundation reconciliation
Laboratory #122	e50762a47e1742cd4b5e06b554a89b46c143ce08	main at eec894206eb5c6c8f8d1bbca20d5b805b4173302	Actions check diagnostics and guarded reruns

The plugin PR contributes three documents to the existing foundation branch. Its historical ancestry on an older main is not its current target. The foundation reconciliation report explicitly labels an earlier two-document review; that historical result must not be presented as validation of the later three-document head.

Original requirements (received 2026-10-11)

Sections 1–5 preserve the received proposals and acceptance criteria. Current delivery is recorded above; future-tense text here is historical, not an open implementation instruction for delivered SEO corrections.

1. Canonicals and imported references — Laboratory #119

This draft contains documentation and two inert patches. Plan these outcomes:

• Give /about/ one self-canonical and matching og:url.
• Give only the exact clean repository-index response a canonical for /explore/repos. Adapt the proposed ingress rule to the accepted serving component. Its intended scope is GET/HEAD, exact original URI and a successful HTML response; queries, pagination, aliases, other methods and other response types must not inherit it.
• Inspect the actual import/reference configuration for the four generated Cinnamon issue links ending in 9037, 8541, 8006 and 8244. The handoff records actual upstream counterparts. Correct the mapping only after confirming the repository's policy and current behavior; retain truthful 404s until a resource or deliberate mapping exists.

Preserve anonymous-root routing, the signed-in dashboard, /about slash normalization, the working issue-to-PR alias, native sitemaps and deliberate robots exclusions. Do not introduce blanket redirects, rewrite imported history or manufacture local issues. The second patch expects the first patch's runbook addition; apply or adapt each proposal once.

The handoff reports successful source/applicability checks, but the ingress candidate still needs full configuration validation, positive and negative response tests, and the mandatory isolated e2e gate before committing any runtime changes under the repository's gated paths. Publication must prove the actual active configuration and public bytes/headers.

2. Public profiles and operator identity — Laboratory #120

Reconcile the proposed head override against the exact target Forgejo fork and preserve its upstream provenance, license and stock hooks. The source candidate targets the exact native home of a public account: visible display name and username in metadata, one absolute canonical, and safely serialized ProfilePage data only where the native account type supports it.

Private, limited, ghost, admin, repository and query/tab contexts retain their stock behavior. Bots and individual-typed infrastructure accounts must not receive an invented Person identity. Maintain the service-account exception inventory. No email, biography, location, membership, external account linkage or avatar is added to structured data; existing visibility and crawler rules remain authoritative.

The landing proposal describes the Laboratory WebSite separately from its OSS Singularity operator. Coordinate its publisher with the stable https://oss-singularity.io/#organization identifier in website #16. Keep the sites' WebSite identities distinct and their visible content unchanged. PR #120 does not include either canonical patch from #119.

The recorded Go rendering, escaping and privacy fixtures are preparation evidence, not a running-image acceptance. Review the full target template, run native CI and isolated e2e, and verify anonymous public profiles plus restricted and non-target contexts before publication. Resolve the root/landing and signed-in dashboard behavior explicitly: markup on /about/ alone does not establish the domain-root site-name requirement. Do not invent language URLs or hreflang variants for a cookie-only locale.

3. Static page metadata — website #16

In the website repository, extend the existing WebSite/Organization aliases and describe the root plus eleven generated canonical hub pages with their actual metadata, language, URL and shared publisher. Preserve the existing stable entity identifiers, verified organization profile reference and visible bodies. The 404 retains its separate behavior and receives no fabricated entity.

The existing renderer/checker changes belong to that repository. Reconcile them against its eventual deployment branch, rerun its current repository and complete native CI gates, independently review, then use the accepted publication controller. Verify public root and representative hub responses, unique static JSON-LD, existing canonicals and the real 404. This does not activate Commons, authentication, QA or other product features.

4. Cloud contributions — agent-plugin #1

Extend the existing foundation and its service, Connect/Identity, OAuth, account-isolation, safe-tool, permission and evidence contracts. Reconcile its pinned gateway audit with the actual migrated service. No second authentication platform or shared owner credential is selected by this requirement.

The additional acceptance case is a fresh supported Cloud session reusing an accepted account connection to transfer its existing Git objects, including a binary asset, preserving original commit IDs through a verified remote update and PR. Bind the plan to repository, artifact contents, original commits, refs and expected prior remote head. Update the ref atomically only when that head still matches, read back the result and verify the PR's repository/head/base/identity. Reconcile partial success, replay and lost responses against actual remote state; a PR-creation API alone transfers no Git objects, and recreated commits do not satisfy original-ID preservation.

Add successful-transfer and permission/account/branch mismatch, malformed artifact, stale-head, replay and partial-result cases to the existing integration acceptance contract. Repository creation is outside this added case. Keep secrets out of chat, packages, logs and artifacts. A previously successful external terminal push and offline package tests establish neither OAuth nor a live plugin connection.

Package/skills/client scenarios stay in agent-plugin; gateway and transfer implementation stay with their confirmed server/identity owner. Internal trials use the new PVE infrastructure: Codex first, with separate evidence for ChatGPT and ZCode after actual client-capability verification; see the access-validation requirement. Public catalog submission follows validated live use and is not authorized now. The separate OSS Singularity plugin follows experience with this first plugin and its own product roadmap.

5. Actions check diagnostics and guarded reruns — Laboratory #122

This open draft adds four documents (397 additions), including a specification, 34 proposed acceptance scenarios and sanitized incident evidence. It contains no feature implementation. The motivating incident is resolved; that result does not establish acceptance of this proposed feature.

Deliver read-only explanation first: identify the authoritative native run/job/attempt, trigger and source, distinguish related executions, and keep native execution, commit status, current required-check policy and publication observations separate. A later manual success cannot replace a failed push check or satisfy a required gate. Ambiguous evidence remains unknown; a status mismatch never triggers automatic republishing or a fabricated green status.

An optional second stage may offer an explicitly reviewed native rerun only after its server-side contract is implemented. Bind original source/event, repository/run/job identity and expected attempt; preserve native permissions, CSRF and approvals. Review whole-job repetition, dependent-job cancellation and invalidation of all run artifacts. Require an atomic expected-attempt transition, a durable operation receipt and read-only recovery after uncertain responses. HTTP 204 proves acceptance, not completion. Page navigation, refreshes and polling never enqueue work.

Resolve three questions against the migration's exact source pin before coding: the trusted status-to-job association and ambiguous legacy records; native metadata or a reviewed profile for source/environment binding; and the atomic rerun transaction, receipt and recovery boundary. The current bodyless native endpoint does not supply the proposed concurrency or idempotency contract.

Implementation belongs in the Laboratory's reviewed application source and own lineage, not ingress rules or browser scripts. Recheck the observed source contracts if the selected pin changes. Any upstream submission needs a separate owner decision. Keep source review, CI, deployment and live acceptance as separate gates. The 34 scenarios have not run: require classifier/identity fixtures, concurrency and recovery integration, harmless native Actions tests in an isolated repository, browser/API checks against the pinned application, and the repository gates applicable to changed paths.

6. Access validation and ZCode — owner request, 2026-10-13

The owner required implementation immediately after initial cutover. The access-validation plan maps current source coverage and gaps, then requires credential-free PR checks, authenticated synthetic tests on release VM1005 and exact-release pre/postpublication real-route proof. Cover SSH/HTTPS Git object reads and authorized disposable writes, REST, MCP tools/auth negatives, real clients, MQTT, browser/session/MFA, join/console and LFS/registry where used. Health 200 or unavailable/skipped cases do not count as working access; current migration manual proofs remain required.

Verify actual Codex/ChatGPT/ZCode transport and authentication capabilities before extending agent-plugin with the ZCode adapter. Reuse the foundation's gateway, Connect/Identity, scoped permission and account-isolation contracts; no second server, shared owner key or public submission is selected. This owner requirement preserves all five received PRs and their acceptance work. Implementation and dated coverage now exist in ACCESS-VALIDATION-IMPLEMENTATION and ACCESS-VALIDATION-ROUTES. Native public-reader proofs are delivered; remaining exact-release routes, authenticated transfer and unsupported-client cases retain their own acceptance boundaries.

Current order and completion evidence — 2026-10-18

1. Use the accepted PVE cutover and subsequent deliveries as the baseline; retain their recovery/retirement limits. Do not schedule migration again or infer that all historical rollout boxes are now individually closed.
2. Draft the next human non-software product experiment. Guide source, publication/current public-route acceptance and the bounded public-only agent continuation trial are complete; preserve the trial's original artifacts and human-usability limit. Native read-only Actions explanation is accepted; original #122 criteria remain for traceability, and guarded rerun is a separate later contract with its own acceptance.
3. Before any Google action inspect existing requests/validations, including the /about redirect validation reported started on 2026-10-10. Run appropriate post-deployment Live Tests and preserve any submission and later stored-crawl/canonical/indexing decisions separately. Unchanged sitemap URLs do not need duplicate submission; promise no rank or site name.
4. Extend the plugin's existing foundation for connected original-object transfer. Public reading, supported-client activation, authenticated writes and later catalog submission are different acceptance gates.
5. Reconcile the original Cloud handoff checklists and return the exact delivered source/live evidence through authorized coordination before changing their historical WIP state. Source correction and publication alone do not close Google's follow-up.

Original author reports remain dated evidence for those original heads. Accepted later deliveries are identified above; this documentation update runs no candidate runtime tests, merges no original handoff PR and changes no live configuration, DNS, Google state or plugin activation.