docs(platform-glossary): resolve "the operator" and the crew vocabulary clash

[ductiletoaster]

Closes the glossary half of A0.4 in the PixelOven Agent Stack Program Plan (requirement G-7).

Why

PixelOven is standing up a component literally named operator — a soft fork of kunchenguid/firstmate, now at pixeloven/operator (private). That creates two vocabulary collisions the foundation should own rather than a consumer, because both appear in agent-facing instructions rather than in one project's docs.

1. "the operator" is a person, not a program

Escalation instructions across the fleet say "ask the operator", "the operator approves", "escalate to the operator". These always mean a human. An agent that resolves them to a program name does something plausible and wrong — the worst failure shape available.

The rule added:

• Prose keeps "the operator" for the human, unqualified and unhedged, so the existing corpus stays correct by default.
• A project named operator is always code-styled (operator) and never capitalized. Capitalization cannot carry the distinction, because it is invisible at the start of a sentence — exactly where "The operator should…" appears.
• Kubernetes operators are noted as a third sense.

2. "crew" now means two different things

Vocabulary	"crew" is	the human is	a worker is
this foundation	the set of agent roles	the operator	a dispatched role
firstmate lineage	the fleet of dispatched worker processes	the captain	a crewmate / secondmate

The load-bearing rule: do not translate between them silently. A firstmate crewmate is a running process in a git worktree; a foundation crew role is a declarative capability definition. They are not the same kind of thing, and one does not implement the other.

It also states explicitly that "the captain" and "the operator" denote the same human, so a third name for that person never gets invented.

Contribution rules honoured

• .claude-plugin/plugin.json and package.json bumped 0.22.0 → 0.23.0 (additive skill content), per the version-bump CI gate.
• docs/CATALOG.md regenerated for the updated frontmatter description.
• Ran locally, all green: check_skills.py, render_roles.py --check, check_skill_refs.py, gen_catalog.py --check, and the templates YAML parse.

Scope

Additive only — one skill, no role definitions touched, no behavior changed.