"future-Claude" is core framework vocabulary, not just a heading - deliberate or historical, given the cross-CLI positioning?

[konsone]

Body:

adapters/lib.sh's rewrite_tool_neutral() neutralizes Claude-specific tool names for the other six adapters (Read tool -> read files, etc.), but "future-Claude" itself isn't touched anywhere in the build - and it's bigger than one heading. It's the term references/ai-first-rules.md uses throughout to describe the framework's central idea (the memoryless agent a vault is written for), and it appears in 56 of the ~65 command files, not just as the ## For future Claude section name. The vault operating-manual filename, _CLAUDE.md, is the same story - referenced literally by every command, unrenamed in every build. obsidian-world.md's PINNED.md mechanism is a third instance ("Claude can PIN critical information...").

I checked a compiled Hermes build and all three ship verbatim, Claude-named, same as Claude Code's own output. Even the README FAQ still calls the project "this Obsidian Claude skill" in one answer.

Given how central and repeated this naming is, I'm curious whether it's deliberate (branding, or something a generic term like "future-agent" would actually lose) or historical inertia from before the project went multi-platform - and whether renaming it project-wide has ever come up. Not proposing the change myself, just asking.