Skip to content

docs: clarify legacy graphify-ts rename guidance#481

Merged
mohanagy merged 2 commits into
nextfrom
issue-468-legacy-naming
Jun 2, 2026
Merged

docs: clarify legacy graphify-ts rename guidance#481
mohanagy merged 2 commits into
nextfrom
issue-468-legacy-naming

Conversation

@mohanagy
Copy link
Copy Markdown
Owner

@mohanagy mohanagy commented Jun 2, 2026

Summary

  • add an explicit README rename/migration note for users arriving from old graphify-ts links, listings, or remotes
  • mirror the canonical Madar package/repo guidance in the MCP registry metadata and CLI/MCP reference
  • lock the rename-note contract with rebrand and registry metadata tests while keeping other public surfaces free of active legacy branding

Testing

  • npm run test:run -- tests/unit/rebrand-surface.test.ts tests/unit/mcp-registry-metadata.test.ts
  • npm run typecheck
  • npm run build
  • CI=1 npm run test:run

Closes #468

Summary by CodeRabbit

  • Documentation

    • Added migration guidance clarifying the project's current name and package identifier, directing users from legacy references to canonical sources.
  • Tests

    • Added test coverage to validate rename and migration documentation accuracy.

mohanagy and others added 2 commits June 2, 2026 22:13
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jun 2, 2026

Review Change Stack

📝 Walkthrough

Walkthrough

The pull request updates user-facing documentation, registry metadata, and test assertions to clarify that Madar is the renamed continuation of graphify-ts. A "Rename and migration" section is added to the README, registry metadata notes are extended with rename context, and test infrastructure is added to validate rebrand content across canonical surfaces.

Changes

Rebrand surface and assertion updates

Layer / File(s) Summary
README, registry metadata, and documentation updates
README.md, docs/mcp-registry/server.json, docs/reference/cli-and-mcp.md
README includes a new "Rename and migration" section explaining the graphify-ts to madar rebrand; registry metadata notes and CLI reference documentation are extended with rename clarifications and canonical identifiers.
Registry metadata type and content assertions
tests/unit/mcp-registry-metadata.test.ts
Type structure is updated to include publisher-provided notes and source, a publisherNotes variable is extracted, and assertions verify rename/continuation context and canonical repository/package references within those notes and documentation content.
Rebrand content validation helpers and tests
tests/unit/rebrand-surface.test.ts
A stripRenameNote helper excises the README rename section by heading bounds; a new test validates the rename section contains expected rebrand content while the rest remains free of legacy branding; the existing legacy-brand removal test is updated to use the helper.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

  • mohanagy/madar#438: Both PRs update MCP registry metadata and assertions—this one adds rename/continuation context to _meta.notes while the retrieved PR introduces validation workflows that check the same manifest structure.
  • mohanagy/madar#466: Both PRs touch registry metadata and documentation surfaces; this one focuses on rebrand clarifications and assertions while the retrieved PR refactors broader README and version updates.

Poem

🐰 From graphs to madar we hop along,
The old name fades, new branded strong,
Rename and migrate, signs now clear—
Users find their way without fear!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title 'docs: clarify legacy graphify-ts rename guidance' directly addresses the main change: adding migration guidance for users encountering the legacy graphify-ts naming.
Description check ✅ Passed The PR description includes all required sections from the template: Summary explaining what changed, Testing with specific commands, and Related issues (Closes #468). The description is complete.
Linked Issues check ✅ Passed The PR meets all requirements from issue #468: adds a README rename/migration note for legacy graphify-ts users [#468], updates MCP registry metadata with Madar canonical references [#468], clarifies CLI/MCP documentation [#468], and locks the rename contract with tests [#468].
Out of Scope Changes check ✅ Passed All changes directly support issue #468 objectives: README rename section, registry metadata updates, CLI documentation clarification, and test coverage for rename guidance are all within scope.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch issue-468-legacy-naming

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 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 `@tests/unit/mcp-registry-metadata.test.ts`:
- Around line 178-180: The test currently verifies repo URLs but misses
asserting the canonical npm package name; update the unit test in
tests/unit/mcp-registry-metadata.test.ts to also assert that the CLI reference
text includes the package identifier by adding an expectation against the same
variable used for the CLI reference (reference) toContain the string
"`@lubab/madar`" so the test fails if the canonical package name is removed or
changed.
🪄 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 4d45ca52-2b56-409c-be26-c09b5596dd35

📥 Commits

Reviewing files that changed from the base of the PR and between 551985a and eff6972.

📒 Files selected for processing (5)
  • README.md
  • docs/mcp-registry/server.json
  • docs/reference/cli-and-mcp.md
  • tests/unit/mcp-registry-metadata.test.ts
  • tests/unit/rebrand-surface.test.ts

Comment on lines +178 to 180
expect(reference).toContain('If you still discover older `graphify-ts` links or listings, Madar is the current project name.')
expect(reference).toContain('`https://github.com/mohanagy/madar`')
expect(releaseDoc).toContain('npm run registry:validate')
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Assert the canonical npm package in this docs contract test.

These checks lock the repo URL, but they do not lock @lubab/madar. If the package identifier drops out of the CLI reference rename note, this PR objective still regresses while the test stays green.

Suggested assertion
     expect(reference).toContain('If you still discover older `graphify-ts` links or listings, Madar is the current project name.')
+    expect(reference).toContain('`@lubab/madar`')
     expect(reference).toContain('`https://github.com/mohanagy/madar`')
📝 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.

Suggested change
expect(reference).toContain('If you still discover older `graphify-ts` links or listings, Madar is the current project name.')
expect(reference).toContain('`https://github.com/mohanagy/madar`')
expect(releaseDoc).toContain('npm run registry:validate')
expect(reference).toContain('If you still discover older `graphify-ts` links or listings, Madar is the current project name.')
expect(reference).toContain('`@lubab/madar`')
expect(reference).toContain('`https://github.com/mohanagy/madar`')
expect(releaseDoc).toContain('npm run registry:validate')
🤖 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 `@tests/unit/mcp-registry-metadata.test.ts` around lines 178 - 180, The test
currently verifies repo URLs but misses asserting the canonical npm package
name; update the unit test in tests/unit/mcp-registry-metadata.test.ts to also
assert that the CLI reference text includes the package identifier by adding an
expectation against the same variable used for the CLI reference (reference)
toContain the string "`@lubab/madar`" so the test fails if the canonical package
name is removed or changed.

@mohanagy mohanagy merged commit ab46053 into next Jun 2, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant