chore: weekly profile refresh

[Oba-One]

Summary

Weekly profile-refresh run for 2026-W33. Refreshes the three auto-managed marker blocks in profile/README.md — Now building, Recently shipped, and What each team is shipping — so the public org page matches what the guild is actually building and shipping.

Why

Scheduled routine (routines/claude/profile-refresh.md), Monday 20:00 UTC. Sources read directly rather than from another routine's memo.

Closes # n/a

What changed

Now building (source: Linear initiatives + active projects, workspace-wide, movement in the last 14 days — window 2026-07-27 → 2026-08-10)

• Green Goods leads: reframed from "closed July with the v1.2.1 patch" to the live state — in QA for the August v1.3.0 cut, sweeping the gardener app and the operator dashboard.
• Commitment Pooling advanced from "architecture frozen, moving to build" to contracts built and merged, with settlement review, the indexer, and the app surfaces next.
• Community Needs & Signals reordered up (the engagement model is now in progress) and PGSP moved down; PGSP wording narrowed to testnet practice.
• Greenpill Network website line now points at steward tooling, matching what actually landed this week.

Recently shipped (source: releases + merged PRs, last 7 days — window 2026-08-03 → 2026-08-10)

• Replaced last week's entries with the one repo that shipped in the window: the Greenpill Network website — the map-moderation review findings closed out, and chapter image uploads enabled for stewards. Both linked to their commits on main.
• green-goods: nothing counted this week, deliberately. The Commitment Pooling contract work (#694) merged to develop, and main — the shipping branch — has not moved since 2026-07-31. The v1.2.1 tag (2026-07-30) falls outside the 7-day window. Per the routine's cross-check, unreleased develop work is reported under Now building, not as shipped.
• Guild org repo: skipped. Its only merge in the window was last week's profile-refresh PR (chore: weekly profile refresh #55); announcing a profile refresh on the profile itself is noise.

What each team is shipping (source: the five Linear team boards, movement in the last 14 days)

• All five teams moved, so all five lines are kept and rewritten against current board state.
• Product now leads with Commitment Pooling build rather than the shipped v1.2.1 patch.
• Growth: dropped the "Octant Epoch 12 partnership" clause — no Octant movement on the Growth board in the window. The line now names only Artizen Season 7, which is already public on this page; the two other applications are referenced without naming the funders, per the routine's public-programs-only rule.

Test plan

• All three marker pairs located before editing; none missing.
• git diff confined to content inside the three marker blocks — 11 insertions, 12 deletions in profile/README.md, no marker line and no other file touched.
• Stale-term / hype-vocabulary grep over profile/README.md (FOMO, virality, leaderboard(s), streak(s), countdown, limited time, AI-first, retired PM URLs): no hits.
• Every "Recently shipped" claim traced to a commit on a public shipping branch; no claim rests on an unmerged or unreleased change.
• Both new commit links verified to resolve (the network-website path 301s to the repo's current name, matching the link style already used elsewhere in this file).

Risk and rollout

• Risk level: low — public prose only, no deploy/contracts/auth/CI paths.
• Rollout: merge as-is. One squash-merge updates the public org page.
• Backwards compatibility: n/a.

Checklist

• CI is green (format, lint, tests, build)
• Conventional Commit message
• Tests added or updated for new behavior — n/a, docs-only
• Docs updated if behavior changed
• Open-source-only dependencies
• No secrets, credentials, or .env* files committed
• If touching a high-risk path (deploy, contracts, auth, CI, security), I have requested a steward review — n/a

Notes for reviewer

• Recently shipped is one bullet this week. That is the honest read of the window, not a gap in sourcing: only one repo shipped to a shipping branch. No placeholder line was added to pad it.
• Nothing outside the markers was changed. One thing worth a maintainer's eye, left untouched per the routine's scope contract: the repo's relative-link checker in CLAUDE.md reports routines/claude/guild-grant-scout.md -> url as broken. It is a false positive — a literal [text](url) quoted inside prose at line 387, not a link — pre-existing since routines: house style v2 (quiet Discord), research-synthesis v3, grant-scout partnership lens #54. Silencing it would mean rewording that line, which is outside this PR's scope.
• Both Linear and GitHub were reachable; no section was refreshed from partial sources.

---

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 Plus

Run ID: 34b52718-b5c7-4979-a02b-fb094cc657d8

📥 Commits

Reviewing files that changed from the base of the PR and between c82a27f and de11dbd.

📒 Files selected for processing (1)

• profile/README.md

📜 Recent review details

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

• GitHub Check: Analyze (javascript-typescript)

🧰 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 (4)

profile/README.md (4)

25-30: LGTM!

---

35-36: LGTM!

---

45-45: 📐 Maintainability & Code Quality

Clarify the scope of Season Two.

If this names only the pilot-garden program, state that scope explicitly or replace it with current pilot gardens. Otherwise, remove the Season framing before merge.

As per coding guidelines: **/*.md: Do not introduce guild-wide Season framing in documentation.

Source: Coding guidelines

---

43-44: LGTM!

Also applies to: 46-47

---

📝 Walkthrough

Summary by CodeRabbit

• Documentation
  • Updated the project profile with current work, including QA, contract pooling, modeling, preparation, and website improvements.
  • Added recently shipped network moderation fixes and scoped chapter image uploads.
  • Refreshed team activity updates across Product, Research, Community, Growth, and Marketing.

Walkthrough

Updated the profile README with current project progress, recently shipped work, and team activities across Product, Research, Community, Growth, and Marketing.

Changes

Profile status refresh

Layer / File(s)	Summary
Refresh profile status content profile/README.md	Updated the current work, recently shipped work, and team status entries with Green Goods, Commitment Pooling, Needs & Signals, PGSP, website updates, and team activities.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• greenpill-dev-guild/.github#41: Updates the same profile status sections.
• greenpill-dev-guild/.github#54: Changes the profile maintenance workflow.
• greenpill-dev-guild/.github#55: Updates the same weekly profile sections.

Poem

A rabbit reviews the status bright,
Green Goods hops into sight.
Shipped work rests in tidy rows,
Team updates bloom as progress grows.
Profile refreshed—away I go!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the weekly profile refresh, which matches the main documentation changes in profile/README.md.
Description check	✅ Passed	The description accurately explains the weekly profile refresh and the three updated sections in profile/README.md.
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-W33

---

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.}