feat: lock positioning + rewrite hero around canonical-source framing#25
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughThis PR synchronizes project positioning across planning documentation and public-facing metadata. A positioning decision establishes the canonical messaging for python-docs-mcp-server as an offline Python stdlib oracle, then applies that messaging consistently to README, package metadata, and service configuration files. ChangesPositioning Update to Python Stdlib Oracle Messaging
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.planning/POSITIONING.md:
- Around line 7-14: The section starting with the heading "Use verbatim in:" and
its bullet list (the lines listing README.md hero, glama.json description,
server.json description, GitHub repo About text, LAUNCH-POST.md lede, Talk bio)
reads like an enforceable policy; change it to a historical/archival statement
instead (e.g., "Applied in README.md, glama.json, server.json, GitHub About,
LAUNCH-POST.md, and Talk bio on 2026-05-14") and remove language that prescribes
current enforcement; keep any enforcement rules out of .planning/ and ensure
live enforcement remains in the appropriate live docs/checks.
In `@glama.json`:
- Line 3: The "description" value must exactly match the locked positioning
sentence; update the JSON entry for the "description" key so its string is
replaced verbatim with: For AI coding agents writing Python the canonical Python
stdlib oracle. Exact symbols, exact sections, exact versions — offline, always
free, always MIT, token-frugal. Ensure there are no added punctuation, line
breaks, or rephrasing (do this change in the "description" field).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 9fa7c448-6aed-4e74-b98b-2aea2f2317c2
📒 Files selected for processing (5)
.planning/POSITIONING.mdREADME.mdglama.jsonpyproject.tomlserver.json
| **Use verbatim in:** | ||
|
|
||
| - `README.md` hero | ||
| - `glama.json` `description` | ||
| - `server.json` `description` | ||
| - GitHub repo `About` text | ||
| - `LAUNCH-POST.md` lede | ||
| - Talk bio |
There was a problem hiding this comment.
Avoid normative “source-of-truth” directives in .planning/.
Lines 7–14 are written as enforceable policy (“Use verbatim in”), which conflicts with the rule that .planning/ is archival history, not live truth. Rephrase this section as a historical record (e.g., “Applied in … on 2026-05-14”) and keep enforcement in live docs/checks.
As per coding guidelines, ".planning/**: Treat .planning/ directory as archival project history, not live repo truth".
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @.planning/POSITIONING.md around lines 7 - 14, The section starting with the
heading "Use verbatim in:" and its bullet list (the lines listing README.md
hero, glama.json description, server.json description, GitHub repo About text,
LAUNCH-POST.md lede, Talk bio) reads like an enforceable policy; change it to a
historical/archival statement instead (e.g., "Applied in README.md, glama.json,
server.json, GitHub About, LAUNCH-POST.md, and Talk bio on 2026-05-14") and
remove language that prescribes current enforcement; keep any enforcement rules
out of .planning/ and ensure live enforcement remains in the appropriate live
docs/checks.
| @@ -1,5 +1,6 @@ | |||
| { | |||
| "$schema": "https://glama.ai/mcp/schemas/server.json", | |||
| "description": "For AI coding agents writing Python: the canonical Python stdlib oracle. Exact symbols, exact sections, exact versions — offline, always free, always MIT, token-frugal.", | |||
There was a problem hiding this comment.
Use the locked positioning sentence verbatim in metadata.
Line 3 does not match the locked sentence wording/order (it rephrases with : and sentence split), so it fails the “verbatim across files” objective.
Suggested fix
- "description": "For AI coding agents writing Python: the canonical Python stdlib oracle. Exact symbols, exact sections, exact versions — offline, always free, always MIT, token-frugal.",
+ "description": "For AI coding agents writing Python, python-docs-mcp-server is the canonical Python stdlib oracle: exact symbols, exact sections, exact versions — offline, always free, always MIT, token-frugal.",📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "description": "For AI coding agents writing Python: the canonical Python stdlib oracle. Exact symbols, exact sections, exact versions — offline, always free, always MIT, token-frugal.", | |
| "description": "For AI coding agents writing Python, python-docs-mcp-server is the canonical Python stdlib oracle: exact symbols, exact sections, exact versions — offline, always free, always MIT, token-frugal.", |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@glama.json` at line 3, The "description" value must exactly match the locked
positioning sentence; update the JSON entry for the "description" key so its
string is replaced verbatim with: For AI coding agents writing Python the
canonical Python stdlib oracle. Exact symbols, exact sections, exact versions —
offline, always free, always MIT, token-frugal. Ensure there are no added
punctuation, line breaks, or rephrasing (do this change in the "description"
field).
…mmary Cross-AI review (Codex P3) caught that .planning/POSITIONING.md claimed 'Use verbatim in: glama.json / server.json' while the actual descriptions deliberately vary by surface (long marketing form vs medium vs PyPI-short). Fix: split into two lists — surfaces that use the sentence verbatim (README hero, GitHub About, launch post, talk bio) vs surfaces that adapt for length but preserve the three key phrases. Also: add 'token-frugal' to pyproject.toml description so all four machine-read positioning surfaces carry the full anchor consistently. Prior Claude reviewer had flagged this as deferrable to PR #3; folding it in here makes POSITIONING.md's new 'preserve all three key phrases' contract internally consistent. Char count: pyproject.toml description = 154 chars (under PyPI's 512 limit). Key-phrase coverage verified: 3 phrases x 4 surfaces = 12/12 present.
1 participant
Summary
First wave of the v0.1.5 launch coordination (PR #1 of 6 per CHANGE-REQUEST-v0.1.5-launch.md).
.planning/POSITIONING.mdas the single source of truth for the launch wave.glama.json,server.json, andpyproject.tomldescriptions with the locked positioning. All three now carry the "always free, always MIT" anchor per decision §9.5.Out of scope (separate PRs):
ayhammouda/python-docs-mcp-server— those will be updated by the upcoming repo rename PR..planning/skeletons — owned by the phase-backlog PR.Test plan
glama.jsonandserver.jsonparse as valid JSONpyproject.tomlparses as valid TOML; PyPI summary character count is within the 512-char limit.planning/POSITIONING.mdmatches verbatim in README hero, glama/server/pyproject descriptions🤖 Generated with Claude Code
Summary by CodeRabbit