Reconcile marketplace candidates and Agentation derivative identity

[its-rosetta]

Provenance and derivative identity

Agentation → Mentions is based on Agentation by Scott Sunarto. This
candidate rebases the derivative onto
@smsunarto/bb-plugin-agentation@0.2.2 at exact revision
8bc27b91333e2228607b137d09b195d90e6aecfa, retains Scott's attribution,
MIT license, the modified agentation@3.0.2 PolyForm Shield license, the
React 19 component-detection patch, and complete plugin-scoped third-party
notices.

Scott's agentation remains the canonical marketplace identity. This
derivative now uses the non-colliding path, collection ID, plugin ID, package,
tool prefix, CLI name, and tag prefix agentation-mentions. The name is an
explicit namespace distinction, not a claim that this is an unrelated product.

That directly addresses the marketplace feedback on
get-bb/marketplace#58: the package is
rebased onto the maintained 0.2.x line, includes the production React 19 fix,
and no longer competes for the original author's ID or artwork.

Behavior, data, network, and authority

The derivative preserves Agentation's visual capture/review workflow and adds:

• a native composer mention for staged annotation batches;
• immediate or durable queued thread delivery;
• optional, read-only Identity Boundaries lookup and verified identity tags;
• distinct agentation_mentions_* tools and bb agentation-mentions CLI.

Annotation bodies, routing, replies, identity IDs, and retention state stay in
the plugin's local bb database/KV namespace. The UI uses bb plugin RPC,
realtime, and same-origin event streaming; it contacts no third-party service
of its own. Delivery can send or queue a target-thread prompt, and agent tools
can update annotation status/replies. The calling agent's normal permissions
govern any source fix.

Perspectives 0.2.0 addresses the review on
get-bb/marketplace#32:

• separate planner and worker provider/model/reasoning/permission settings;
• explicit inheritance/default rules and preflight validation before spawning;
• documented invocation count, cost, and permission behavior;
• Cole-approved PE02-A artwork.

help creates two hidden model invocations. gather_perspectives creates
one planner, 3–7 concurrent workers, and one synthesis thread, with at most one
bounded planner retry. Prompts require read-only advisory behavior, but bb 0.39
has no technical read-only permission mode; the configured/inherited permission
mode remains the real authority envelope. Perspectives stores no result data
and contacts no external service of its own.

Sticky Notes 0.1.1 and BB UI Reference 0.1.1 are artwork-only patch releases.
Their IDs, implementation, descriptions, permissions, and existing marketplace
source metadata are unchanged.

Approved artwork

All four packages preserve Cole's generated RGB source PNG and verified
RGB24 nearest-neighbor 16/24/32 derivatives byte-for-byte:

• Agentation → Mentions: AM02-A
• Perspectives: PE02-A
• Sticky Notes: SN02-A
• BB UI Reference: UI03-A

The package manifests use valid named compact host icons and the approved 32px
PNG as the rich logo. Marketplace entries use the same approved 32px bytes.

Release topology

Plugin ID	npm package	Version	Immutable tag
agentation-mentions	@phosphorco/bb-plugin-agentation-mentions	0.1.0	agentation-mentions/v0.1.0
perspectives	@phosphorco/bb-plugin-perspectives	0.2.0	perspectives/v0.2.0
sticky-notes	@phosphorco/bb-plugin-sticky-notes	0.1.1	sticky-notes/v0.1.1
bb-ui-reference	@phosphorco/bb-plugin-bb-ui-reference	0.1.1	bb-ui-reference/v0.1.1

No existing 0.1.0 package or tag is overwritten or moved.

Validation

• Mandatory RED witnesses failed on the old identity, missing artwork/version
  contracts, and ignored/unvalidated Perspectives execution settings.
• Final repository tests: 126/126 passed.
• Full typecheck passed.
• Full bb 0.39 production build passed; generated dist/ was excluded from
  the source commit.
• Clean bb 0.39 lifecycle: Agentation → Mentions and Perspectives both
  installed as running, survived restart, removed, and reinstalled as running.
• Four local npm pack candidates were inspected and checksummed.
• Every proposed npm version and tag was confirmed absent before handoff.