docs: add naming and branding guidance for plugin authors

[Quick104]

Problem

Related issue: N/A — narrow fix

The plugin SDK is where third-party developers land first, and it says nothing about what to name a plugin or whether the Silo logo may be its icon. Silo-Server/siloserver.org#16 adds naming guidance to the brand page; this repository should point to it.

Approach

Add a short "Naming and branding" section before "License": pick your own name and mention Silo in the summary, silo-plugin-* repository names are fine, avoid "Silo[word]" product names, do not use the Silo logo as the plugin icon, set publisher_name to yourself unless the project publishes the plugin, and link the brand page for the rest. publisher_name is the existing manifest presentation field in proto/silo/plugin/v1/common.proto.

Validation

README only. Verified the referenced field exists:

$ grep -n publisher_name proto/silo/plugin/v1/common.proto
159:  string publisher_name = 9;

Risks

None identified.

Checklist

• I read and can explain the complete diff.
• This pull request addresses one concern.

AI Disclosure

• Harness: Claude Code (Claude Agent SDK) running inside T3 Code
• Tool(s): Claude Code
• Model(s): claude-fable-5-1
• Involvement: Fully AI-generated, human verified
• Adversarial review: n/a — documentation-only change; the copied file was diffed byte-for-byte against the source branch.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Added naming and branding guidance covering plugin names, Silo references, logos, publisher attribution, and brand-policy documentation.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 64e63d95-1665-45f5-96c1-144d1879fa0f

📥 Commits

Reviewing files that changed from the base of the PR and between f110653 and e873349.

📒 Files selected for processing (1)

• README.md

Included review availability: 0 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour.

---

📝 Walkthrough

Walkthrough

README.md adds plugin naming and branding guidance, including attribution, logo usage, publisher naming, and a link to the full brand policy.

Changes

Plugin naming and branding guidance

Layer / File(s)	Summary
Plugin naming and branding documentation README.md	Adds guidance for plugin names, Silo references, logos, publisher attribution, naming restrictions, and the full brand policy.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to e8733

This documentation-only update adds plugin naming and branding guidance without changing runtime behavior or public interfaces. No current merge-readiness risk is identified.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the documentation change and identifies the target audience. It matches the README addition about naming and branding guidance for plugin authors.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/brand-guidance-sync

---

_{Comment @coderabbitai help to get the list of available commands.}