chore: weekly profile refresh

[Oba-One]

Weekly refresh of the three auto-managed marker blocks in profile/README.md for 2026-W31. Nothing outside the markers changed.

Sources and window

Block	Source	Window
now-building	Linear initiatives + projects, workspace-wide	active / moved in last 14 days (since 2026-07-13)
recently-shipped	GitHub releases + merged PRs on shipping branches	last 7 days (since 2026-07-20)
team-shipping	Linear, all five teams	moved in last 14 days

What changed

Now building — reordered so the two threads with the most movement lead. Dropped the "v1.2.0 shipped in July" clause from the Green Goods line (it belongs in Recently shipped, and it has now aged out of that window). Commitment Pooling moves up and gains its current state: the scope-and-design work closed on 2026-07-25 and operator onboarding for the first dry run is in progress.

Recently shipped — this is the substantive change, and it is thinner than usual because the week genuinely was:

• green-goods — no release, and no merges to main. Its last main merge was the v1.2.0 release PR on 2026-07-08. The 16 PRs merged this week all landed on develop (pre-v1.3.0), so per the shipping-branch rule they are not counted as shipped.
• network-website — no releases, and no merges at all in the window; its last merge was 2026-07-18.
• .github — two PRs merged to main (guild-weekly-synthesis: restrict public events to Community Sync + Builder Spaces #50 on 07-21, docs(routines): move guild routines to Claude Opus 5 / Fable 5 #51 on 07-27). The only shipping-branch merges this week, so the only bullet.

I added one plain sentence after the bullet stating there were no product releases this week and pointing at v1.2.0 as the current release, so the section is not read as "nothing is happening." Flagging it for your call: if you would rather the section carry only repo bullets, drop that sentence.

What each team is shipping — all five teams moved. Each line now pairs the current focus with a completion I could see in Linear: Product's maturation push (closed 07-16), Research's commitment-pooling scenario pack and external brief (07-25), Community's garden survey (07-25), Marketing's onboarding video batch and end-to-end walkthrough (07-22). Growth gains the Artizen Season 7 raise alongside Octant Epoch 12 — both public campaigns; no amounts, prospects, or unannounced partners.

Notes

• Two source quirks worth recording: network-website now resolves to greenpill-dev-guild/network (renamed), which makes repo:greenpill-dev-guild/network-website searches fail with a 422 rather than return empty — worth knowing before anyone reads a future empty result as "no activity." And the search API's merged field was unreliable here; merge state was taken from merged_at.
• Outside the markers, so untouched: the repo's relative-link check fails on a pre-existing broken link in routines/claude/guild-grant-scout.md ([...](url), a placeholder). Unrelated to this change.

Privacy pass: no issue IDs, no private status-update content, no funder or partner names that are not already public, no amounts.

🤖 Generated with Claude Code

https://claude.ai/code/session_01GQ81759DmZabNADxrUijYn

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

@Oba-One, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 50 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 60e5c99b-16f8-4714-a8d9-7950d6c622aa

📥 Commits

Reviewing files that changed from the base of the PR and between 0863fe2 and c86ce01.

📒 Files selected for processing (1)

• profile/README.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

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

---

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