OSS-OO/laboratory
OSS-OO/laboratory
Watch
5
0
Fork
You've already forked laboratory
 0
Code Issues 7 Pull requests 5 Projects Releases Packages Wiki Activity Actions

WIP: public profile and laboratory identity — MAMA Astra handoff #120

Draft
ClaudiuSchuster wants to merge 1 commit from oss-oo/public-identity-20261010 into main
pull from: oss-oo/public-identity-20261010
merge into: OSS-OO:main
Conversation 1 Commits 1 Files changed 10 +1637 -3
ClaudiuSchuster commented 2026-10-10 21:02:06 +00:00
Owner

Public member profiles are reachable and discoverable, but the fresh Google Live Test on 2026-10-10 22:43:36 MESZ still finds no declared canonical. Their generic description also omits the public username. This draft gives MAMA Astra a bounded source candidate to carry into the infrastructure migration.

Changes

  • Add a head override based on the exact pinned Forgejo source. Only an exact, public profile home receives display name plus username in its title/description and a native absolute canonical.
  • Add safely encoded ProfilePage JSON-LD for the relevant native person or organization type. Bots and the three documented individual-typed infrastructure accounts receive no invented Person identity. Private/limited profiles, admin/repository pages and query/tab variants retain stock output.
  • Add one landing WebSite/operator graph with truthful OSS-OO aliases and the shared OSS Singularity organization ID. Visible landing content remains byte-identical.
  • Add Go rendering/privacy/escaping fixtures to CI, preserve upstream template provenance/license, and record GSC evidence plus the migration acceptance steps.

Validation completed

  • Go html/template tests: 3 groups, 22 subcases passed, including script-termination payloads, private-field sentinels, type exceptions and unchanged stock contexts.
  • Independent runtime/source review passed after the service-account exclusions.
  • Landing bytes outside the one new JSON-LD script and the head body scaffold match the base exactly; git diff whitespace check passed.
  • Both canonical attachments from PR #119 still apply cleanly in sequence to an isolated copy. They are not duplicated in this branch.

Draft acceptance still required

Native PR CI, rendering in the actual target Forgejo image, isolated e2e, deployment and a post-deployment Google Live Test remain pending. Docker/Podman are unavailable in the preparation environment. No scripts, Compose, Caddy or agent-gateway runtime files changed; future edits in those paths require AGENTS' e2e gate before commit.

Anonymous root currently redirects to /about/ and signed-in root is the dashboard. The WebSite graph on /about/ does not establish Google's site-name root requirement. MAMA Astra should resolve root/landing behavior in the accepted migration and integrate PR #119's independent canonical proposals once. Native robots, sitemaps and account visibility remain authoritative.

Google's stored profile result remains Discovered — currently not indexed, with no regular crawl. This PR does not claim deployment, indexing or a guaranteed ranking change.

Handoff: docs/handoffs/2026-10-10-public-identity/README.md
Machine-readable evidence: docs/handoffs/2026-10-10-public-identity/evidence.json

Public member profiles are reachable and discoverable, but the fresh Google Live Test on 2026-10-10 22:43:36 MESZ still finds no declared canonical. Their generic description also omits the public username. This draft gives MAMA Astra a bounded source candidate to carry into the infrastructure migration. ## Changes - Add a head override based on the exact pinned Forgejo source. Only an exact, public profile home receives display name plus username in its title/description and a native absolute canonical. - Add safely encoded ProfilePage JSON-LD for the relevant native person or organization type. Bots and the three documented individual-typed infrastructure accounts receive no invented Person identity. Private/limited profiles, admin/repository pages and query/tab variants retain stock output. - Add one landing WebSite/operator graph with truthful OSS-OO aliases and the shared OSS Singularity organization ID. Visible landing content remains byte-identical. - Add Go rendering/privacy/escaping fixtures to CI, preserve upstream template provenance/license, and record GSC evidence plus the migration acceptance steps. ## Validation completed - Go html/template tests: 3 groups, 22 subcases passed, including script-termination payloads, private-field sentinels, type exceptions and unchanged stock contexts. - Independent runtime/source review passed after the service-account exclusions. - Landing bytes outside the one new JSON-LD script and the head body scaffold match the base exactly; git diff whitespace check passed. - Both canonical attachments from PR #119 still apply cleanly in sequence to an isolated copy. They are not duplicated in this branch. ## Draft acceptance still required Native PR CI, rendering in the actual target Forgejo image, isolated e2e, deployment and a post-deployment Google Live Test remain pending. Docker/Podman are unavailable in the preparation environment. No scripts, Compose, Caddy or agent-gateway runtime files changed; future edits in those paths require AGENTS' e2e gate before commit. Anonymous root currently redirects to /about/ and signed-in root is the dashboard. The WebSite graph on /about/ does not establish Google's site-name root requirement. MAMA Astra should resolve root/landing behavior in the accepted migration and integrate PR #119's independent canonical proposals once. Native robots, sitemaps and account visibility remain authoritative. Google's stored profile result remains Discovered — currently not indexed, with no regular crawl. This PR does not claim deployment, indexing or a guaranteed ranking change. Handoff: docs/handoffs/2026-10-10-public-identity/README.md Machine-readable evidence: docs/handoffs/2026-10-10-public-identity/evidence.json
seo: clarify public profile and laboratory identities
All checks were successful
ci / ci (pull_request) Successful in 1m11s
Details Explain this check
cf86b8cde7
ClaudiuSchuster commented 2026-10-10 21:20:27 +00:00
Author
Owner

Native CI and handoff checkpoint

The exact PR head cf86b8cde7ab2d8935c70ea1e93e8f24b28e1c20 has now passed the required native ci / ci (pull_request) gate in 1m11s: run 267. Its complete tree 78f52b8f5f6aff3b5fb10e3cded7d688ad363df8 was also fetched independently and matches the locally reviewed candidate exactly.

This PR stays a draft for MAMA Astra. Nothing from it has been merged or deployed. The pinned-image runtime acceptance, root routing/site-name decision and post-deployment Google verification remain part of the migration handoff in the repository. Existing PR #119 is linked and the combined patches were checked for clean application.

The actual profile Live Test remains healthy but currently has no declared canonical; its stored index state is “Discovered — currently not indexed”. Those observations are pre-deployment evidence, not a claim that this patch has already changed Google indexing.

## Native CI and handoff checkpoint The exact PR head `cf86b8cde7ab2d8935c70ea1e93e8f24b28e1c20` has now passed the required native `ci / ci (pull_request)` gate in **1m11s**: [run 267](https://oss-oo.io/OSS-OO/laboratory/actions/runs/267/jobs/0). Its complete tree `78f52b8f5f6aff3b5fb10e3cded7d688ad363df8` was also fetched independently and matches the locally reviewed candidate exactly. This PR stays a **draft** for MAMA Astra. Nothing from it has been merged or deployed. The pinned-image runtime acceptance, root routing/site-name decision and post-deployment Google verification remain part of the migration handoff in the repository. Existing PR #119 is linked and the combined patches were checked for clean application. The actual profile Live Test remains healthy but currently has no declared canonical; its stored index state is “Discovered — currently not indexed”. Those observations are pre-deployment evidence, not a claim that this patch has already changed Google indexing.
All checks were successful
ci / ci (pull_request) Successful in 1m11s
Required
Details Explain this check
This pull request has changes conflicting with the target branch.
  • .forgejo/workflows/ci.yml
  • forgejo-custom/templates/base/UPSTREAM-NOTICE.md
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin oss-oo/public-identity-20261010:oss-oo/public-identity-20261010
git switch oss-oo/public-identity-20261010
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
OSS-OO/laboratory!120
No description provided.