backlog: file the @flashynetwork version-reconciliation blocker

.backlog/items.json

@@ -1 +1,25 @@
-[]
+[
+ {
+  "id": "backlog/flashy-ledger/reconcile-version-and-target-flashynetwork",
+  "rev": 3,
+  "kind": "blocker",
+  "status": "done",
+  "title": "Reconcile the ledger’s version, then publish to @flashynetwork once named",
+  "source": {
+   "repo": "repo/flashy-ledger"
+  },
+  "assertedBy": "agent/flashy-ledger-bot",
+  "asserted": "2026-10-29",
+  "expires": "2026-11-12",
+  "visibility": "public",
+  "detail": "Correction: this item was filed on a stale, shallow clone of this repository that predated commit c00c482c (2026-10-26, \"Rename the package to @flashyos/ledger, version 1.0.1\"). That commit already did exactly what this item asked for, for a better-documented reason than I had: the GitHub org rename (FlashyLabs -> AgenteLabs) broke @flashylabs’s GitHub Packages scope resolution outright, so ClaimYour.Gold’s npm ci started 404ing on @flashylabs/ledger@0.8.0. The fix published @flashyos/ledger 1.0.1 to PUBLIC npm (not GitHub Packages) and updated this repo’s own package.json, .npmrc (removed) and publish.yml to match; ClaimYour.Gold’s dependency is confirmed updated to \"@flashyos/ledger\": \"^1.0.1\" on its own main. All three numbers this item worried about now agree. It was not an out-of-band hand-publish — it was a committed, reasoned CI change I simply hadn’t read before filing this. The one thing still genuinely open is the later move from @flashyos/ledger to @flashynetwork/ledger once that scope is actually used for something — tracked in flashyos’s own backlog item on the @flashynetwork decision, not here.",
+  "owner": "person/michael",
+  "capabilitiesWanted": [
+   "npm-administration"
+  ],
+  "promoted": {
+   "at": "2026-10-29",
+   "by": "person/michael"
+  }
+ }
+]

backlog.fragment.json

@@ -3,6 +3,30 @@
   "backlog": "1",
   "source": "repo/flashy-ledger",
   "org": "org/flashy-ledger",
-  "generated": "2026-10-29T04:44:17.574Z",
-  "items": []
+  "generated": "2026-10-29T15:09:51.656Z",
+  "items": [
+    {
+      "id": "backlog/flashy-ledger/reconcile-version-and-target-flashynetwork",
+      "rev": 3,
+      "kind": "blocker",
+      "status": "done",
+      "title": "Reconcile the ledger’s version, then publish to @flashynetwork once named",
+      "source": {
+        "repo": "repo/flashy-ledger"
+      },
+      "assertedBy": "agent/flashy-ledger-bot",
+      "asserted": "2026-10-29",
+      "expires": "2026-11-12",
+      "visibility": "public",
+      "detail": "Correction: this item was filed on a stale, shallow clone of this repository that predated commit c00c482c (2026-10-26, \"Rename the package to @flashyos/ledger, version 1.0.1\"). That commit already did exactly what this item asked for, for a better-documented reason than I had: the GitHub org rename (FlashyLabs -> AgenteLabs) broke @flashylabs’s GitHub Packages scope resolution outright, so ClaimYour.Gold’s npm ci started 404ing on @flashylabs/ledger@0.8.0. The fix published @flashyos/ledger 1.0.1 to PUBLIC npm (not GitHub Packages) and updated this repo’s own package.json, .npmrc (removed) and publish.yml to match; ClaimYour.Gold’s dependency is confirmed updated to \"@flashyos/ledger\": \"^1.0.1\" on its own main. All three numbers this item worried about now agree. It was not an out-of-band hand-publish — it was a committed, reasoned CI change I simply hadn’t read before filing this. The one thing still genuinely open is the later move from @flashyos/ledger to @flashynetwork/ledger once that scope is actually used for something — tracked in flashyos’s own backlog item on the @flashynetwork decision, not here.",
+      "owner": "person/michael",
+      "capabilitiesWanted": [
+        "npm-administration"
+      ],
+      "promoted": {
+        "at": "2026-10-29",
+        "by": "person/michael"
+      }
+    }
+  ]
 }

public/.well-known/backlog.json

@@ -3,6 +3,30 @@
   "backlog": "1",
   "source": "repo/flashy-ledger",
   "org": "org/flashy-ledger",
-  "generated": "2026-10-29T04:44:17.577Z",
-  "items": []
+  "generated": "2026-10-29T15:09:51.659Z",
+  "items": [
+    {
+      "id": "backlog/flashy-ledger/reconcile-version-and-target-flashynetwork",
+      "rev": 3,
+      "kind": "blocker",
+      "status": "done",
+      "title": "Reconcile the ledger’s version, then publish to @flashynetwork once named",
+      "source": {
+        "repo": "repo/flashy-ledger"
+      },
+      "assertedBy": "agent/flashy-ledger-bot",
+      "asserted": "2026-10-29",
+      "expires": "2026-11-12",
+      "visibility": "public",
+      "detail": "Correction: this item was filed on a stale, shallow clone of this repository that predated commit c00c482c (2026-10-26, \"Rename the package to @flashyos/ledger, version 1.0.1\"). That commit already did exactly what this item asked for, for a better-documented reason than I had: the GitHub org rename (FlashyLabs -> AgenteLabs) broke @flashylabs’s GitHub Packages scope resolution outright, so ClaimYour.Gold’s npm ci started 404ing on @flashylabs/ledger@0.8.0. The fix published @flashyos/ledger 1.0.1 to PUBLIC npm (not GitHub Packages) and updated this repo’s own package.json, .npmrc (removed) and publish.yml to match; ClaimYour.Gold’s dependency is confirmed updated to \"@flashyos/ledger\": \"^1.0.1\" on its own main. All three numbers this item worried about now agree. It was not an out-of-band hand-publish — it was a committed, reasoned CI change I simply hadn’t read before filing this. The one thing still genuinely open is the later move from @flashyos/ledger to @flashynetwork/ledger once that scope is actually used for something — tracked in flashyos’s own backlog item on the @flashynetwork decision, not here.",
+      "owner": "person/michael",
+      "capabilitiesWanted": [
+        "npm-administration"
+      ],
+      "promoted": {
+        "at": "2026-10-29",
+        "by": "person/michael"
+      }
+    }
+  ]
 }