Track host adoption of the proposed `projects` scope

[SongshGeo]

Tracking issue for docs/PROPOSAL_PROJECTS_SCOPE.md — the projects scope we proposed to the PaperBell host team when the project dropdown shipped (#25).

Status: not implemented by any host build. Confirmed against 0.4.4-test.c69a024: requestProjects, onProjectsChange, and paperbell:projects-changed are all absent, and capabilities is still the original seven scopes. Our gating (capabilities.includes("projects") and typeof requestProjects === "function") means this is completely inert — the field falls back to free text with no console noise and no consent prompt.

What we are waiting on

The two questions that matter more than the API itself:

1. Which frontmatter shape does Project Manager actually query? We write a plain acronym (project: ColMemo) per the existing PAPERBELL_SUITE.md convention. If it wants [[wikilink]], changing the writer is one line — migrating notes already on users' disks is not. The escape hatch offered in the proposal: let the host return a frontmatterValue per project and we write it verbatim, keeping format authority on the Project Manager side.
2. One paper is up to four notes, all carrying the same project:. Counting notes counts one paper up to four times; longform.title is identical across a paper's drafts and is the ready-made dedupe key.

Plus: stable id across renames, acronym uniqueness per vault, and a low-friction consent gate (see #31).

When it lands

• Re-vendor src/paperbell/shared-config.ts, drop the proposal marker, reconcile with whatever the host actually shipped
• test/paperbell/host-conformance.test.ts already has a block that stays skipped today and arms itself automatically once a bundle carrying requestProjects is installed — it checks the parts a host could plausibly ship without (the advertised scope, the event name)
• MAINTAINING.md warns that a straight re-vendor deletes the proposal block; see Re-vendor shared-config for host schemaVersion 2 #27

Note

#29 may make this moot for most users: cimpoFolders.projects in the v2 config already tells us where projects live, over a scope we consume today.