[dskvr]

Adds the common capability (NAP-COMMON), which 12 published applets require.

• Reads: getProfile (by key or shared address) and follows are public data, read from the profile service and the account's current list.
• Writes: follow/unfollow change the account's kind 3 list through the shell's signing gate, so the person sees "Change who you follow" with who is added and removed before anything is signed. Every other entry, tag and the content are kept. react (kind 7, with the author and kind when known, plus custom emoji) and report (kind 1984) publish like any other post. Every write succeeds when any relay accepts it (D-028).
• Read-only and signed-out sessions cannot write.
• Decision recorded as D-035. D-034 on main is the release-on-merge decision.

Verification

• New common-actions.feature covering reads, follows, consent refusal, invalid keys, no relay accepting, reactions, reports and read-only sessions.
• A kernl scenario drives common.follow from a mounted applet to the "Change who you follow" prompt, and a "no" refuses it.
• Build, type-check, dependency rules, docs gate, svelte check and slop (100) all pass locally.
• The full test suite was not run locally: this machine is at load average ~67 from other sessions, and that times out unrelated heavy crypto scenarios. CI's clean runner is the authority.
• The store's cache-first scenario no longer depends on timing: the fake relay waits for the cache to answer.

🤖 Generated with Claude Code