chore: weekly profile refresh

[Oba-One]

Weekly refresh of the two auto-managed sections of profile/README.md. Only the content inside the now-building and recently-shipped marker blocks changed; the rest of the file is byte-identical. A human merges.

Now building (source: Linear — Product + Research, In Progress / moved in the last ~14 days)

• Green Goods: reworded to reflect the active protocol-hardening + polish push (QA/release hardening + Public Website & Docs Polish projects In Progress) and the move to a monthly release cadence.
• PGSP: updated from "relaunching the Genesis validator squad" to the operator-first re-pace (re-paced 2026-06-19) — node setup now, Genesis squad relaunch + first operator cohort next.
• Greenpill Network website: new bullet — the Website Polish & Steward Onboarding project is In Progress under the Network Presence initiative.
• Impact Framework: new bullet — Impact Framework v0.1 Refresh (Research) is In Progress.
• Removed NYC Vault Crowdfunding — the Linear project was marked Completed on 2026-06-29, so it no longer belongs in "now building."

Recently shipped (source: GitHub — last 7 days, 2026-06-22 → 06-29)

• green-goods is the only repo with merges in the window: a USD/wETH toggle on the /fund flow, a full-screen admin Submit Work flow, hardened vault crowdfunding, and time-boxed media uploads. Replaces the old static "see releases" placeholder (there are no tagged releases yet; first cadenced release is July).

Gaps / notes

• No tagged releases exist on any repo, so the shipped bullet summarizes merged PRs.
• coop (last merge 2026-06-19), network-website (last merge 2026-06-17): nothing merged in the 7-day window, so they're omitted per the skip-empty rule.
• cookie-jar: the GitHub PR-list endpoint returned 404 (no accessible PRs); nothing to report this week.
• green-goods merges land on develop; wording says "merged" rather than "deployed" since the first production release is scheduled for July.

Public-safe: no internal issue IDs, no private status-update content, no non-public partner/funder names. No growth-hacking vocabulary.

🤖 Generated with Claude Code

https://claude.ai/code/session_01J1nqUMKVKbyZAL1z99jWsH

---

Generated by Claude Code

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: fec462d1-8f03-4340-aa00-1b8afd57306b

📥 Commits

Reviewing files that changed from the base of the PR and between 4e75662 and 1fb6b6d.

📒 Files selected for processing (1)

• profile/README.md

📜 Recent review details

⏰ Context from checks skipped due to timeout. (2)

• GitHub Check: Analyze (javascript-typescript)
• GitHub Check: Analyze (actions)

🧰 Additional context used

📓 Path-based instructions (4)

profile/README.md

📄 CodeRabbit inference engine (CLAUDE.md)

Use absolute GitHub URLs in profile/README.md for links back into this repo

Files:

• profile/README.md

**/*.md

📄 CodeRabbit inference engine (CLAUDE.md)

Link to the issue-creation flow in docs that ask someone to "open" an issue or RFC, not just the source template file

**/*.md: Do not introduce guild-wide Season framing in documentation
Do not describe the dev guild as the entire Greenpill Network in documentation
Avoid growth-hacking and trend-chasing voice in documentation: no FOMO, virality, leaderboards, streaks, or AI-first framing

Files:

• profile/README.md

**/*.{md,yml,yaml}

📄 CodeRabbit inference engine (CLAUDE.md)

Search for and retire stale terms: app.charmverse.io, greenpill.network/dev-guild, FOMO, virality, leaderboards, streaks, AI-first, former dev-guild PM URL, retired funded-work file names, old GitHub grant lifecycle labels, and retired Claude routine filenames

Do not reintroduce the former dev-guild PM URL or old migration language for project-management state

Files:

• profile/README.md

{CONTRIBUTING.md,GOVERNANCE.md,SECURITY.md,SUPPORT.md,profile/README.md,.github/ISSUE_TEMPLATE/**,.github/PULL_REQUEST_TEMPLATE.md}

📄 CodeRabbit inference engine (AGENTS.md)

Treat contact emails, disclosure SLAs, payout timing, and governance claims as sensitive public commitments and do not change them casually

Files:

• profile/README.md

🔇 Additional comments (2)

profile/README.md (2)

27-31: LGTM!

---

36-36: LGTM!

---

📝 Walkthrough

Summary by CodeRabbit

• Documentation
  • Updated the profile README with refreshed project status items in the “Now building” section.
  • Added a new “Recently shipped” entry for Green Goods, highlighting recent release-hardening improvements and workflow updates.
  • Kept the existing Green Goods release link for continued access to release details.

Walkthrough

Updates profile/README.md: replaces three "Now building" bullets with four updated entries, and adds a "Recently shipped" bullet for green-goods with a PR search link and release-hardening details.

Changes

README Status Update

Layer / File(s)	Summary
Now building and Recently shipped updates profile/README.md	Replaces prior Now building bullets with entries for Green Goods, PGSP, Greenpill Network website, and Impact Framework; adds a green-goods Recently shipped bullet with a PR link and release details.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A rabbit hops through the README with glee,
Swapping old bullets for what's soon to be!
Green Goods hardens, PGSP takes flight,
Greenpill and Impact shine ever so bright.
The warren's roadmap — updated just right! 🐇✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title is related to the change, but "weekly profile refresh" is generic and not specific enough.	Use a more descriptive title that names the main updated sections or key content changes in profile/README.md.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description matches the README section refresh and accurately summarizes the content changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch profile-refresh/2026-W27

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}