Add Pro tier: README ladder + open-core boundary rule - #44
Conversation
|
🤖 Babysit-PRs — 2026-06-13 CI: ✅ green (checks + shellcheck: success) · review comments: none · merge state: ✅ clean. No action taken — ready to merge whenever you are. Generated by Claude Code |
|
🤖 Babysit-PRs — 2026-06-17
Generated by Claude Code |
|
🤖 Babysit-PRs — 2026-06-26
No action needed. Ready for Edwin's review/merge. Generated by Claude Code |
|
🤖 Babysit-PRs — 2026-06-29
No action needed. Launch dependency still outstanding: needs LangOptima-General #218 (Pro tier README / Generated by Claude Code |
|
🤖 Babysit-PRs — 2026-07-11
No action needed — still the one PR of the six actually ready to ship. Launch dependency unchanged: still needs Generated by Claude Code |
|
🤖 Babysit-PRs — 2026-07-12
So the repo-side dependency has been resolved for a month. What's still unconfirmed is deploy, not merge: I tried fetching No action taken on this PR itself — still CI-green/clean/ready. Recommend Edwin do a 10-second manual check of the live URL; if it resolves, this PR has nothing left blocking it. Generated by Claude Code |
|
🤖 Babysit-PRs — 2026-07-15
No action taken — still ready to merge. Re-checked the launch dependency noted on 07-12: Generated by Claude Code |
|
🤖 Babysit-PRs — 2026-07-19
No action taken — still ready to merge. Re-checked the launch dependency: Generated by Claude Code |
|
🤖 Babysit-PRs — 2026-07-20
No code action taken — still the one PR of the batch actually ready to ship. Re-checked the external launch dependency: Generated by Claude Code |
|
🤖 Babysit-PRs — 2026-07-27
No action taken. External launch dependency unchanged — already escalated on 07-20, not re-litigating the same signal: Generated by Claude Code |
|
🤖 Babysit-PRs — 2026-07-28
No action taken. External launch dependency unchanged: Generated by Claude Code |
|
🤖 Babysit-PRs — 2026-08-03
No action taken. External launch dependency unchanged — re-checked this run: Generated by Claude Code |
|
🤖 Babysit-PRs — 2026-08-11
No action taken. Per this PR's own stale-signal escalation rule (invoked 07-20), not re-checking the Generated by Claude Code |
|
🤖 Babysit-PRs — 2026-08-17
No action taken. Per this PR's own stale-signal escalation rule (invoked 07-20), not re-checking the Generated by Claude Code |
|
🤖 Babysit-PRs — 2026-08-20
No action taken. Per this PR's own stale-signal escalation rule (invoked 07-20), not re-checking the Generated by Claude Code |
|
🤖 Babysit-PRs — 2026-08-22
No action taken. Per this PR's own stale-signal escalation rule (invoked 07-20), not re-checking the Generated by Claude Code |
|
🤖 Babysit-PRs — 2026-08-24
No action taken. Still waiting on the two Edwin-owned items: a manual browser check of Generated by Claude Code |
Summary
.claude/rules/open-core-boundary.md— every addition to this repo passes the free-vs-Pro check before merging. Merging here is a one-way door (MIT, public forever); four tests decide the default (pattern vs. playbook, tool-agnostic vs. named-tool wiring, one operator vs. team rollout, demo vs. customer's Monday); unsure → Pro first. Community PRs always land here under MIT with credit — never behind the paywall.CLAUDE.md(loads every session), the rules index,CONTRIBUTING.md, and the CHANGELOG.Launch coupling — merge order
Test plan
CLAUDE.mdrules list,.claude/rules/README.mdtable, and CONTRIBUTING all point to the rulehttps://claude.ai/code/session_01HdP5UkzUEKTTzt2Rypcj7z