docs: retire Proof of Ship, Celo Public Goods and Regional DAOs; rename Foundation to Celo Core Co

[GigaHierz]

The hole, and the fix

The Contribute section pointed readers at programs that no longer run, under an
organisation name that has changed, on an events platform we no longer use.

• Regional DAOs page deleted. contribute-to-celo/daos.mdx (91 lines) is gone.
  Added /contribute-to-celo/daos → /contribute-to-celo, and repointed the two
  redirects that previously landed on it (/blog/2022/05/10/Getting started with DAOs on Celo, /what-is-celo/joining-celo/daos) so nothing chains through a
  redirect to a deleted page.
• Proof of Ship removed — 9 references across 7 files. It is sunset, so every
  mention goes, including the img/building/ecosystem-grants.png embed, whose
  diagram plots "Proof of Ship" as the entry-stage rung of the funding ladder.
• Celo Public Goods removed — the celopg.eco links plus the
  ### Mechanisms for Celo Public Goods Proposals section and the
  Celo Public Goods Governance row in the proposal-types table.
• Celo Foundation → Celo Core Co in prose. URLs are left alone, including the
  LinkedIn slug /company/celo-foundation, which is a live external link.
• Events moved to Luma. All 5 lemonade.social/s/celogovernance links now
  point at the Celo Luma profile. Labels that read "Governance Events" became
  "Events" / "Celo Events" — the Luma profile is Celo's general events page, not
  a governance-only space.
• Celo Developers newsletter added in 3 places where builder updates are
  offered: the Builders page, Joining Celo's "As a Builder" list, and the footer.

Also removes five stale bullets from contribute-to-celo/index.mdx: ecosystem-database
registration, both "local chapter" links (they pointed at the deleted page), and the
Celo Signal signup.

What this does NOT do / residual risk

• img/building/ecosystem-grants.png is now referenced by 0 pages. I removed the
  embed rather than ship a diagram advertising a sunset program. The file is still on
  disk. It also labels a "Celo Builder Fund" that appears nowhere in the page text, so
  it had already drifted. It needs a redraw, not just a re-link.
• build-on-celo/fund-your-project.mdx is now thin — 2 programs (Prezenti, Verda
  Ventures) plus a newsletter link. Proof of Ship was the only item under
  ## From Idea to MVP to your first users, so that section went with it.
• The Celo Public Goods Snapshot mechanism (snapshot.org/#/celopg.eth) is no longer
  documented anywhere in this repo. If that Snapshot space is still live, this removes
  the docs' only record of how program-selection votes work. Confirmed in scope; calling
  it out because it is the one deletion here with a factual, not promotional, cost.
• Celo Signal is untouched outside the Contribute index — 6 references remain on the
  governance and staking pages. Out of scope for this pass.
• 4 links to embeds.beehiiv.com/eeadfef4-… are untouched (support.mdx,
  fund-your-project.mdx, home/celo.mdx, snippets/home.jsx). That is a different mailing
  list from celo-devs.beehiiv.com; confirmed before leaving them. They are opaque
  iframe-embed URLs labelled three different ways ("DevDesk Mailing List", "Join the
  Newsletter", "joining our newsletter") — worth normalising in a separate pass.
• snippets/home.jsx is dead code — imported by 0 files, and its internal links still
  point at retired /about-celo/** paths. Updated here only to keep it consistent with
  home/celo.mdx, which it duplicates. Deleting it would end the double maintenance.
• Orphan-page count is unchanged at 20 (measured both sides, below). Those are docs: resolve the 20 orphaned pages — 10 re-nav'd, 10 deleted with redirects (#2253) #2293's.

Judgement calls

1. Removed the funding-ladder image instead of keeping it. It is a raster file I cannot
   edit and it renders the sunset program name. Reversal cost: one line to re-add the embed.
2. Reworded the Fund-your-project intro. It claimed "a strong focus on retroactive
   funding, rewarding impactful contributions after they've been made" — Proof of Ship was
   that retroactive mechanism. The remaining programs are forward-looking, so the sentence
   was left false by the removal. Now: "a variety of funding mechanisms — grants, funds, and
   sustainable revenue models — to support projects at different stages." Reversal: one sentence.
3. Reworded the Celo Community Treasury row in the proposal-types table. It defined itself
   against the now-undocumented budget ("proposals that do not fall within a current Celo
   Public Good Budget or aim to request over $500,000"). Now: "Funding proposals requesting
   over $500,000 in value in a single proposal." This narrows a governance definition — worth
   a governance-side check before merge. Reversal: one table cell.
4. Relabelled "Governance Events" → "Events" / "Celo Events". The new Luma profile is not
   governance-scoped, so keeping the old label would have mislabelled the destination.
   Reversal: three strings.
5. Deleted the emptied ## From Idea to MVP to your first users heading rather than leaving
   a heading with no content.

Bundled product change: the newsletter addition (3 spots) is additive and independent of the
removals — happy to drop it; the cleanup stands without it.

Issues

Closes: none — this does not satisfy any acceptance box of an open issue.
Refs #2261 — adjacent only. That story renames contribute-to-celo/* → contribute/*; this
PR edits files inside that directory but does no restructuring. See conflicts below.

Stacking / conflicts

Branched off origin/main, 0 commits behind, independent of my other open PRs.

• Content files: zero overlap with any open PR. docs: resolve the 20 orphaned pages — 10 re-nav'd, 10 deleted with redirects (#2253) #2293 is the only open PR touching
  build-on-celo/**, and it touches index.mdx, support.mdx, build-with-usat.mdx,
  build-on-socialconnect.mdx — none of which this PR modifies.
• docs.json is shared with all 5 open PRs (feat(seo): set the brand Organization entity via Mintlify's native seo.organization #2285, docs: resolve the 20 orphaned pages — 10 re-nav'd, 10 deleted with redirects (#2253) #2293, feat(docs): add an "Edit on GitHub" entry to the page context menu #2297, docs(redirects): add 33 verified redirects for pre-migration URLs still 404ing #2299, feat(analytics): route GA4 through GTM and instrument engagement events #2300) because it
  holds nav, redirects, theme and footer for the whole site. The edits here are in three
  distinct regions — the Contribute nav group, three redirect entries, and the footer socials
  list. docs: resolve the 20 orphaned pages — 10 re-nav'd, 10 deleted with redirects (#2253) #2293 and docs(redirects): add 33 verified redirects for pre-migration URLs still 404ing #2299 both append to the redirects array, so expect a textual conflict there
  and a trivial resolution (keep both sides). Suggested order: land the redirect-heavy PRs
  (docs: resolve the 20 orphaned pages — 10 re-nav'd, 10 deleted with redirects (#2253) #2293, docs(redirects): add 33 verified redirects for pre-migration URLs still 404ing #2299) first, then rebase this one.
• story: Homepage, Contribute rename, and an "AI resources" page — final pass #2261 will move contribute-to-celo/* → contribute/*. Land this first; it is a
  content diff and will be carried by the move. Landing story: Homepage, Contribute rename, and an "AI resources" page — final pass #2261 first turns this into a
  path-conflict cleanup for no benefit.

Verification evidence

Run on this head (67b4807f), not CI's cache.

$ git diff origin/main...HEAD --stat | tail -1
 16 files changed, 34 insertions(+), 148 deletions(-)

$ mint broken-links
success no broken links found

$ bash scripts/check-orphans.sh | grep -c '^[a-z]'      # this head
20
$ (cd <worktree of origin/main> && bash scripts/check-orphans.sh | grep -c '^[a-z]')
20                                                       # unchanged — adds no orphans

Removal is complete, by grep rather than by the link checker (see the mutation result below):

$ grep -rni "proof.of.ship|proofofship" --include=*.mdx --include=*.jsx --include=*.json .
(none)
$ grep -rniE "celopg|lemonade\.social|Celo Foundation" --include=*.mdx --include=*.jsx --include=*.json .
(none)
$ grep -rn "contribute-to-celo/daos" .
docs.json:583:      "source": "/contribute-to-celo/daos",     # the redirect source — intended

Mutation results — 2 mutations, and the first one matters:

Mutation	Expected	Actual
1. Re-add an inbound link to the deleted /contribute-to-celo/daos in home/index.mdx	red	green — 0 broken links
2. Add a link to /contribute-to-celo/daos-does-not-exist (no page, no redirect)	red	red — found 1 broken links in 1 files

Mutation 1 going green is not a checker bug — mint broken-links resolves redirects, and the
redirect added in this PR makes that link legitimately non-broken. The consequence is that a
green broken-links run does NOT prove the inbound links to the deleted page were removed.
That property is proven by the grep above instead. Mutation 2 confirms the checker still has
teeth for genuinely dangling links, so the green run is worth something — just not that.

External links checked with a browser UA (beehiiv 403s plain curl):

https://luma.com/user/usr-QJkvU5EML2BJeYc              200
https://celo-devs.beehiiv.com/subscribe                200  <title>Subscribe | Celo Developers</title>

Rendered surfaces clicked through on mint dev: /contribute-to-celo, /contribute-to-celo/builders,
/home, /home/protocol/governance/overview (table renders with 4 rows), /home/protocol/governance/governance-toolkit,
/build-on-celo/fund-your-project, footer.

Remaining ops steps

• Redraw img/building/ecosystem-grants.png without Proof of Ship (and reconcile the
  "Celo Builder Fund" label with the page text), then re-embed it — or delete the file.
• Confirm the Celo Public Goods Snapshot space is genuinely retired; if it is still live,
  its voting mechanism now has no home in the docs.
• Decide whether to delete the unreferenced snippets/home.jsx.

Checklist

• Title is the commit message I want on main
• Covers the seam this touches (the link graph) — mutation-tested, result reported above
• Judgement calls / bundled product changes flagged above
• mint broken-links + orphan check pass locally on the current head
• README / AGENTS.md / examples checked for drift — no references to the removed programs
• No secrets in the diff
• One concern per PR — NOT met. See the question below.

Questions for the maintainer

1. This bundles six concerns (DAOs page, Proof of Ship, Celo Public Goods, the org rename,
   the events swap, the newsletter addition) and the repo rule is one per PR. They were done as
   one pass because they overlap heavily in the same files —
   contribute-to-celo/index.mdx is touched by four of the six, so splitting produces PRs that
   conflict with each other rather than merging cleanly. Happy to split into
   removals / rename / events+newsletter if you would rather review them separately.
2. Judgement call 3 narrows a governance definition in the proposal-types table. Worth a
   second pair of eyes from someone closer to governance before this merges.