@ham2k/extension-sdk 0.12.8 → 0.12.9

package/dist/activityScoring.js

@@ -128,8 +128,10 @@ function activityScorer(rules) {
       const isDupe = verdict === "duplicate";
       const freshRefOnly = verdict === "ref" && !freshRefRescuesActivation;
       const activationCredit = freshRefOnly ? 0 : activationValue;
+      const hasStake = activationValue + huntingValue > 0;
       const score = { value: isDupe ? 0 : activationCredit + huntingValue };
-      if (isDupe) {
+      if (!hasStake) {
+      } else if (isDupe) {
         score.dupe = true;
         score.alerts = ["duplicate"];
       } else if (verdict) {

package/dist/index.d.ts

@@ -1,4 +1,4 @@
-// @ham2k/extension-sdk 0.12.8
+// @ham2k/extension-sdk 0.12.9
 /** Experimental v1 panel scene contract. All coordinates are in the scene's viewBox. */
 export interface PanelScene {
 	version: 1;

package/docs/hooks.md

@@ -2239,6 +2239,7 @@ Consequences worth knowing:
 
 | Category | Role | Notes |
 |---|---|---|
+| `chasing` | what each contact counts toward a program's checklist (claims) | [claims.md](https://github.com/ham2k/halo/blob/main/docs/design/claims.md) |
 | `confirmation` | QSL/confirmation sources (spot-history cross-checking) | |
 | `opSetting` | per-operation settings contributions | |
 

package/docs/settings.md

@@ -346,6 +346,12 @@ override) without it cluttering the panel for regular users:
 { type: "field", fieldType: "text", key: "apiEndpointOverride", label: "API Endpoint Override", devMode: true }
 ```
 
+A panel with nothing to show at the current developer-mode setting is left
+out of the Settings screen's list of categories rather than shown as an empty
+heading, so a panel whose every field is `devMode` appears there only while
+developer mode is on. Its sidebar entry is not: give such a panel
+`sidebar: false`, or the entry opens on an empty page.
+
 ## `aliases`: short names for the SET command
 
 The `SET`, `SHOW` and `HIDE` commands search every declared setting by key,
@@ -435,6 +441,16 @@ one dialog.
   value: false, target: "logging" }
 ```
 
+The Developer settings panel is another: its "Extension Settings" section
+collects every field tagged `target: 'developer'` — the place for a switch
+only someone working on the extension or its service needs, such as POTA's
+"use the test servers". The section shows only once some field targets it.
+Pair the target with `devMode: true` so the field's home panel hides it too
+(see "`devMode` fields" above), and with `sidebar: false` when that is the
+panel's only field. The section is extension API 8: a bundle relying on it
+declares `"api": 8`, so an older app — which would list the panel as an empty
+heading — is never offered it.
+
 `target` is a single target key, or an array when the same field should
 surface under more than one. A `'<target>-extended'` target (e.g.
 `'logging-extended'`) is the same idea, but starts hidden behind that

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ham2k/extension-sdk",
-  "version": "0.12.8",
+  "version": "0.12.9",
   "description": "Write extensions for the Ham2K Logger: typed hook contracts and the host API",
   "keywords": [
     "ham2k",