findxpand 0.1.0 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 756ce879fc1079faabc838210e35b0467f721dc3064b4c7f0032df2164ce8f0d
-  data.tar.gz: 28c91eb83f1f26942080772c18522cdb7a52fe7bd7c4c652dfa0aba58ac08735
+  metadata.gz: ef918e1eb0601a773101d3adb8b1212ab2c1e948c58a7f23444a573e0a1eea35
+  data.tar.gz: 12ab12acef7154ec6187b77cd722638a55615dafffa3bdb0728cc8ef158c0bc2
 SHA512:
-  metadata.gz: 84a14740683127e6b8b76b3194c460e9e451f21f28f1d6b02ff81cf6e8d4e4249eb166cd9d4440997660bc5b8e1d78f64075af05557a2d78b849a11a7a25d920
-  data.tar.gz: b711ee022f7a8122ea6929a633bbee91ae98612641ee926210511db4ce53dc15761e978bd2a96560749961c6135c5ad60731b2675fc40cc3234edef331c25e0e
+  metadata.gz: 0f8e4d22cf91f93aa0dc9785c2fe4ba7dd7f46ba1ae334986ffc6e68132a9ef4222ed9e7b4fe66e2fba5d2fd0fdabd599228d64d6e541f6aae83d88224da2d10
+  data.tar.gz: efdc1090f9ee2b8af362abd1983cb3b41df347cb8d66792d70d718e6776ba80b0f0617ab20c7a5250526b98068cedd5dad8a0b4ebfec8faae0048f375e19682a

data/lib/findxpand/rewrite.rb

@@ -108,7 +108,7 @@ module Findxpand
     # 100 KB.
     ATTRS = %q{(?:"[^"]*"|'[^']*'|[^>"'])*}
 
-    # Where a tag name ends. `` is not this test: it is ASCII in JavaScript
+    # Where a tag name ends. `\b` is not this test: it is ASCII in JavaScript
     # and PCRE and Unicode here and in Python, so `<titleé>` was rewritten as a
     # title by Node and PHP and refused by this file and the reference - two
     # implementations writing into an element that does not exist. A tag name

data/lib/findxpand/store.rb

@@ -129,10 +129,19 @@ module Findxpand
     # failure it was written for. Ported 2 Sep 2026, counter and semantics
     # unchanged, rather than reworded here (§20.1 rule 2).
     #
-    # Still outstanding, and named rather than hidden: Python and PHP do not
-    # have `unmatched` yet, and `Degraded.reason` — which is pinned by the
-    # shared fixture — still does not read it in any language. What reads it
-    # here is `reach_reason`, this package's own layer over the shared verdict.
+    # **Closed 3 Sep 2026.** Python and PHP both count `unmatched` now, Node
+    # carries `skip_undecodable` at zero it can never reach, and the four key
+    # sets are pinned to `middleware/conformance/counters.json` — one list, read
+    # by all four suites, exactly as `cases.json` pins the rewrite. Removing a
+    # required key now fails the suite of the language that removed it, which is
+    # the thing none of these packages could do for itself before: a missing key
+    # is invisible from inside the package that is missing it.
+    #
+    # Still outstanding, and named rather than hidden: `Degraded.reason` — which
+    # is pinned by the shared fixture — does not read `unmatched` in any
+    # language. What reads it here is `reach_reason`, this package's own layer
+    # over the shared verdict. Teaching the shared verdict to read it means a
+    # row in the fixture first, or three implementations drift from a fourth.
     NO_COUNTERS = {
       considered: 0, applied: 0, passed: 0, skip_encoded: 0,
       skip_large: 0, skip_undecodable: 0, error: 0, redirect: 0, status: 0,

data/lib/findxpand.rb

@@ -44,7 +44,7 @@ require 'findxpand/admin'
 require 'findxpand/middleware'
 
 module Findxpand
-  VERSION = '0.1.0'
+  VERSION = '0.1.1'
 
   # Not published to RubyGems, and nothing in this gem may claim otherwise.
   #
@@ -54,7 +54,9 @@ module Findxpand
   # 404, and the first thing a customer would learn about us. There is no publish
   # workflow in this tree for any of the three packages, so `gem install
   # findxpand` fails the same way. The CLI and the README ask here.
-  PUBLISHED_TO_REGISTRIES = false
+  #
+  # There is a workflow now and it has run: verified 3 Sep 2026 by asking the registry with no credentials: npm 200 (0.1.0, latest), PyPI 200 (0.1.0), RubyGems 200 (0.1.0). Packagist is still 404, which is why PHP keeps its own flag.
+  PUBLISHED_TO_REGISTRIES = true
 
   # Said once, wherever an install instruction appears, for as long as the gem is
   # unpublished. Without it the command reads as a mistake.

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: findxpand
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors:
 - Nextoria
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2026-09-02 00:00:00.000000000 Z
+date: 2026-09-03 00:00:00.000000000 Z
 dependencies: []
 description: One deploy. After that, approved fixes arrive as a manifest pushed to
   your own origin and no further release is needed. The corrected HTML is produced