@kehto/paja 0.24.4 → 0.25.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -81,21 +81,32 @@ available, can connect to a bunker/NIP-46 URI, and only uses the generated local
81
81
  development signer when the Dev signer button is selected. Sign, publish, DM
82
82
  send, filesystem picker, Blossom upload, and external-link requests use one serialized in-page
83
83
  confirmation dialog. Deny has initial focus and Escape denies. A napplet-scoped
84
- sign request defaults to one-time approval, with explicit options to remember
85
- that event kind or trust every kind from the napplet identity and target. The trust
86
- choice carries a visible warning. Remembered signing authority is keyed by the
87
- active signer pubkey, host-owned napplet d-tag and aggregate hash, and the Paja
88
- target boundary. Runtime pointers are isolated by verified artifact hash;
89
- direct development targets are isolated by exact target URL, and their trust
90
- survives code reloads at that URL. Changing the signer, identity, artifact, or
91
- target asks again. Missing source identity or a nonnumeric kind remains
92
- one-shot, denials are never remembered, and the signer controls can revoke
93
- every remembered approval. If durable deletion fails, Paja keeps the approval
94
- listed and logs the failure instead of claiming revocation. A full Paja host
95
- reload creates a new ephemeral Dev signer and therefore asks again; a stable
96
- NIP-07 or NIP-46 account can reuse its saved choice. Publish and other operation
97
- confirmations continue to prompt independently. This is Paja runtime policy under draft
98
- [NAP-RELAY PR #2 at `0be8abce18beb46ca37bd4ddd042f58d30b4eedc`](https://github.com/napplet/naps/pull/2), not
84
+ sign or publish request defaults to one-time approval. The modal can remember
85
+ one event kind, all events for the current action, or **all signing and publishing
86
+ from this napplet version**. Signing-only permission never implies publication;
87
+ the combined choice explicitly grants both. The dialog shows the napplet,
88
+ artifact/version, source scope and signer, with a warning about future effects.
89
+ Grants bind the active account to the host's verified manifest identity (including
90
+ publisher) and artifact hash. Signed versions can reuse approval after reload;
91
+ another manifest, version or account asks again. Local single-file targets use
92
+ their content hash in a separate local scope. Direct development URLs are mutable,
93
+ so approvals last only for the current document/frame load and must be renewed
94
+ after reload; HMR can still change that development session's running code.
95
+ CVM without a user signer uses a separate, document-scoped host-generated
96
+ principal; its approvals never transfer to a user account or another host session.
97
+ Otherwise, unknown identity/account/kind remains one-shot. Denials are never remembered.
98
+ Signer controls revoke every remembered signing/publication approval; failed
99
+ durable deletion is reported instead of claiming revocation. Missing browser
100
+ storage makes new choices memory-only. An ephemeral Dev account changes on a
101
+ full host reload and therefore asks again. Older signing-only records are retained
102
+ without gaining publication and emit `KEHTO-PAJA-SIGNER-CONSENT-V1` once per host
103
+ module lifetime; current records stay quiet. Removing a window or changing the
104
+ signer denies pending signing/publication. Link requests always use the modal,
105
+ and the external browser handoff runs directly from its approval click with
106
+ `noopener,noreferrer`. Other operation permissions remain separate.
107
+ This is Paja host policy under [NAP-RELAY PR #2 at `9f30b350`](https://github.com/napplet/naps/blob/9f30b3505335a52c574ff570576687d6467021ff/naps/NAP-RELAY.md),
108
+ [NAP-OUTBOX PR #32 at `8865f73d`](https://github.com/napplet/naps/blob/8865f73d52a4864afee145f28d26520476273927/naps/NAP-OUTBOX.md)
109
+ and [NAP-LINK PR #53 at `50a2cd45`](https://github.com/napplet/naps/blob/50a2cd45e76f06e87b87e93842badf4c61f17bde/naps/NAP-LINK.md), rather than
99
110
  a Kehto kernel default. Upload consent identifies the requesting napplet, file, MIME type,
100
111
  size, selected server, and durable public effect before bytes leave the browser.
101
112
  A denial or a live publish with no accepting relay returns a canonical failure
@@ -149,8 +160,8 @@ The focused host regression runs in Chromium and Firefox after `pnpm build`:
149
160
  Other domains are equally capability-bound. Relay, outbox, and count require
150
161
  live relays; count uses NIP-45 `COUNT` without downloading events. Storage
151
162
  requires writable `localStorage`; the memory setting is an unadvertised fixture.
152
- Keys requires a document listener, media requires the browser Media Session
153
- API, notifications require Paja's host renderer, links require browser
163
+ Keys requires a document listener, media requires a browser document and uses audio/video elements (OS Media Session
164
+ integration is optional), notifications require Paja's host renderer, links require browser
154
165
  navigation, and intent requires the installed-catalog/runtime-tab host
155
166
  controller. DM also requires the Dev signer and live relays; FS requires a
156
167
  successful OPFS probe, while picker calls additionally require the corresponding
@@ -572,3 +583,11 @@ Paja MUST load all three NIP-5D manifest kinds: root `15129`, named `35129`, and
572
583
  ## Controller diagnostics
573
584
 
574
585
  Paja shows a numbered controller icon directly beside the console arrow for each controller the browser detects. Each slot has its own color and input animation; hover for the controller model and activity state. Buttons and stick movement light up only that controller (stick movement below 0.12 is ignored). Quick taps retain the highlight briefly so they are easy to spot. Reduced-motion settings keep the activity highlight without animation. Disconnecting removes the icon. Browsers may require a button press before exposing a newly connected controller. These host diagnostics work without a napplet gamepad subscription and do not change focus-scoped input delivery.
586
+
587
+ ## Media player
588
+
589
+ Paja provides shell-owned audio/video playback through its resource resolver and a
590
+ collapsible player with transport, seek, volume, and close controls. It also
591
+ streams live HTTPS MP3/AAC radio without awaiting EOF and displays napplet-owned
592
+ sessions. See [Media playback](../../docs/media.md) for
593
+ source support, lifecycle rules, and canonical API examples.