diff --git a/.changeset/eb13-procedure-271.md b/.changeset/eb13-procedure-271.md
deleted file mode 100644
index c609f98..0000000
--- a/.changeset/eb13-procedure-271.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-"@cosyte/x12": patch
----
-
-**The 271 reads and builds the procedure a benefit line applies to (EB-13).**
-
-Dental payers send per-procedure coinsurance, frequency, age and maximum limits on 271 benefit lines,
-keyed by a CDT code in EB-13, and the CAQH CORE eligibility data content rule calls for it. Until now
-those lines read back with no procedure, and the 271 builder could not write one.
-
-- Reading: each `X12EligibilityBenefit` now carries `procedure`, an `X12EligibilityProcedure` with the
-  qualifier (EB-13-1), the code (EB-13-2), up to four modifiers in transmitted order (EB-13-3 to
-  EB-13-6) and the description (EB-13-7) when the sender sent one. It is `undefined` when EB-13 is
-  absent or has no qualifier. Components are split on the component separator the interchange
-  declares in ISA-16, never an assumed `:`.
-- Building: a 271 benefit takes an optional `procedure` (`Build271ProcedureSpec`: qualifier, code
-  and modifiers) and writes it as one composite. The builder refuses an empty qualifier or code, an
-  empty modifier, and more than four modifiers, because a fifth would land in the description
-  position and an empty one would shift later modifiers on read. It does not write a description.
-- The 270 reader's EQ-02 procedure decodes exactly as before; it now shares its decoder with the 271.
-
-If you build an `X12EligibilityBenefit` object literal yourself, such as a test double, add
-`procedure: undefined` to it. Code that reads benefits from `get271` needs no change.
diff --git a/README.md b/README.md
index df47a0d..778d530 100644
--- a/README.md
+++ b/README.md
@@ -31,7 +31,7 @@ a stable code instead of failing or guessing.
 
 ## Status
 
-**Version 0.1.0**, published on npm from a public repository.
+**Version 0.1.1**, published on npm from a public repository.
 
 From `0.1.0` the public API is settled and safe to depend on: the exported readers, builders,
 types and warning codes are the surface we keep stable, and the warning registry only ever gains
diff --git a/package.json b/package.json
index b99d1b3..7caf907 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@cosyte/x12",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Developer-focused ASC X12 healthcare EDI parser, serializer, and builder for Node.js and TypeScript: lenient on parse, spec-clean on emit.",
   "license": "MIT",
   "author": "Cosyte <hello@cosyte.com> (https://cosyte.com)",
diff --git a/src/index.ts b/src/index.ts
index 2b1d435..88bd845 100644
--- a/src/index.ts
+++ b/src/index.ts
@@ -18,7 +18,7 @@
  * console.log(VERSION);
  * ```
  */
-export const VERSION: string = "0.1.0";
+export const VERSION: string = "0.1.1";
 
 // The package's conformance declaration: which implementation guide each
 // reader and builder implements, which identifiers 45 CFR 162.920 names for