okf-pro 1.1.0 → 1.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a908d8394cc7ea78e25a744f080813d34eb656b77274e3bb8db4397d222c3950
-  data.tar.gz: 687919c65db7bf0d42bc48f475cd88f636c01aaf87f49443d92c6de0fd434fb9
+  metadata.gz: 5aa082e7d1ee662bf38b9f16302377b930e9739766dfd24921b5b42867f8c5de
+  data.tar.gz: 30f2caaa6dc5a517dd80ca2b8869946332f7da11513db3ef4d8370da921bc623
 SHA512:
-  metadata.gz: '0589ad1bd8edb04b767044692d20b271614fe37d60f598fe1b51ba436384142049da27d94d8281df54b0a485b658751e7ef2fe3d4c84a292b4593a61502d6c87'
-  data.tar.gz: 7afe1c08143bf0524f9deb5ce47e827276b59aa805f62cb65b2be5e5414bb542b1208a4b2a59826443ab1fde4e5680066fd047e6236007afc8b3e1b0e04e7ae3
+  metadata.gz: 196051ae74e6a129bb82f99b8865d827f9b12ccc27d1b7a51784b2227c412baf867a5df26e13536d7e35b63196cbcb7601638f7f7876fdd7d73734bfb73e17ab
+  data.tar.gz: 9105128a81dfa9e195395ebb3de2759c4c64b9d4f93ce77ed87d5dd36a02299c9d9f642da913f5e0590f62b19af422f6ef710ae29bd91755dfb59a86dd0036f5

data/.okf/capabilities/verbs.md

@@ -37,6 +37,16 @@ the two together.
 It does not go through `dir_argument`: `setup` into an empty directory is the
 whole point, and refusing one that holds no bundle would refuse every first run.
 
+It does go through `parse_flags`, and for a while it was the only family that
+did not. `--help` therefore reached the verb as its destination, and the
+generator answered the question by running. `setup --help` wrote twenty-five
+seed files into a directory named `--help`. `upgrade --help` rewrote the four
+gem-owned files of whatever repository you were standing in, because `upgrade`
+defaults its destination to the working directory. Both exited 0.
+
+None of the three declares a flag, and none needs a `FLAGS` entry to refuse
+one: absence from that table already means "accepts none".
+
 **Readers** (`audit`, `records`, `snapshot`, `unverified`, `state`, `board`,
 `friction`) answer questions. Every one of them routes through `parse_flags`,
 listed in `FLAGS` or not — because absence from that table means "accepts none",

data/.okf/log.md

@@ -1,5 +1,17 @@
 # Update Log
 
+## 2026-08-30
+
+* **The scaffold verbs go through `parse_flags` too, and the catalogue says so.**
+  [capabilities/verbs](/capabilities/verbs.md) described the family by what it
+  does *not* do: no `dir_argument`, because `setup` into an empty directory is
+  the point. That omission read as an exemption from the parser as well, and it
+  was one. `--help` reached the verb as its destination, so the generator
+  answered the question by running. The paragraph now names both halves, and
+  [testing/adding-a-verb](/testing/adding-a-verb.md) step 5 says it too. **A
+  family defined only by its exception gets extended in the direction of the
+  exception**, and the next reader pays for that.
+
 ## 2026-08-19
 
 * **Every concept declares `generated:`.** The dates are read from git with

data/.okf/testing/adding-a-verb.md

@@ -39,7 +39,9 @@ its caller's typo as a broken bundle; a check that returns 1 is read as
    would make every `okf help` load the whole library — and they are held
    together by a test rather than by discipline.
 5. **Declare its flags** in `FLAGS` if it takes any. Absence means "accepts
-   none", not "is exempt": every reader routes through `parse_flags` either way.
+   none", not "is exempt". Every reader routes through `parse_flags` either
+   way, and so does every scaffold verb — that second half cost a release to
+   become true.
 6. **A writer owes a pure transform.** Compute the new text in `board/edit.rb`
    or `log/edit.rb` — they cannot touch the disk — declare the added, removed
    and moved lines, and let `Conserve` refuse the mismatch. See

data/CHANGELOG.md

@@ -4,6 +4,32 @@ All notable changes to okf-pro are documented here. The format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this gem uses
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.1.1] - 2026-08-30
+
+### Fixed
+
+- **`okf pro setup --help` prints the usage instead of running the generator.**
+  The three scaffold verbs read their destination from `argv.shift` and never
+  reached `parse_flags`. The flag was therefore the destination. `setup --help`
+  wrote the twenty-five seed files into a directory named `--help` and exited 0.
+  `upgrade --help` was worse: `upgrade` defaults its destination to the working
+  directory, so it rewrote the four gem-owned files of whatever repository you
+  were standing in.
+
+  A help flag that answers the question by running the verb is the worst shape
+  it can have. This is the one family where the answer is files on disk.
+
+  The fix routes the three verbs through the parser the readers already use.
+  None of them declares a flag, and none gains a `FLAGS` entry. Absence from
+  that table already means "accepts none" rather than "is exempt", so `setup
+  --json` is now a typo the parser names. Before, it was a seeded repository in
+  a directory with a leading dash. `--` still separates a destination from the
+  flags, for the rare path that starts with one.
+
+  The write verbs carried this defect and fixed it: `okf pro capture --help`
+  once appended `- <date> — --help` to the Inbox. The scaffold verbs are the
+  last family nobody had checked for it.
+
 ## [1.1.0] - 2026-08-22
 
 ### Changed
@@ -250,5 +276,7 @@ every use. This surface answers both.
 - **The `.bin/okf_pro` binary is gone.** `okf pro` is the only door, which is
   what lets the wrapper refuse anything that is not it.
 
+[1.1.1]: https://github.com/serradura/okf/compare/okf-pro/v1.1.0...okf-pro/v1.1.1
+[1.1.0]: https://github.com/serradura/okf/compare/okf-pro/v1.0.1...okf-pro/v1.1.0
 [1.0.1]: https://github.com/serradura/okf/compare/okf-pro/v1.0.0...okf-pro/v1.0.1
 [1.0.0]: https://github.com/serradura/okf/releases/tag/okf-pro%2Fv1.0.0

data/lib/okf/plugin.rb

@@ -75,8 +75,6 @@ module OKF
       # rather than swallowed — `okf/pro.rb` refuses an under-floor Ruby with
       # `exit 2`, and a rescue that turned that refusal into an error report
       # would be the fail-open this method exists to close.
-      #
-      # rubocop:disable Lint/RescueException
       def call(argv)
         verb = argv.first.to_s
 
@@ -93,10 +91,9 @@ module OKF
         status.is_a?(Integer) ? status : blocked("returned #{status.inspect} instead of an exit status")
       rescue ::SystemExit
         raise
-      rescue ::Exception => e
+      rescue ::Exception => e # rubocop:disable Lint/RescueException
         blocked("#{e.class}: #{e.message}")
       end
-      # rubocop:enable Lint/RescueException
 
       private
 

data/lib/okf/pro/cli.rb

@@ -795,6 +795,18 @@ module OKF
       end
 
       def scaffold(verb, argv, stdout: $stdout, stderr: $stderr)
+        # The one verb group that used to skip the parser, and the one where
+        # skipping it was worst: `--help` became the destination, so asking
+        # what the generator does ran it, into a directory called `--help`.
+        #
+        # No `FLAGS` entry, deliberately — absence already means "accepts
+        # none", and `parse_flags` refuses an undeclared flag either way. An
+        # empty entry would say these three verbs were considered and given
+        # nothing, which is a distinction this table does not draw for `audit`
+        # or `records` either.
+        options = parse_flags(argv, verb, stdout, stderr)
+        return options == :handled ? PASS : BLOCK unless options.is_a?(Hash)
+
         dest = argv.shift
 
         unless argv.empty?

data/lib/okf/pro/version.rb

@@ -2,6 +2,6 @@
 
 module OKF
   module Pro
-    VERSION = "1.1.0"
+    VERSION = "1.1.1"
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: okf-pro
 version: !ruby/object:Gem::Version
-  version: 1.1.0
+  version: 1.1.1
 platform: ruby
 authors:
 - Rodrigo Serradura
@@ -174,7 +174,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 4.0.16
+rubygems_version: 4.0.10
 specification_version: 4
 summary: 'A profile of OKF: one opinionated shape of knowledge bundle, and the gates
   that hold it there. Structure for making things happen.'