honker 0.1.2 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 04f540681d13eb8cbd385ba2f43d121d5273b73dfde940cf7f689047278fe08d
-  data.tar.gz: 1073ccdb529b22484fe275fff403c019963983dc250d145e68ece63abbfcb92b
+  metadata.gz: 6d4ec2fd1faf6bbe935f087e8b6bcc28e875ee35c5c1212106d4d6fcf4e4eb70
+  data.tar.gz: fbec7fc3f448934b848f2aa4af73c257aacb2dbb6e2bfc1ce9a04944b2b5cff1
 SHA512:
-  metadata.gz: 4b1ae556c89d8b2bdb5c77bc45936e8f465fc62a65f691da4e137df0e066283f209ab88b8064026c6649caf3626ec200f3cb76766705ef3324ad6edeefbec602
-  data.tar.gz: b6d8be9a6527d9cd8feb1ae6e57467d4e1c5e619c44823aa984fb52296402b917ab0215cef008bbc6d22eb88a7b5ab79385afcad688b90593f76182dd9bea33f
+  metadata.gz: 8c20783f45f36b00c477c656843aa786b062990bc7b419034005a039dfce70705142716dda245168d3027e5f51e0c74091ce4bdaa9d3afb577745f999d9ee373
+  data.tar.gz: 75dd17ed09ca7ee424cf145f64a6d94abedfa960b6864001b6a7ef29cee2cd2e0338cc9a67abfe491dc36b83bbf913f6b26468ecfc07aaf54a93e18e8f8aa725

data/README.md

@@ -9,11 +9,202 @@ Full docs:
 
 ## Install
 
+Add it to your `Gemfile`:
+
+```ruby
+# Gemfile
+gem "honker"
+```
+
+then `bundle install`. Or install it directly:
+
+```sh
+gem install honker
+```
+
+Honker is a thin Ruby wrapper around a SQLite loadable extension
+written in Rust. How that extension reaches your gem install depends on
+your platform, with a fallback to compile the extension for other
+platforms.
+
+Most platforms (x86_64 and arm64 for Linux, arm64 for macOS) get a
+platform gem with the extension already built and bundled inside it:
+
+| Platform            | Triple          |
+| ------------------- | --------------- |
+| x86_64 Linux        | `x86_64-linux`  |
+| arm64 Linux         | `aarch64-linux` |
+| Apple Silicon macOS | `arm64-darwin`  |
+
+```sh
+gem install honker
+# Fetching honker-0.2.0-arm64-darwin.gem
+```
+
+`Honker::Database.new("app.db")` then finds the bundled extension
+automatically.
+
+### Where the bundled extension lives
+
+It is shipped inside the gem under `lib/honker/`, with a filename that
+follows the host OS's native shared-library convention:
+
+| Host OS | Extension file                   | Why this name                                |
+| ------- | -------------------------------- | -------------------------------------------- |
+| Linux   | `lib/honker/libhonker_ext.so`    | `lib` prefix, `.so` (shared object)          |
+| macOS   | `lib/honker/libhonker_ext.dylib` | `lib` prefix, `.dylib` (dynamic library)     |
+| Windows | `lib/honker/honker_ext.dll`      | no `lib` prefix, `.dll` (dynamic-link lib)   |
+
+`Honker::Database.new` checks the host OS at load time and resolves to
+the matching filename, so you usually do not need to think about it.
+You only see the difference if you build the extension yourself or set
+`HONKER_EXTENSION_PATH`, in which case the file you point at must match
+the OS the Ruby process is running on.
+
+To find the installed copy:
+
+```sh
+gem which honker            # => …/gems/honker-0.2.0-arm64-darwin/lib/honker.rb
+ls "$(dirname "$(gem which honker)")/honker"
+# libhonker_ext.dylib  ...
+```
+
+### Overriding the extension path
+
+To point at a different copy of the extension (a local dev build, a
+sidecar mounted into a container, a system path) pass `extension_path:`
+or set `HONKER_EXTENSION_PATH`; both override the bundled file.
+
+```ruby
+Honker::Database.new("app.db", extension_path: "./libhonker_ext.dylib")
+```
+
+```sh
+HONKER_EXTENSION_PATH=/opt/honker/libhonker_ext.so ruby app.rb
+```
+
+### Source gem (compiles on install, needs Rust)
+
+Every other platform (Intel macOS, Windows, anything else) gets the
+generic gem, which ships the Rust crate source and compiles the
+extension during `gem install`. Install [`rustc` and `cargo`](https://rustup.rs)
+first; otherwise the install fails with a clear message pointing at
+rustup.
+
+```sh
+gem install honker
+# Fetching honker-0.2.0.gem
+# Building native extensions. This could take a while...
+# honker: building the SQLite extension with cargo
+```
+
+The compiled artifact lands in the same `lib/honker/` directory as the
+prebuilt gems, so `Honker::Database.new` finds it the same way.
+
+### Installing from git
+
+`honker` lives in a subdirectory of a polyglot monorepo, so a `github:`
+dependency needs Bundler's `glob:` option to point at the gemspec. A
+git checkout has no prebuilt extension, so it always takes the
+compile-on-install path and needs `rustc`:
+
+```ruby
+# Gemfile
+gem "honker",
+    github: "russellromney/honker",
+    glob:   "packages/honker-ruby/honker.gemspec"
+```
+
+To pin to a branch, tag, or commit, add `branch:`, `tag:`, or `ref:`:
+
 ```ruby
+# Gemfile
+gem "honker",
+    github: "russellromney/honker",
+    glob:   "packages/honker-ruby/honker.gemspec",
+    branch: "main"
+```
+
+## Using Honker alongside an ORM
+
+`honker-ruby` opens its own `SQLite3::Database` handle (via the
+[`sqlite3`](https://rubygems.org/gems/sqlite3) gem) and loads the
+extension into it. To share a single SQLite file (and a single
+transaction) with Rails/ActiveRecord, Sequel, ROM, or Hanami::DB, get
+the underlying `sqlite3` gem connection your ORM is already using and
+load the Honker extension into that handle, so `honker_enqueue(...)`
+and friends are callable from inside one of its transactions.
+
+### Rails / ActiveRecord
+
+Point ActiveRecord at the bundled extension via `database.yml`:
+
+```yaml
+# config/database.yml
+production:
+  adapter: sqlite3
+  database: app.sqlite3
+  extensions:
+    - <%= Honker.extension_path %>
+```
+
+```ruby
+# Gemfile
 gem "honker"
 ```
 
-You also need the Honker SQLite extension from the main repo.
+That's it. `Honker::Railtie` runs `Honker.bootstrap` against
+`ActiveRecord::Base.connection` in `config.after_initialize`, so no
+initializer is required.
+
+Multi-database apps still need to call `Honker.bootstrap(some_other_conn)`
+themselves for non-primary connections.
+
+### Sequel (and ROM / Hanami::DB)
+
+`Honker.sequel_after_connect` returns the right `after_connect:` proc,
+so each new connection in the pool gets the extension loaded and the
+schema bootstrapped:
+
+```ruby
+require "sequel"
+require "honker"
+
+DB = Sequel.connect(
+  "sqlite://app.sqlite3",
+  after_connect: Honker.sequel_after_connect,
+)
+
+DB.synchronize do |conn|
+  conn.execute("SELECT honker_enqueue('emails', '{}', NULL, NULL, 0, 3, NULL)")
+end
+```
+
+To bootstrap once from a migration instead of on every connect, pass
+`bootstrap: false`:
+
+```ruby
+DB = Sequel.connect(
+  "sqlite://app.sqlite3",
+  after_connect: Honker.sequel_after_connect(bootstrap: false),
+)
+```
+
+### Setup helpers
+
+Both recipes above are built from the same module-level helpers, which
+wrap the extension-load and `honker_bootstrap()` ceremony:
+
+```ruby
+Honker.extension_path                  # => bundled path (or HONKER_EXTENSION_PATH override)
+Honker.load_extension(conn)            # enable_load_extension(true) → load → enable_load_extension(false)
+Honker.bootstrap(conn)                 # SELECT honker_bootstrap()
+Honker.setup(conn)                     # load_extension then bootstrap
+Honker.sequel_after_connect            # proc { |conn| Honker.setup(conn) } for Sequel/Rom/Hanami
+```
+
+See the per-ORM walkthroughs at
+[honker.dev/guides/orm/ruby](https://honker.dev/guides/orm/ruby/).
 
 ## Watcher backends
 
@@ -28,7 +219,7 @@ the matching feature.
 ```ruby
 require "honker"
 
-db = Honker::Database.new("app.db", extension_path: "./libhonker_ext.dylib")
+db = Honker::Database.new("app.db")
 q = db.queue("emails")
 
 q.enqueue({to: "alice@example.com"})

data/ext/honker/extconf.rb

@@ -0,0 +1,69 @@
+# frozen_string_literal: true
+#
+# Builds the Honker SQLite loadable extension when the generic (source)
+# gem is installed. Precompiled platform gems ship the extension and do
+# not run this. A Rust toolchain is required; see https://rustup.rs.
+#
+# RubyGems runs this script and then `make`. It does the cargo build
+# itself, drops the artifact in lib/honker/, and writes a no-op Makefile.
+
+require "rbconfig"
+require "fileutils"
+
+ext_dir = __dir__
+
+manifest = [
+  File.join(ext_dir, "honker-extension", "Cargo.toml"),                 # vendored in the gem
+  File.expand_path("../../../../honker-extension/Cargo.toml", ext_dir), # repo checkout (github:)
+].find { |path| File.file?(path) }
+
+if manifest.nil?
+  abort "honker: honker-extension crate source not found; cannot build the extension"
+end
+
+cargo_found = system("cargo", "--version", out: File::NULL, err: File::NULL)
+unless cargo_found
+  abort <<~MSG
+    honker: cannot build the SQLite extension because the Rust toolchain
+    (cargo) was not found on PATH.
+
+    This is the honker source gem; it compiles the extension on install.
+    To fix this, either:
+      * install Rust from https://rustup.rs and reinstall honker, or
+      * use a precompiled platform gem (published for x86_64 Linux,
+        arm64 Linux, and Apple Silicon macOS).
+  MSG
+end
+
+ext_name =
+  case RbConfig::CONFIG.fetch("host_os")
+  when /mswin|mingw|cygwin/ then "honker_ext.dll"
+  when /darwin/ then "libhonker_ext.dylib"
+  else "libhonker_ext.so"
+  end
+
+target_dir = File.join(ext_dir, "target")
+
+puts "honker: building the SQLite extension with cargo"
+system(
+  { "CARGO_TARGET_DIR" => target_dir },
+  "cargo", "build", "--release", "--manifest-path", manifest,
+  exception: true,
+)
+
+artifact = File.join(target_dir, "release", ext_name)
+abort "honker: cargo build did not produce #{artifact}" unless File.file?(artifact)
+
+dest_dir = File.expand_path("../../lib/honker", ext_dir)
+FileUtils.mkdir_p(dest_dir)
+FileUtils.cp(artifact, File.join(dest_dir, ext_name))
+FileUtils.rm_rf(target_dir)
+puts "honker: extension ready at lib/honker/#{ext_name}"
+
+# RubyGems runs `make` after this script; the build is already done, so
+# the Makefile only needs targets that succeed as no-ops.
+File.write(File.join(ext_dir, "Makefile"), <<~MAKEFILE)
+  all:
+  clean:
+  install:
+MAKEFILE

data/ext/honker/honker-core/Cargo.toml

@@ -0,0 +1,49 @@
+[package]
+name = "honker-core"
+version = "0.2.3"
+edition = "2024"
+description = "Shared Rust foundation for Honker bindings (SQLite loadable extension, PyO3, napi-rs, and friends). Not intended for direct use."
+license = "MIT OR Apache-2.0"
+repository = "https://github.com/russellromney/honker"
+homepage = "https://honker.dev"
+readme = "README.md"
+keywords = ["sqlite", "queue", "pubsub", "notify", "honker"]
+categories = ["database", "concurrency"]
+
+[features]
+bundled-sqlite = ["rusqlite/bundled"]
+# Optional kernel-watch backend: use OS filesystem notifications as wake
+# hints (still verifies via PRAGMA data_version). Experimental.
+kernel-watcher = ["dep:libc", "dep:notify"]
+# Optional shm fast path: read the SQLite WAL index shared-memory file
+# directly instead of running PRAGMA data_version. Experimental.
+shm-fast-path = ["dep:memmap2"]
+
+[lib]
+name = "honker_core"
+# Plain rlib — no cdylib, no Python/Node/C ABI here. Consumed as a
+# regular Cargo dependency by the three binding crates.
+
+[dependencies]
+chrono = { version = "0.4", default-features = false, features = ["clock"] }
+parking_lot = "0.12.5"
+rusqlite = { version = "0.39.0", features = ["functions", "hooks"] }
+thiserror = "2.0.18"
+# Optional: kernel-watch backend.
+# macos_kqueue: on macOS, use kqueue (RecommendedWatcher = KqueueWatcher) instead of
+# FSEvents. FSEvents has a 1 s batching latency — worse than 1 ms polling. kqueue
+# delivers per-event notifications immediately, matching the intent of this backend.
+notify = { version = "6", optional = true, features = ["macos_kqueue"] }
+# Optional: shm fast path.
+memmap2 = { version = "0.9", optional = true }
+libc = { version = "0.2", optional = true }
+
+# file-id only supports unix and windows. Other targets (WASI, Redox,
+# illumos, etc.) get the `(0, 0)` fallback in stat_identity.
+[target.'cfg(any(unix, windows))'.dependencies]
+file-id = "0.2.3"
+
+[dev-dependencies]
+# chrono-tz only in tests — lets us exercise DST edge cases with a
+# fixed timezone (US/Eastern) regardless of where tests run.
+chrono-tz = "0.10"

data/ext/honker/honker-core/LICENSE

@@ -0,0 +1,6 @@
+Honker is licensed under either of:
+
+* Apache License, Version 2.0 (LICENSE-APACHE or https://www.apache.org/licenses/LICENSE-2.0)
+* MIT license (LICENSE-MIT or https://opensource.org/licenses/MIT)
+
+at your option.

data/ext/honker/honker-core/LICENSE-APACHE

@@ -0,0 +1,176 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction,
+and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by
+the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all
+other entities that control, are controlled by, or are under common
+control with that entity. For the purposes of this definition,
+"control" means (i) the power, direct or indirect, to cause the
+direction or management of such entity, whether by contract or
+otherwise, or (ii) ownership of fifty percent (50%) or more of the
+outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity
+exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications,
+including but not limited to software source code, documentation
+source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical
+transformation or translation of a Source form, including but
+not limited to compiled object code, generated documentation,
+and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or
+Object form, made available under the License, as indicated by a
+copyright notice that is included in or attached to the work
+(an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object
+form, that is based on (or derived from) the Work and for which the
+editorial revisions, annotations, elaborations, or other modifications
+represent, as a whole, an original work of authorship. For the purposes
+of this License, Derivative Works shall not include works that remain
+separable from, or merely link (or bind by name) to the interfaces of,
+the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including
+the original version of the Work and any modifications or additions
+to that Work or Derivative Works thereof, that is intentionally
+submitted to Licensor for inclusion in the Work by the copyright owner
+or by an individual or Legal Entity authorized to submit on behalf of
+the copyright owner. For the purposes of this definition, "submitted"
+means any form of electronic, verbal, or written communication sent
+to the Licensor or its representatives, including but not limited to
+communication on electronic mailing lists, source code control systems,
+and issue tracking systems that are managed by, or on behalf of, the
+Licensor for the purpose of discussing and improving the Work, but
+excluding communication that is conspicuously marked or otherwise
+designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity
+on behalf of whom a Contribution has been received by Licensor and
+subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+copyright license to reproduce, prepare Derivative Works of,
+publicly display, publicly perform, sublicense, and distribute the
+Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+(except as stated in this section) patent license to make, have made,
+use, offer to sell, sell, import, and otherwise transfer the Work,
+where such license applies only to those patent claims licensable
+by such Contributor that are necessarily infringed by their
+Contribution(s) alone or by combination of their Contribution(s)
+with the Work to which such Contribution(s) was submitted. If You
+institute patent litigation against any entity (including a
+cross-claim or counterclaim in a lawsuit) alleging that the Work
+or a Contribution incorporated within the Work constitutes direct
+or contributory patent infringement, then any patent licenses
+granted to You under this License for that Work shall terminate
+as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+Work or Derivative Works thereof in any medium, with or without
+modifications, and in Source or Object form, provided that You
+meet the following conditions:
+
+(a) You must give any other recipients of the Work or
+Derivative Works a copy of this License; and
+
+(b) You must cause any modified files to carry prominent notices
+stating that You changed the files; and
+
+(c) You must retain, in the Source form of any Derivative Works
+that You distribute, all copyright, patent, trademark, and
+attribution notices from the Source form of the Work,
+excluding those notices that do not pertain to any part of
+the Derivative Works; and
+
+(d) If the Work includes a "NOTICE" text file as part of its
+distribution, then any Derivative Works that You distribute must
+include a readable copy of the attribution notices contained
+within such NOTICE file, excluding those notices that do not
+pertain to any part of the Derivative Works, in at least one
+of the following places: within a NOTICE text file distributed
+as part of the Derivative Works; within the Source form or
+documentation, if provided along with the Derivative Works; or,
+within a display generated by the Derivative Works, if and
+wherever such third-party notices normally appear. The contents
+of the NOTICE file are for informational purposes only and
+do not modify the License. You may add Your own attribution
+notices within Derivative Works that You distribute, alongside
+or as an addendum to the NOTICE text from the Work, provided
+that such additional attribution notices cannot be construed
+as modifying the License.
+
+You may add Your own copyright statement to Your modifications and
+may provide additional or different license terms and conditions
+for use, reproduction, or distribution of Your modifications, or
+for any such Derivative Works as a whole, provided Your use,
+reproduction, and distribution of the Work otherwise complies with
+the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+any Contribution intentionally submitted for inclusion in the Work
+by You to the Licensor shall be under the terms and conditions of
+this License, without any additional terms or conditions.
+Notwithstanding the above, nothing herein shall supersede or modify
+the terms of any separate license agreement you may have executed
+with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+names, trademarks, service marks, or product names of the Licensor,
+except as required for reasonable and customary use in describing the
+origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+agreed to in writing, Licensor provides the Work (and each
+Contributor provides its Contributions) on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+implied, including, without limitation, any warranties or conditions
+of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+PARTICULAR PURPOSE. You are solely responsible for determining the
+appropriateness of using or redistributing the Work and assume any
+risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+whether in tort (including negligence), contract, or otherwise,
+unless required by applicable law (such as deliberate and grossly
+negligent acts) or agreed to in writing, shall any Contributor be
+liable to You for damages, including any direct, indirect, special,
+incidental, or consequential damages of any character arising as a
+result of this License or out of the use or inability to use the
+Work (including but not limited to damages for loss of goodwill,
+work stoppage, computer failure or malfunction, or any and all
+other commercial damages or losses), even if such Contributor
+has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+the Work or Derivative Works thereof, You may choose to offer,
+and charge a fee for, acceptance of support, warranty, indemnity,
+or other liability obligations and/or rights consistent with this
+License. However, in accepting such obligations, You may act only
+on Your own behalf and on Your sole responsibility, not on behalf
+of any other Contributor, and only if You agree to indemnify,
+defend, and hold each Contributor harmless for any liability
+incurred by, or claims asserted against, such Contributor by reason
+of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS

data/ext/honker/honker-core/LICENSE-MIT

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Russell Romney
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

data/ext/honker/honker-core/README.md

@@ -0,0 +1,30 @@
+# honker-core
+
+Shared Rust foundation for [Honker](https://honker.dev) bindings. Not intended for direct use — consumed by `honker-extension` (the SQLite loadable extension), the Python binding, `honker-node`, `honker-rs`, and future bindings.
+
+If you want to *use* Honker:
+
+| Language | Package | Repo |
+|---|---|---|
+| Any SQLite client | `honker-extension` on crates.io (or prebuilt `.dylib`/`.so`) | [russellromney/honker](https://github.com/russellromney/honker) |
+| Rust | `honker` on crates.io | [russellromney/honker-rs](https://github.com/russellromney/honker-rs) |
+| Python | `pip install honker` | (inside the main repo) |
+| Node | `@honker/node` on npm | [russellromney/honker-node](https://github.com/russellromney/honker-node) |
+| Go | `go get github.com/russellromney/honker-go` | [russellromney/honker-go](https://github.com/russellromney/honker-go) |
+| Ruby | `gem install honker` | [russellromney/honker-ruby](https://github.com/russellromney/honker-ruby) |
+| Elixir | `{:honker, "~> 0.1"}` | [russellromney/honker-ex](https://github.com/russellromney/honker-ex) |
+| Bun | `bun add honker-bun` | [russellromney/honker-bun](https://github.com/russellromney/honker-bun) |
+
+## What this crate provides
+
+- `open_conn(path, install_notify)` — open a SQLite connection with Honker's PRAGMA defaults and optional `notify()` install.
+- `attach_notify(conn)` — register the `notify()` SQL scalar + `_honker_notifications` table.
+- `attach_honker_functions(conn)` — register every `honker_*` SQL scalar (queues, streams, scheduler, rate limits, locks, results).
+- `bootstrap_honker_schema(conn)` — idempotent DDL for all `_honker_*` tables.
+- `Writer` / `Readers` — single-writer slot + bounded reader pool with blocking and non-blocking acquire.
+- `SharedUpdateWatcher` — one PRAGMA-polling thread per database fanning out to N subscribers.
+- `cron::next_after_unix(expr, from_unix)` — standard 5-field crontab parser + next-fire calculator with local-TZ + DST handling.
+
+## License
+
+Apache-2.0.