fractfs 0.1.0__tar.gz

fractfs-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,62 @@
+name: Publish to PyPI
+
+# Tag-triggered release: pushing a tag like v0.1.0 builds the package and
+# publishes it to PyPI via Trusted Publishing (OIDC) — no stored token.
+on:
+  push:
+    tags:
+      - "v*"
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    name: Build distributions
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install build tooling
+        run: python -m pip install --upgrade build twine
+
+      - name: Verify tag matches package version
+        run: |
+          TAG="${GITHUB_REF_NAME#v}"
+          PKG=$(python -c "import tomllib; print(tomllib.load(open('pyproject.toml','rb'))['project']['version'])")
+          echo "tag=$TAG package=$PKG"
+          if [ "$TAG" != "$PKG" ]; then
+            echo "::error::Tag $GITHUB_REF_NAME does not match pyproject version $PKG"
+            exit 1
+          fi
+
+      - name: Build sdist and wheel
+        run: python -m build
+
+      - name: Check metadata
+        run: twine check dist/*
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    name: Publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write  # required for Trusted Publishing (OIDC)
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish
+        uses: pypa/gh-action-pypi-publish@release/v1

fractfs-0.1.0/.gitignore

@@ -0,0 +1,22 @@
+# Local-only assistant notes
+CLAUDE.md
+plans/
+
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+build/
+dist/
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.coverage
+htmlcov/
+.venv/
+venv/
+.env
+
+# OS
+.DS_Store

fractfs-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

fractfs-0.1.0/PKG-INFO

@@ -0,0 +1,284 @@
+Metadata-Version: 2.4
+Name: fractfs
+Version: 0.1.0
+Summary: Drop-in tiered file storage for apps on ephemeral nodes: redirect big/durable files to Databricks Volumes or S3, checkpoint hot local state for restart safety.
+Project-URL: Homepage, https://github.com/isaac-harvey/fractfs
+Project-URL: Repository, https://github.com/isaac-harvey/fractfs
+Project-URL: Issues, https://github.com/isaac-harvey/fractfs/issues
+Author: Isaac Harvey
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: checkpoint,databricks,ephemeral,fsspec,tiered-storage,volumes
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: POSIX
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: System :: Filesystems
+Requires-Python: >=3.9
+Requires-Dist: pathspec>=0.11
+Requires-Dist: tomli>=2.0; python_version < '3.11'
+Provides-Extra: dev
+Requires-Dist: pytest-cov; extra == 'dev'
+Requires-Dist: pytest>=7; extra == 'dev'
+Requires-Dist: ruff; extra == 'dev'
+Provides-Extra: hashing
+Requires-Dist: xxhash>=3.0; extra == 'hashing'
+Provides-Extra: s3
+Requires-Dist: fsspec>=2023.1; extra == 's3'
+Requires-Dist: s3fs>=2023.1; extra == 's3'
+Description-Content-Type: text/markdown
+
+# fractfs
+
+**Drop-in tiered file storage for apps on ephemeral nodes.**
+
+`fractfs` lets an app with limited, ephemeral local disk transparently push large
+files to durable remote storage (Databricks Volumes primarily; S3 / any `fsspec`
+backend by extension) while keeping small hot state local, with periodic
+checkpoint/restore so a node stop/start doesn't lose data.
+
+The only change to your application is one line at startup:
+
+```python
+import fractfs
+fractfs.init()
+```
+
+plus a `.fractfs.toml` in the repo. No I/O interception, no monkeypatching — it
+works at the filesystem layer via symlinks, so it's library-agnostic (duckdb,
+polars, pyarrow, raw C all just work).
+
+## Why
+
+Apps moving from Posit Connect to Databricks Apps run on nodes with limited,
+ephemeral local disk. Large files don't fit and shouldn't live on the node, and
+anything written locally is lost when the node restarts. `fractfs` tags
+directories and files into tiers and provisions the filesystem so the right data
+lands in the right place — without intercepting I/O calls.
+
+## Install
+
+```bash
+pip install fractfs            # core (Databricks Volumes mount / local backend)
+pip install 'fractfs[s3]'      # + S3 / fsspec backends
+pip install 'fractfs[hashing]' # + xxhash content-based change detection
+```
+
+## Configuration
+
+A single `.fractfs.toml` at the app root:
+
+```toml
+[dirs]
+# Directories whose contents live on the Volume (durable remote store).
+# Directory-granular. New files created here later also land remote by default.
+paths = ["data/blobs", "exports", "cache/parquet"]
+
+[ignore]
+# gitignore-syntax. Matching files are NEVER synced/checkpointed.
+patterns = ["*.tmp", "__pycache__/", ".DS_Store"]
+
+[local]
+# gitignore-syntax. Matching files are "hot": they live on LOCAL disk
+# (fast, atomic rename) but ARE checkpointed for restore.
+patterns = ["*.meta.json", "manifest.json", "index.sqlite"]
+```
+
+### Environment variables
+
+| Var | Meaning | Example |
+|---|---|---|
+| `fractfs_BACKEND` | `volumes` \| `s3` \| `local` | `volumes` |
+| `fractfs_VOLUME_ROOT` | Mount root (or fsspec URL) for the remote store | `/Volumes/cat/schema/vol` |
+| `fractfs_SYNC_INTERVAL` | Checkpoint cadence (seconds) | `300` |
+| `fractfs_SCRATCH` | Node-local scratch root for back-symlink targets | `/tmp/fractfs` |
+| `fractfs_CHECKPOINT_SUBDIR` | Where checkpoints live under the Volume | `_checkpoint` |
+| `fractfs_CONTENT_HASH` | Use content hashing for change detection | `true` |
+| `fractfs_AUTO_IGNORE_BUNDLE` | Exclude the deploy bundle from the checkpoint | `true` |
+| `fractfs_ROOT` | App root holding `.fractfs.toml` | `/app` |
+
+Env vars override the TOML scalar fields. (Both `fractfs_` and `FRACTFS_`
+prefixes are accepted.)
+
+## The three tiers
+
+| Tier | Source | Lands | Checkpointed? | Mechanism |
+|---|---|---|---|---|
+| `dirs` | `[dirs].paths` | **Volume** | No (already durable) | directory symlink → `VOL/<dir>` |
+| `local` | `[local].patterns` | **Node** | **Yes** | pre-created back-symlink when inside a Volume dir |
+| `ignore` | `[ignore].patterns` | **Node** | **No** | back-symlink (kept off Volume) + sync walker skips |
+| *(default)* | everything else | **Node** | **Yes** | normal local disk, checkpointed |
+
+### Precedence (the load-bearing rule)
+
+When a path matches more than one tier, highest priority wins:
+
+1. **`ignore`** — never synced, stays local.
+2. **`local`** — stays local, synced.
+3. **`dirs`** — Volume redirect (the default for everything else under the dir).
+
+Patterns use gitignore syntax (via [`pathspec`](https://pypi.org/project/pathspec/))
+matched against the full relative path: `manifest.json` matches at any depth;
+`data/blobs/manifest.json` matches only there.
+
+## The `local` tier — what it is and is not
+
+`local` is for small files co-written with large blobs (a `manifest.json` next to
+`x.parquet`) that must survive restart but shouldn't take the FUSE cost of going
+direct-to-Volume. Local ext4 gives proper atomic `rename`; a Volume FUSE mount
+has real per-op overhead and weak atomicity, so for small mutable metadata
+local-tier is both faster and safer.
+
+**The limit:** `local` does **not** give blob↔metadata transactional
+consistency. On cold restart you restore a checkpoint up to
+`fractfs_SYNC_INTERVAL` seconds stale, while the blob on the Volume is current.
+Use `local` only for independent / rebuildable small state. If the small file is
+a pointer into the blob that must be exactly consistent, either put it in a
+`[dirs]` directory too (shared fate, accept the FUSE cost) or make it
+reconstructable from the blob on startup.
+
+### Keeping `local` files always-local (lock files, sqlite, manifests)
+
+A `[dirs]` directory is a symlink to the Volume, so files created inside it
+follow that link to the Volume *by default*. To keep a `local`/`ignore` file on
+fast node-local disk instead, fractfs places a **back-symlink** on the Volume
+that points at node-local scratch:
+
+```
+VOL/data/blobs/manifest.json  ->  $fractfs_SCRATCH/data/blobs/manifest.json
+```
+
+A symlink has to exist before the write to redirect it, so what fractfs can pin
+depends on whether it can predict the path:
+
+- **Exact filenames** (`manifest.json`, `index.sqlite`, or anchored
+  `data/blobs/manifest.json`) are pinned with a back-symlink **pre-created at
+  `init()`**, possibly dangling — so the file is local from its **very first
+  write**, no restart needed.
+- **Directory patterns** (a pattern ending in `/`, e.g. `.locks/`) pin a whole
+  subtree. *Any* filename created inside it lands local — this is the escape
+  hatch for lock files and other state with unpredictable names. Point the app at
+  a pinned subdirectory:
+
+  ```toml
+  [ignore]
+  patterns = [".locks/"]    # data/blobs/.locks/<anything> stays node-local
+  ```
+
+- **Globs** (`*.lock`, `*.tmp`) **cannot** be pre-pinned — fractfs can't know the
+  filename until the app creates it, and intercepting the write would mean
+  monkeypatching I/O (explicitly rejected). A `*.lock` created *directly* inside a
+  `[dirs]` dir therefore lands on the Volume. `init()` emits a warning (also in
+  `status()["warnings"]`) when a `[local]` glob could be affected.
+
+**The boundary, stated plainly:** anything that spawns sidecar files with names
+you don't control *next to* the data — a SQLite db emitting `-wal`/`-shm`, a
+library dropping `<name>.lock` beside the file it locks — should **not** live
+loose inside a `[dirs]` directory. Put that state in the default local tree (not
+under any `[dirs]` path) where it's plain local disk + checkpointed with all
+sidecars co-located, or confine it to a pinned `foo/` subdirectory.
+
+## Public API
+
+```python
+import fractfs
+
+fractfs.init()        # load config, provision symlinks, restore checkpoint, start sync
+# ... app runs unchanged ...
+fractfs.sync_now()    # force a checkpoint (e.g. before graceful shutdown)
+fractfs.status()      # tier of each tracked path, last sync time, etc.
+fractfs.shutdown()    # stop the sync daemon (runs a final checkpoint)
+```
+
+`init()` blocks on restore before returning, so the app never reads cold state.
+The provisioner refuses to replace a non-empty real local directory with a
+symlink unless you pass `fractfs.init(force=True)` (which migrates its contents
+to the Volume first).
+
+## The deploy bundle is auto-ignored
+
+The platform re-supplies your deployed app bundle (code, assets, `.fractfs.toml`)
+from the image on every cold start, so checkpointing it would copy your whole app
+to durable storage every interval for nothing. fractfs detects the bundle and
+excludes it automatically.
+
+**How:** at each `init()` (after provisioning, before restore) fractfs takes the
+set of files already present in the local tree and subtracts anything it already
+knows is runtime state (everything in the checkpoint manifest). On a cold
+ephemeral node the remainder is exactly the freshly-deployed bundle; on a warm /
+persistent disk the subtraction keeps real runtime files *out* of the bundle so
+they keep being checkpointed. It's recomputed every start, so it tracks redeploys
+that add or remove files with no config changes. `status()` reports
+`bundle_file_count`.
+
+**Turn it off** with `fractfs_AUTO_IGNORE_BUNDLE=false` (or `auto_ignore_bundle =
+false` in the TOML) if you want every local file checkpointed regardless.
+
+**Caveat (persistent disks only):** a runtime file created but never checkpointed
+before a restart that *survives* on a persistent local disk could be
+misclassified as bundle and then skipped. This can't happen on an ephemeral disk
+(uncheckpointed files are already gone), and a persistent local disk usually
+doesn't need the checkpoint anyway — but disable the feature if you rely on one.
+
+## Deploying on fast ephemeral disk (NVMe instance store)
+
+When a node has local NVMe, the cleanest layout is to put the **entire working
+directory on NVMe** — fastest possible disk for all hot state — and let fractfs
+divert big files to durable storage and checkpoint the rest. NVMe being wiped on
+stop/replace is exactly what the checkpoint covers.
+
+No new fractfs concept is needed: NVMe simply *becomes* the local disk. (NVMe is
+never a durable *target* — you never checkpoint *to* it; it's a fast, ephemeral
+*source* that gets checkpointed, the same role as the default local tree.)
+
+```bash
+# 1. NVMe instance store mounted at /mnt/nvme (instance/launch config).
+# 2. Run the app from there so the bundle and all writes live on NVMe.
+export fractfs_ROOT=/mnt/nvme/app
+export fractfs_SCRATCH=/mnt/nvme/app/.fractfs-scratch   # back-symlink targets on NVMe too
+# 3. Durable store for big files + checkpoints (NOT on NVMe):
+export fractfs_BACKEND=s3
+export fractfs_VOLUME_ROOT=s3://my-bucket/my-app
+export fractfs_SYNC_INTERVAL=300
+```
+
+```toml
+# /mnt/nvme/app/.fractfs.toml
+[dirs]
+paths = ["data/blobs", "exports"]   # big files -> S3, direct
+```
+
+Then:
+
+- **Big files** (`[dirs]`) go straight to S3 — never on NVMe, never checkpointed.
+- **Runtime state** (default tier) lives on fast NVMe and is checkpointed to S3.
+- **The bundle** is auto-ignored (re-supplied by the image each start).
+- **On cold start**, the platform re-extracts the bundle onto NVMe and fractfs
+  restores runtime state from the S3 checkpoint before your app reads anything.
+
+Two notes:
+
+- **Reads of the bundle stay local on NVMe; you don't need EBS for it.** Keep EBS
+  only if you genuinely want the bundle to *persist* (e.g. slow re-deploys) — and
+  if so, an OverlayFS mount (EBS lower, NVMe upper) gives "reads fall through to
+  EBS, all writes land on NVMe" transparently. That's an infra-level mount set up
+  before the app starts; fractfs composes on top of it unchanged.
+- **Splitting hot dirs across two local disks** (some on NVMe, some on EBS, at the
+  same time) is the one case that would need a future "fast-local redirect target"
+  tier. The single-disk layout above needs none of it.
+
+## Sharp edges
+
+- **Multi-replica.** Back-symlink targets are node-local; the link itself lives on
+  the Volume and is visible to other replicas. Fine for single-replica apps —
+  document/guard before running multiple replicas against the same Volume.
+- **FUSE atomicity.** Checkpoint writes use temp-file-then-`rename`. If your mount
+  doesn't honour atomic rename, the backend falls back to a plain copy.
+- **Change detection.** Default is size+mtime (cheap, can miss same-size edits).
+  Set `fractfs_CONTENT_HASH=true` (and install `fractfs[hashing]`) for content
+  hashing on correctness-sensitive trees.
+
+## License
+
+See [LICENSE](LICENSE).