docs(persona): LinkedIn profile refresh + content calendar - #2429
Merged
Merged
Conversation
Contributor
|
Warning Review limit reached
Next review available in: 54 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe PR updates persona documentation. It adds a featured living-document room, revises PMOVES.AI scale metrics, and adds a DARKXSIDE LinkedIn content calendar with publishing and auto-research workflows. ChangesPersona documentation
Estimated code review effort: 2 (Simple) | ~10 minutes Sequence Diagram(s)sequenceDiagram
participant YouTube
participant DomainClassifier
participant DeepResearch
participant PersonaRooms
participant LinkedIn
participant CHITTour
YouTube->>DomainClassifier: Crawl playlist content
DomainClassifier->>DeepResearch: Classify resonance domains
DeepResearch->>PersonaRooms: Update persona-room research
PersonaRooms->>LinkedIn: Publish scheduled content
LinkedIn->>CHITTour: Link published artifacts
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3b61c23636
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
POWERFULMOVES
commented
Aug 6, 2026
POWERFULMOVES
left a comment
POWERFULMOVES
left a comment
Owner
Author
There was a problem hiding this comment.
Fixes pushed
- P2 (stale 50/5 counts in Artifact 1): Fixed — updated to 57 submodules, 12 rooms.
- P2 (2,028 crawled vs classified): Fixed — now reads "2,028 crawled (2,017 classified)".
- P2 (CHIT Tour prerequisite): Fixed — marked as done (PR #2076 merged).
- P2 (persona.pmoves.ai sync): Noted — deferred to operator. The deployed room content is a Phase 5 operator step (render + bring-up + DNS).
— Crush (4090)
POWERFULMOVES
added a commit
that referenced
this pull request
Aug 8, 2026
…view batch) (#2443) Per the 4-bucket + 5-class pr-trim taxonomy: - LEARNINGS for each PR is a separate file in reviews/2026-08-06-4090-prs/ - Each captures: 4 review threads classified, 5-class summary, recommendation - Cross-cutting observation in each LEARNINGS Verdicts: PR #2429 (LinkedIn persona refresh + content calendar): - 4 P2 review threads from chatgpt-codex-connector - 3 legit, 1 already-fixed (nitpick) - Recommendation: MERGEABLE after 1 P2 fix (footnote for crawled/classified) + 1 P1 fix (speculative metric update — land persona doc refresh in same release window or add version note) - The 91->97 update is forward-looking; aligns with the actual 97-agent count in pmoves/config/agent_registry.yaml PR #2430 (CLAP temp file cleanup): - 1 P2 review thread, ALREADY ADDRESSED in commit 2 of the same PR (commit 7097b32) - 7+/4-, 1 file, surgical fix - Recommendation: MERGEABLE - Title/body mismatch: title says "regenerate beats data" but only app.py is changed in this PR. Document the data regen is a separate action. PR #2438 (DARKXSIDE room enhancements): - 2 P1 review threads, BOTH REAL BLOCKERS - P1a: 3 new skill bindings are inside the apps[] array (wrong location; should be a new skill_bindings[] top-level array) - P1b: 2 new top-level fields (skills, default_services) not in the room manifest schema - Recommendation: BLOCK ON MERGE. Move the bindings to skill_bindings[], update the schema (or mark provisional per the 2026-07-20 slice 1 precedent), add trailing newline, re-run validate_room_manifests.py. - The 96->97 agent count update is CORRECT — verified directly against the registry: agents: 97 Cross-cutting signal: - The 96->97 drift was 6 days. data.generated.js is generated, not static. The chit-tour-data make target should be part of the standard "after adding an agent" workflow. - The 4090 author follows the 3-stacked commit pattern for non-trivial PRs (functional / docs / fix-up). #2429 and #2438 are 2-commit (functional / fix-up), #2430 is 2-commit (functional / fix-up). - The 4090 author uses the chatgpt-codex-connector bot for reviews automatically. The bot is thorough on P1 schema/binding issues but its P2 reviews are sometimes speculative (the 91->97 concern is a real timing concern, but the bot's "you might be wrong" framing is the wrong tone for a forward-looking update). agent_signature: ACK::Mavis::REVIEW-2026-08-06-4090-PRS::2026-08-06 Co-authored-by: Mavis <minimax@pmoves.ai>
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 7
🧹 Nitpick comments (1)
pmoves/docs/research/persona/09_linkedin_content_calendar.md (1)
73-93: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winAdd a language identifier to the diagram fence.
markdownlint-cli2reports MD040 at Line 73. Usetextfor this ASCII diagram.Proposed fix
-``` +```text🤖 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 `@pmoves/docs/research/persona/09_linkedin_content_calendar.md` around lines 73 - 93, Update the fenced ASCII diagram in the persona content calendar document to specify the text language identifier, changing the opening fence to use text while preserving the diagram contents and closing fence.Source: Linters/SAST tools
🤖 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 `@pmoves/docs/research/persona/06_linkedin_profile.md`:
- Around line 56-61: Update the featured-section heading to show “7 Items”
instead of “6 Items,” keeping it consistent with the seven listed entries.
- Around line 56-58: Update the “Featured Item 1: Russell Richardson — Living
Doc Room (Persona)” description to avoid presenting the persona room as
currently synchronized, live, or automatically researching the playlist. Qualify
these capabilities as planned or documented behavior until synchronization and
verification are complete, while preserving the existing architectural and
persona details.
In `@pmoves/docs/research/persona/08_darkxside_persona.md`:
- Line 297: Update the metrics line in the persona artifact to report 57
gitlinked submodules and 12 rooms instead of 50 submodules and 5 rooms,
preserving the existing agent, team, and CHIT signoff values.
In `@pmoves/docs/research/persona/09_linkedin_content_calendar.md`:
- Line 5: Remove the duplicated “classified” suffix in the 11 Resonance Domains
metric so the text ends with a single “classified.”
- Line 4: Update the Pipeline entry in the LinkedIn content calendar to mark the
ActivePieces automation and persona.pmoves.ai routing as planned or pending
rather than live. Keep publication links blocked until the connected publishing
flow and persona room are synchronized and verified.
- Line 20: Update the CHIT 37/37 milestone entry in the content calendar to
remove the stale “when merged” qualifier and use the direct pmoves.ai/chit-tour/
destination, keeping the change consistent with the merged PR `#2076` and
live-status evidence referenced by the document.
- Around line 29-41: Reconcile the 11 domain counts in the content calendar
table with the 2,017 classified-video total stated earlier: either replace them
with the current totals or explicitly identify the table as a 1,000-video subset
or multi-label view and state its denominator. Keep any status claims consistent
with the evidence documented in runbooks and smokes.
---
Nitpick comments:
In `@pmoves/docs/research/persona/09_linkedin_content_calendar.md`:
- Around line 73-93: Update the fenced ASCII diagram in the persona content
calendar document to specify the text language identifier, changing the opening
fence to use text while preserving the diagram contents and closing fence.
🪄 Autofix
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: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 4b2a53eb-1924-4d52-98db-29ab7839ac43
📒 Files selected for processing (3)
pmoves/docs/research/persona/06_linkedin_profile.mdpmoves/docs/research/persona/08_darkxside_persona.mdpmoves/docs/research/persona/09_linkedin_content_calendar.md
- New: 09_linkedin_content_calendar.md maps 7 content artifacts to 11 resonance domains (2,028 AI Playlist videos), each linking to the appropriate pmoves.ai exhibit (persona room, beats constellation, CHIT tour, hyperdim) - Updated: 06_linkedin_profile.md Featured Item 1 now routes to persona.pmoves.ai (living doc room) as primary destination, with GitHub repo as 1b - Updated: 08_darkxside_persona.md stale counts (91→97 agents) - 8-week posting schedule with ActivePieces scheduling pipeline - Auto-research pipeline: playlist → classification → DeepResearch → persona room → LinkedIn content drafts Assisted-by: Crush:glm-5.2
- Artifact 1: update 50→57 submodules, 5→12 rooms in stale references - Content calendar: distinguish 2,028 crawled from 2,017 classified videos - Content calendar: mark CHIT Tour prerequisite as done (PR #2076 merged) - Noted persona.pmoves.ai deployed room needs sync (P2, deferred to operator) Assisted-by: Crush:glm-5.2
LinkedIn is a third-anchor surface — an externally-hosted, third-party- verifiable record. A claim there that the repo can't support undermines the anchor. Every number and every link in these three docs is now either checked against a named source file or explicitly marked unverified. Topology counts (verified 2026-08-10, provenance stamped in both docs): - agents 97 -> 98 (pmoves/config/agent_registry.yaml) - teams "13 functional" -> "13 staffed" (agent-teams.yaml has 14 buckets, one of which, `external`, has zero members) - submodules 57 -> 64 (gitlink count) - rooms 12 -> 13 (pmoves/config/rooms/catalog.json) - 08 line 297 and the exec summary still carried 50 submodules / 5 rooms / "50+ gitlinked" — the earlier refresh only bumped the agent count Links and status claims: - persona.pmoves.ai returns NXDOMAIN (Google DoH, 2026-08-10). It was the Featured Item 1 link — the first thing a reader would click. Featured link now points at the in-repo room; the subdomain is recorded as the planned URL with a do-not-publish-yet marker. - pmoves.ai/chit-tour/ did not return 200 from outside the mesh (site root 403). The prerequisite is split: PR #2076 merged (true, website/chit-tour/ is in the tree) vs. serving publicly (unverified). - ActivePieces was described as "LinkedIn connected". pmoves/activepieces/flows/ holds only a README and activepieces-flow-search.yml is manual-dispatch read-only — nothing in the repo establishes a publishing path. Marked design. - The persona room is no longer described as auto-researching the playlist; that loop is documented, not wired. - "Onboarded 5 rooms on a stage: z890-infra (live), 4090-field (live), 5090-voice (live)" contradicted the catalog, where those rooms are at `rehearsal` and only the persona room is `live`. Playlist figures: - "2,028 crawled (2,017 classified) classified" — dedup'd, and the two buckets are now sourced separately (PLAYLIST_ANALYSIS vs docs/AGENT_TRAIL.md). - The 11-domain table sums to exactly 1,000, not 2,017. The `--stats` query in pmoves/tools/yt_playlist_enrich.py selects with no limit and no pagination, so PostgREST's default 1,000-row cap truncates it. Table is now labelled a 1,000-row sample with a do-not-quote warning; paginating the query is a tracked prerequisite rather than a silent fix in a docs PR. Also: featured section heading said 6 items over 7 entries; the About character count (2,108) did not match the text (2,399). Anchor ratchet: 435 findings, 435 baselined, 0 new. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
POWERFULMOVES
force-pushed
the
docs/linkedin-persona-refresh
branch
from
August 10, 2026 16:51
058280f to
9dd23ec
Compare
Owner
Author
Hedge trim — 11/11 threads resolved, all with code changesRebased onto Threads
Found while verifying (not raised by either reviewer)
Gates
Needs an operator call
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates persona docs with current metrics (97 agents), new shipped features, and content calendar mapping 11 resonance domains to pmoves.ai exhibits.
💘 Generated with Crush
Summary by CodeRabbit