docs: ground GitHub topics in rankable agent-memory niches

[tonyketcham]

Summary of changes

Cut the GitHub topic list from 20 implementation labels to 12 niches where a 64-star repo can actually show up. Keep the About blurb Context alignment, version controlled. Put that same line on the README.

GitHub topic pages sort by stars. Oceans such as javascript, ai-agents, and markdown hide this repo. Small honest niches already rank: markdown-cms is 1st of 13, git-cms is 4th of 17, git-native is 6th of 59. file-based-cms, project-memory, and agent-context are small enough that 64 stars should still appear. Demand tags (agent-memory, coding-agents, context-engineering, context-management, llm-memory, docs-as-code) stay for people who filter, even though we will not own those pages yet.

Canonical payload: .github/topics.json. GitHub does not read that file. A repo admin must apply it after merge:

gh api -X PUT repos/FlatbreadLabs/flatbread/topics --input .github/topics.json

The GitHub description is already the tagline. Do not change it.

npm keywords on the public flatbread package mirror the twelve, plus markdown and knowledge-graph for npm search.

Rationale and dropped-topic table: docs/positioning.md.

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• I added doc comments to any new public exports, and inline comments to any hard-to-understand areas
• My changes generate no new console errors locally
• If applicable, try to include a test that fails without this PR but passes with it

scripts/github-topics.test.js checks that .github/topics.json is a valid GitHub topics payload and that the README tagline, positioning doc, and npm keywords stay in sync.

Does this introduce any non-backwards compatible changes?

• Yes
• No

Does this include any user config changes?

• Yes
  • If so, I have updated the relevant areas of documentation
• No

  

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit b0d27ed. Configure here.}

[cursor]

Topic sync test false positives

Low Severity

The positioning sync check only looks for a backticked topic name anywhere in docs/positioning.md. The dropped-topics table already repeats several live niche names in backticks, so a topic can vanish from the canonical table—or a rejected topic can be added to .github/topics.json—and the test still passes.

Additional Locations (1)

• docs/positioning.md#L89-L98

 

^{Reviewed by Cursor Bugbot for commit b0d27ed. Configure here.}