@kehto/paja 0.22.0 → 0.24.1

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
@@ -198,6 +198,8 @@ runtime tabs in local storage so returning to `/web/paja/` restores the previous
198
198
  pointer set. An explicit pointer in the URL still takes precedence over restored
199
199
  tabs.
200
200
 
201
+ The browser page title follows the active napplet tab name, including when switching or closing tabs. With no active napplet, the title is `@kehto/paja`.
202
+
201
203
  The static artifact defaults to Paja's standard live relays and memory uploads.
202
204
  To point it at specific live relays or Blossom upload servers, pass
203
205
  comma-separated host lists when generating the artifact:
@@ -252,6 +254,14 @@ catalog. Entries preserve exact conventions and ordered parameter names under
252
254
  publisher/kind-safe opaque IDs, including nameless root and snapshot artifacts.
253
255
  The target's resolved `intent` domain must be available; INC is not required.
254
256
 
257
+ Catalog installs, replacements, removals, and user default-handler updates emit
258
+ `intent.changed` to eligible open napplets (`napplet.intent.onChanged(...)`).
259
+ Replacements notify both removed and added archetypes, once per slug, using the
260
+ current filtered catalog. A `no handler` rejection remains terminal: callers must
261
+ retry explicitly; installing a handler does not replay the failed invocation.
262
+ This follows `napplet/naps` NAP-INTENT on master (last changed at `e5308ac`), whose
263
+ runtime behavior recommends notifications on catalog/default changes.
264
+
255
265
  Selection uses exact contracts and user-owned default, chooser, recommendation,
256
266
  and explicit-authorization policy. Explicit handler IDs require sender-aware
257
267
  authorization and cannot address an arbitrary running frame.
@@ -548,3 +558,7 @@ remain a documented upstream spec gap; no host sender identity is invented.
548
558
  ## GAMEPAD integration
549
559
 
550
560
  This non-normative guidance defers to the living [NAP-GAMEPAD](https://github.com/napplet/naps/pull/108). Services export `createGamepadService` and `browserGamepadOptions`; shell exports `denyNappletControllerAccess`. Paja and the playground register one host reader and deny native gamepad/HID/USB paths before frame execution. Source-bound subscriptions receive immediate full snapshots; only the visible host's input owner gets live controls. Focus loss supplies neutral controls and timestamp zero; unsubscribe, window destruction, and service removal release polling. Non-browser or denied native readers report the proposal's unavailable reasons. See [Controller input](https://github.com/kehto/web/blob/main/docs/gamepad.md).
561
+
562
+ ## Controller diagnostics
563
+
564
+ 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.