specmod 0.2.3__tar.gz → 0.4.0__tar.gz

{specmod-0.2.3 → specmod-0.4.0}/.github/workflows/build.yml

@@ -10,10 +10,14 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
         with:
           fetch-depth: 0   # hatch-vcs derives the version from tags
-      - uses: astral-sh/setup-uv@v5
+      # Pinned to a full version, unlike the other three. `astral-sh/setup-uv`
+      # publishes no bare major tag — `@v10` does not resolve, and using it
+      # fails every job at "Getting action download info", before a step runs.
+      # Bump this deliberately; do not "tidy" it to `@v10`.
+      - uses: astral-sh/setup-uv@v10.0.1
       - run: uv python install 3.11
 
       - name: Build sdist and wheel
@@ -34,7 +38,7 @@ jobs:
           print('specmod', specmod.__version__, '- wheel imports cleanly')
           "
 
-      - uses: actions/upload-artifact@v4
+      - uses: actions/upload-artifact@v7
         with:
           name: dist
           path: dist/

{specmod-0.2.3 → specmod-0.4.0}/.github/workflows/docs.yml

@@ -24,10 +24,14 @@ jobs:
   docs:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
         with:
           fetch-depth: 0   # hatch-vcs derives the version from tags
-      - uses: astral-sh/setup-uv@v5
+      # Pinned to a full version, unlike the other three. `astral-sh/setup-uv`
+      # publishes no bare major tag — `@v10` does not resolve, and using it
+      # fails every job at "Getting action download info", before a step runs.
+      # Bump this deliberately; do not "tidy" it to `@v10`.
+      - uses: astral-sh/setup-uv@v10.0.1
       - run: uv python install 3.11
       - run: uv venv # create a venv to install into
 
@@ -50,7 +54,7 @@ jobs:
 
       # Not a Pages artefact: this is a plain zip anyone can download from the
       # run and open locally, and it stays useful if Read the Docs is down.
-      - uses: actions/upload-artifact@v4
+      - uses: actions/upload-artifact@v7
         with:
           name: docs-html
           path: docs/_build/html

{specmod-0.2.3 → specmod-0.4.0}/.github/workflows/release.yml

@@ -77,7 +77,7 @@ jobs:
       id-token: write   # mandatory for Trusted Publishing
       contents: read
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
         with:
           # The tag, not the branch. main has already moved on by one commit
           # (the release PR merge), and hatch-vcs would derive a .postN.devN
@@ -85,7 +85,11 @@ jobs:
           ref: ${{ needs.release-please.outputs.tag_name }}
           fetch-depth: 0   # hatch-vcs derives the version by describing tags
 
-      - uses: astral-sh/setup-uv@v5
+      # Pinned to a full version, unlike the other three. `astral-sh/setup-uv`
+      # publishes no bare major tag — `@v10` does not resolve, and using it
+      # fails every job at "Getting action download info", before a step runs.
+      # Bump this deliberately; do not "tidy" it to `@v10`.
+      - uses: astral-sh/setup-uv@v10.0.1
       - run: uv python install 3.11
       - run: uv build
 

{specmod-0.2.3 → specmod-0.4.0}/.github/workflows/test.yml

@@ -14,8 +14,12 @@ jobs:
   lint:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
-      - uses: astral-sh/setup-uv@v5
+      - uses: actions/checkout@v7
+      # Pinned to a full version, unlike the other three. `astral-sh/setup-uv`
+      # publishes no bare major tag — `@v10` does not resolve, and using it
+      # fails every job at "Getting action download info", before a step runs.
+      # Bump this deliberately; do not "tidy" it to `@v10`.
+      - uses: astral-sh/setup-uv@v10.0.1
         with:
           enable-cache: true
       - run: uv python install 3.11
@@ -28,10 +32,14 @@ jobs:
   typecheck:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
         with:
           fetch-depth: 0   # hatch-vcs needs history to derive the version
-      - uses: astral-sh/setup-uv@v5
+      # Pinned to a full version, unlike the other three. `astral-sh/setup-uv`
+      # publishes no bare major tag — `@v10` does not resolve, and using it
+      # fails every job at "Getting action download info", before a step runs.
+      # Bump this deliberately; do not "tidy" it to `@v10`.
+      - uses: astral-sh/setup-uv@v10.0.1
         with:
           enable-cache: true
       - run: uv python install 3.11
@@ -48,10 +56,14 @@ jobs:
         os: [ubuntu-latest, macos-latest]
         python-version: ["3.11", "3.12", "3.13"]
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
         with:
           fetch-depth: 0
-      - uses: astral-sh/setup-uv@v5
+      # Pinned to a full version, unlike the other three. `astral-sh/setup-uv`
+      # publishes no bare major tag — `@v10` does not resolve, and using it
+      # fails every job at "Getting action download info", before a step runs.
+      # Bump this deliberately; do not "tidy" it to `@v10`.
+      - uses: astral-sh/setup-uv@v10.0.1
         with:
           enable-cache: true
       - run: uv python install ${{ matrix.python-version }}
@@ -64,7 +76,7 @@ jobs:
         # execution is excluded because it costs ~40s and a Jupyter kernel, and
         # is worth paying once rather than six times — see the notebook job.
         run: uv run pytest -m "not dataset and not notebook" --cov=specmod --cov-report=xml --cov-report=term
-      - uses: codecov/codecov-action@v4
+      - uses: codecov/codecov-action@v7
         if: matrix.os == 'ubuntu-latest' && matrix.python-version == '3.11'
         with:
           files: coverage.xml
@@ -73,10 +85,14 @@ jobs:
   floors:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
         with:
           fetch-depth: 0
-      - uses: astral-sh/setup-uv@v5
+      # Pinned to a full version, unlike the other three. `astral-sh/setup-uv`
+      # publishes no bare major tag — `@v10` does not resolve, and using it
+      # fails every job at "Getting action download info", before a step runs.
+      # Bump this deliberately; do not "tidy" it to `@v10`.
+      - uses: astral-sh/setup-uv@v10.0.1
       - run: uv python install 3.11
       - run: uv venv
       # Exercise the declared minimums. CI otherwise installs the newest of
@@ -92,10 +108,14 @@ jobs:
     # third kind, so it runs per-PR rather than at release.
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
         with:
           fetch-depth: 0
-      - uses: astral-sh/setup-uv@v5
+      # Pinned to a full version, unlike the other three. `astral-sh/setup-uv`
+      # publishes no bare major tag — `@v10` does not resolve, and using it
+      # fails every job at "Getting action download info", before a step runs.
+      # Bump this deliberately; do not "tidy" it to `@v10`.
+      - uses: astral-sh/setup-uv@v10.0.1
         with:
           enable-cache: true
       - run: uv python install 3.11

{specmod-0.2.3 → specmod-0.4.0}/.pre-commit-config.yaml

@@ -36,12 +36,18 @@ repos:
       # running the hooks over one silently stripped six bytes from the middle
       # of it — a corrupted pickle that still looks like a plausible diff.
       # Anything binary has to be excluded by hand; the hooks do not detect it.
+      #
+      # The two vendored directories under `docs/_static/` are excluded for
+      # both reasons at once. Their `.woff2` files are binary, and the licences
+      # beside them have to stay byte identical to what upstream publishes —
+      # `trailing-whitespace` edited Merriweather's OFL the first time it was
+      # staged, which is a licence rewritten to satisfy a linter.
       - id: end-of-file-fixer
-        exclude: '\.spec$'
+        exclude: &verbatim '(\.spec$|^docs/_static/(fonts|katex)/)'
       - id: trailing-whitespace
-        exclude: '\.spec$'
+        exclude: *verbatim
       - id: mixed-line-ending
-        exclude: '\.spec$'
+        exclude: *verbatim
 
   - repo: https://github.com/kynan/nbstripout
     rev: 0.8.1

specmod-0.4.0/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "0.4.0"
+}

{specmod-0.2.3 → specmod-0.4.0}/CHANGELOG.md

@@ -9,6 +9,65 @@ release could have this problem — every later one has a real predecessor tag
 so leave subsequent headings as generated. release-please only prepends to this
 file, so this edit survives. -->
 
+## [0.4.0](https://github.com/sgjholt/SpecMod/compare/v0.3.0...v0.4.0) (2026-09-16)
+
+
+### Features
+
+* **smoothing:** wire [smoothing] method up, and add three more methods ([fff3ab1](https://github.com/sgjholt/SpecMod/commit/fff3ab1ef01a7f4d942fd776821d0418a0642a55))
+
+
+### Bug Fixes
+
+* **config:** refuse a [smoothing] method the pipeline does not apply ([1f18c68](https://github.com/sgjholt/SpecMod/commit/1f18c68a71794c2b1612a7cf0feedcfef39b625b))
+* **test:** compare the roadmap against the published minor, not the proposed one ([1e34b4e](https://github.com/sgjholt/SpecMod/commit/1e34b4e5ab2bdef5d65f6fc0d620a42b9c3891eb))
+* **tools:** call the preprocess API that 0.3.0 left behind ([8501c8e](https://github.com/sgjholt/SpecMod/commit/8501c8ed618e5d652b9eeffc36893115a58fd7d5))
+
+
+### Documentation
+
+* keep the reasoning out of the docstrings, in comments where it belongs ([2684ec9](https://github.com/sgjholt/SpecMod/commit/2684ec923c8dcf59e882b2d11e9dc11ccbcf3766))
+* say what tagging the frozen commit does and does not trigger ([2273219](https://github.com/sgjholt/SpecMod/commit/2273219e2a78ac1c1562118c2a1b3bce4df597dd))
+* state what the smoothers are, not how they were arrived at ([4c97491](https://github.com/sgjholt/SpecMod/commit/4c97491d50aba5a1468304072ab3c6ed2904f2e0))
+* the 0.3.0 work shipped a week ago, so stop calling it unreleased ([e2aaced](https://github.com/sgjholt/SpecMod/commit/e2aaced546a247b2c5967f01586c19928bcfe297))
+* v0.1.1 is master's tip, which is what freezing it was for ([db50972](https://github.com/sgjholt/SpecMod/commit/db509729f3b7877a20b5691dddec8a6e139fb466))
+
+## [0.3.0](https://github.com/sgjholt/SpecMod/compare/v0.2.3...v0.3.0) (2026-09-06)
+
+
+### ⚠ BREAKING CHANGES
+
+* the tutorial page moves from `/tutorial/SpecModTutorial.html` to `/tutorial/specmod-tutorial.html`.
+* the ten mutating functions in `specmod.preprocess` are renamed and now return a new stream or trace. `get_signal` is removed, and the two undated deprecation shims are gone.
+
+### Features
+
+* let the fitted band be capped, fixed or corrected by hand ([ba241a9](https://github.com/sgjholt/SpecMod/commit/ba241a95d94a298418b3c6f414a0026b9f310926))
+* preprocess returns new streams instead of mutating ([78aabeb](https://github.com/sgjholt/SpecMod/commit/78aabeb4856eda4208787fcd53b0df77bc50bd1c))
+
+
+### Bug Fixes
+
+* give the noise and bandwidth registries a documented home ([daeb2cc](https://github.com/sgjholt/SpecMod/commit/daeb2cc43eff2869e9617e4111f281f9bd4d33bb))
+* **transforms:** re-export every public name from base ([67c24c3](https://github.com/sgjholt/SpecMod/commit/67c24c3dda80f7fbc1bd51861861bde48d943eac))
+
+
+### Code Refactoring
+
+* **docs:** build the tutorial from a script too ([de846c6](https://github.com/sgjholt/SpecMod/commit/de846c6128fc7922df8e1e3c2c1c01f2b8bf95bb))
+* **docs:** one notebook builder per notebook, named after it ([0175f89](https://github.com/sgjholt/SpecMod/commit/0175f890f5f92668341a17bece7149f7d8f8c6b7))
+* split io and plotting into packages ([027b77f](https://github.com/sgjholt/SpecMod/commit/027b77f7d050716b7d98fc873a8a4e93098d1d68))
+
+
+### Documentation
+
+* adopt the academic theme from the branding manual ([76f0aa0](https://github.com/sgjholt/SpecMod/commit/76f0aa0a40a134eeb91b8ada04c8f5fa66243c54))
+* kebab-case the tutorial notebook, snake_case its builder ([5a65b73](https://github.com/sgjholt/SpecMod/commit/5a65b7336980bf5d7163c4cad28e7c273715c0a3))
+* measure the MathJax figure instead of asserting it ([cba7e01](https://github.com/sgjholt/SpecMod/commit/cba7e0116a09ba8d4565308ee8c0227d138b20cd))
+* render maths with KaTeX, served from this site ([902d3fe](https://github.com/sgjholt/SpecMod/commit/902d3fec4230e6af17ea1b7a9d32d9e9c153fd8e))
+* self-host the branding fonts ([c1e6f9f](https://github.com/sgjholt/SpecMod/commit/c1e6f9fe16f4ec48c5e788e6b29181c5ffc01bbf))
+* the decomposition is finished ([bbb2b71](https://github.com/sgjholt/SpecMod/commit/bbb2b7189b9f98c3baa48fe907bc2c414455f5d9))
+
 ## [0.2.3](https://github.com/sgjholt/SpecMod/compare/v0.2.2...v0.2.3) (2026-09-05)
 
 

{specmod-0.2.3 → specmod-0.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: specmod
-Version: 0.2.3
+Version: 0.4.0
 Summary: A Python toolbox for processing and modelling seismic spectra
 Project-URL: Homepage, https://github.com/sgjholt/SpecMod
 Project-URL: Repository, https://github.com/sgjholt/SpecMod
@@ -35,11 +35,12 @@ Requires-Dist: pytest-cov>=5.0; extra == 'dev'
 Requires-Dist: pytest>=8.0; extra == 'dev'
 Requires-Dist: ruff>=0.6; extra == 'dev'
 Provides-Extra: docs
+Requires-Dist: furo>=2024.1; extra == 'docs'
 Requires-Dist: myst-nb>=1.1; extra == 'docs'
 Requires-Dist: myst-parser>=3.0; extra == 'docs'
-Requires-Dist: pydata-sphinx-theme>=0.15; extra == 'docs'
 Requires-Dist: sphinx-togglebutton>=0.3; extra == 'docs'
 Requires-Dist: sphinx>=7.3; extra == 'docs'
+Requires-Dist: sphinxcontrib-katex>=0.9; extra == 'docs'
 Provides-Extra: io
 Requires-Dist: h5py>=3.11; extra == 'io'
 Requires-Dist: pyarrow>=16.0; extra == 'io'
@@ -179,13 +180,13 @@ changes nothing else.
 
 ## Reading picks
 
-Arrivals are attached to traces by `set_picks`, which detects the format from
-the file rather than from its name:
+`with_picks` returns a stream with arrivals attached, detecting the format
+from the file rather than from its name:
 
 ```python
 import specmod.preprocess as pre
 
-pre.set_picks(stream, "event.xml")
+stream = pre.with_picks(stream, "event.xml")
 ```
 
 Everything `obspy.read_events` parses is read through one delegate — QuakeML,

{specmod-0.2.3 → specmod-0.4.0}/README.md

@@ -122,13 +122,13 @@ changes nothing else.
 
 ## Reading picks
 
-Arrivals are attached to traces by `set_picks`, which detects the format from
-the file rather than from its name:
+`with_picks` returns a stream with arrivals attached, detecting the format
+from the file rather than from its name:
 
 ```python
 import specmod.preprocess as pre
 
-pre.set_picks(stream, "event.xml")
+stream = pre.with_picks(stream, "event.xml")
 ```
 
 Everything `obspy.read_events` parses is read through one delegate — QuakeML,

{specmod-0.2.3 → specmod-0.4.0}/docs/REFACTOR_PLAN.md

@@ -1087,7 +1087,7 @@ and there are presumably more in your working directories.
 Two ways out, and the first is much better:
 
 1. **Convert in the old environment.** Phase 0 is already building a Docker image
-   where the 0.1.0 code runs (§6.7). Add a small
+   where the 0.1.1 code runs (§6.7). Add a small
    `scripts/convert_legacy_spec.py` to it that loads `.spec` files with the old
    classes present and writes the new HDF5 format. This is a one-shot migration
    with no lasting cost to the codebase.
@@ -2742,13 +2742,30 @@ Two further problems with reproducing the published run from this repository:
    manuscript filename (`...SRL3`) suggests a third revision, which would also
    explain a 2021 code state behind a 2020 access date.
 
-   Practical consequence: **the candidate is `ba3f7ec` or later, not the
+   The evidence narrows it: **the candidate is `ba3f7ec` or later, not the
    pre-November-2020 commits**, because the earlier code cannot perform the
    workflow the paper describes. Only `09f57b9` (removed cython) changes
    `specmod/` after that, so the realistic candidates are `ba3f7ec` and
-   `453c77c`. Pick one, record the reasoning, and move on — this is the
-   strongest possible argument for the `v0.1.0` tag (§6.7) and for `hatch-vcs`
-   (§6.4): it must never be this hard again.
+   `453c77c`.
+
+   **Answered: `453c77c`** — the tip of `master`, 2021-08-12. On the author's
+   word, and it is why `master` was frozen at that commit rather than at any
+   other: the branch *is* the v0.1.1 record (§6.7). Which of the two the
+   evidence above prefers was never the question it looked like.
+
+   What that settles and what it does not: the code is identified, so §5.2.6
+   step 2 can be run against a known commit. The dating oddity is unchanged —
+   the manuscript's access date still precedes the commit it cites, which the
+   third revision (`...SRL3`) explains without needing the code to have moved.
+   It is recorded rather than resolved, because nothing in the repository can
+   resolve it.
+
+   This is still the strongest possible argument for tagging that commit (§6.7)
+   and for `hatch-vcs` (§6.4): a version that takes a page of archaeology to
+   identify must never happen again. **No `v0.1.1` tag exists yet.** Creating
+   one is safe — `453c77c` is an ancestor of `main`, and every later release
+   tag outranks it for `hatch-vcs`, so nothing derives a version from it — but
+   it is repository state, not something a commit here can carry.
 2. **The full published pipeline is not in this repository.** The two-stage
    inversion (fit Ω/`f_c`/`t*` free, then fix event `f_c` to the
    inverse-hypocentral-distance-weighted mean of station `f_c` and refit) and the
@@ -3414,6 +3431,31 @@ been audited once is worth more than one that reads confidently throughout.
 | "`commitlint`-enforced" again, in §6.4 | The §7 instance was corrected and this one was left standing, in the same document. §6.4 corrected. |
 | `publish.yml` "GitHub Release published → PyPI" | It would never have run. release-please creates the release with the default `GITHUB_TOKEN`, and events triggered by that token do not start a workflow. The publish job moved into `release.yml`, gated on `release_created`. §6.5 corrected. |
 
+**A fourth of the same shape, found later** — the three above were corrected in
+the prose; this one was a live setting:
+
+> `[smoothing] method` — "Name -> smoother, for resolving `SmoothingConfig.method`"
+
+`SMOOTHERS` existed, `method` validated against its `Literal`, and **no code
+anywhere read it**. The comparison binned with `log_bin` unconditionally.
+Measured on the 28 PNR windows, `log_bins`, `konno_ohmachi` and `none` produced
+bit-identical output — `none` included, which reads as "leave my spectra
+unsmoothed" while every spectrum went on being binned exactly as before.
+
+**Fixed rather than documented.** `SpectrumPair.compare` now takes a `smoother`,
+`[smoothing] method` resolves to one, and the registry gained `log_window`
+(constant-relative-bandwidth smoothing with a selectable window shape, and a
+median option) and `savitzky_golay` beside the two that were there.
+`tests/test_config.py::TestEverySmoothingMethodIsWiredUp` and
+`tests/test_pipeline.py::TestTheConfiguredSmootherReachesTheComparison` are the
+mechanism the comment claimed: each accepted value resolves, carries its
+section's parameters, and survives the whole path on real windows.
+
+`log_bins` stays `core.collection.log_bin` rather than `smoothing.LogBinner` —
+the two differ in clamping and in what `n_bins` counts, and the difference is
+every committed golden number. The default path is unchanged, which the golden
+suite asserts and which is why this could land without moving a number.
+
 **A claim whose mechanism is absent but whose property holds — for a different
 reason, which matters:**
 
@@ -3460,7 +3502,8 @@ of §5.2, and the two-stage fit API of §5.2.5.
 **`master` is frozen; `main` is the trunk.** `main` was branched from `master` at
 `453c77c` and is where all refactor work lands. `master` is never committed to
 again — it becomes the permanent, named record of the pre-refactor code, doing
-the job a `v0.1.0` tag would have done.
+the job a `v0.1.1` tag would have done. Its tip, `453c77c`, **is** the v0.1.1
+the Magna paper cites (§5.2.5, §8).
 
 **Every pull request must target `sgjholt/SpecMod`, never `uofuseismo/SpecMod`.**
 This is not a matter of care — it is a GitHub default working against you.
@@ -3498,7 +3541,7 @@ Two consequences worth acting on:
 - [ ] Settings → Actions → confirm workflows are enabled
 - [ ] Settings → Branches → protect `master` (no pushes, no deletion) so the
       frozen record stays frozen
-- [ ] `git tag -a v0.1.0 453c77c -m "pre-refactor snapshot" && git push origin v0.1.0`
+- [ ] `git tag -a v0.1.1 453c77c -m "the version the Magna paper cites" && git push origin v0.1.1`
 
 **No Claude session URLs in commit messages, PR bodies, or any other published
 artifact.** The repository is public and those links are private session state. A
@@ -3516,12 +3559,20 @@ needed and neither can be made from a git client:
    convention rather than a guarantee — one absent-minded `git push origin
    master` and the record is gone.
 
-Optionally also tag `453c77c` as `v0.1.0` for good measure; belt and braces, and
-it gives release-please an explicit floor to generate the first changelog from.
-The two are complementary — the tag is immutable, the branch is discoverable.
+Also tag `453c77c` as `v0.1.1` — no longer optional now that §8 records it as
+the commit the paper cites. A branch is discoverable and a tag is immutable,
+and a citation should resolve to the immutable one.
+
+Tagging it publishes nothing. No workflow triggers on tags; the PyPI upload is
+gated on release-please's `release_created`, which only a merged release PR on
+`main` can set; and `git describe` takes the nearest tag, which is a release
+far ahead of this one. **Do not create a GitHub Release from the tag**, which
+is the one action that would publish: Zenodo listens to the release webhook and
+would mint a DOI for the pre-refactor code. The commit has no `pyproject.toml`
+and is not packageable.
 
 > Note on tooling limits: tag pushes are blocked in the automation environment
-> this plan was written in (HTTP 403 on `push origin v0.1.0`, while branch
+> this plan was written in (HTTP 403 on `push origin v0.1.1`, while branch
 > pushes to the same remote succeed), which is why `main` exists as a branch
 > rather than the state being pinned by a tag. **This does not affect the release
 > automation in §6.4** — release-please creates tags from inside GitHub Actions
@@ -3531,10 +3582,10 @@ The two are complementary — the tag is immutable, the branch is discoverable.
 
 Worth being precise about what any of this does and does not preserve: it
 preserves the **code**, but the code is not **runnable** — `mtspec` no longer
-builds on any current toolchain (§2.1). Reproducing a 0.1.0 result needs three
+builds on any current toolchain (§2.1). Reproducing a 0.1.1 result needs three
 things, which is what Phase 0 delivers:
 
-1. `master` (and optionally `v0.1.0`) — the source.
+1. `master` (and the `v0.1.1` tag on its tip) — the source.
 2. A `Dockerfile` pinning `gfortran`, `python 3.9`, `numpy<2` — the environment
    that can still build `mtspec`. Also the only place existing `.spec` pickles
    can be read (§4.6).
@@ -3565,13 +3616,13 @@ Each phase ends green on CI and is independently mergeable.
 
 | Phase | Work | Depends on | Rough size |
 |---|---|---|---|
-| **0. Safety net** | Freeze `master`, default branch → `main`, optional `v0.1.0` tag (§6.7); reproducible legacy env (`Dockerfile`: gfortran + ObsPy 1.2.0 / SciPy 1.4.1 / NumPy 1.18 / pandas 1.0.0 (§5.2.6)); write `datasets/magna_2020.toml` and a first cut of `specmod.acquire`, publish the artifact as a `data-v1` release asset (§5.2); capture golden outputs for PNR **and** Magna; reproduce Table S2 / Figure 2 with 0.1.1 (§5.2.6 step 2); convert any `.spec` files (§4.6) | — | 1.5–2 days |
+| **0. Safety net** | Freeze `master`, default branch → `main`, optional `v0.1.1` tag (§6.7); reproducible legacy env (`Dockerfile`: gfortran + ObsPy 1.2.0 / SciPy 1.4.1 / NumPy 1.18 / pandas 1.0.0 (§5.2.6)); write `datasets/magna_2020.toml` and a first cut of `specmod.acquire`, publish the artifact as a `data-v1` release asset (§5.2); capture golden outputs for PNR **and** Magna; reproduce Table S2 / Figure 2 with 0.1.1 (§5.2.6 step 2); convert any `.spec` files (§4.6) | — | 1.5–2 days |
 | **1. Make it installable** | `pyproject.toml` + hatch-vcs, `src/` layout, `__init__.py`; ruff config, one-shot `ruff format` + `.git-blame-ignore-revs`, module renames to snake_case; mypy skeleton; pre-commit; `test`/`build` CI; `.gitignore`, `CITATION.cff`; fix the three hard breakages (§1) and the four `F821` bugs ruff finds (§2.5); delete `Tests/Tutorial/`, strip notebook outputs, subset the inventory (§5.1) | 0 | 3–4 days |
 | **2. De-globalise** | `config/` package per §4.8 — semantic groups, layer resolution, `config show`/`freeze`, provenance stamping; remove all module-level config reads (tracked by `PLW0603`); `Motion`/`AmplitudeKind` enums; `Spectrum` as a frozen dataclass with `duration`; mutable class attrs (`RUF012`); `isinstance` checks; `logging`. **Tag `v0.2.0`** | 1 | 3–4 days |
 | **2b. Release plumbing** ✅ | ~~Sphinx skeleton + `pydata-sphinx-theme` + autodoc/napoleon/intersphinx~~ ✅; ~~`docs.yml` → a published site~~ ✅ — Read the Docs rather than GH Pages, for versions (§6.3); ~~release-please + PyPI Trusted Publishing~~ ✅ — one `release.yml`, not two workflows (§6.5); ~~Zenodo webhook~~ ✅ documented. Five repository settings have to be turned on by hand: `docs/releasing.md` lists them. The `ci/` mirror that staged workflow files for hand-copying is gone — it existed because an agent token could not push `.github/workflows/`, and that permission is now granted. Parallel with 2 | 1 | 1–2 days |
 | **3. Transform layer** | `SpectralEstimator` protocol; `FFTEstimator`, `WelchEstimator`, `MultitaperEstimator`; `smoothing/` incl. Konno–Ohmachi and `LogBinner`; mtspec demoted to optional legacy backend; Tier 1 + Tier 2 tests; theory docs page | 2 | 5–7 days |
 | **4. CWT** | `CWTEstimator` + `Scalogram`; COI handling; the Parseval/units calibration and its test; `time_average()`; `ScalogramQC` + the four QC checks; COI floor into `BandwidthSelector`; scalogram plotting; HDF5 scalogram storage | 3 | 6–8 days |
-| **5. Decompose** | Split `Spectral.py` (655 lines) into `core/` + `snr/` ✅; ~~`Fitting.py` → `fitting/`~~ ✅ — `base`/`guess`/`spectrum`/`event`, 745 lines to four modules of 30–300, public names unchanged; models as objects ✅; `io/`; `viz/`; non-mutating operations; mypy override list → empty ✅; `picks/` per §4.9 ✅ | 3 | 4–6 days |
+| **5. Decompose** ✅ | Split `Spectral.py` (655 lines) into `core/` + `snr/` ✅; ~~`Fitting.py` → `fitting/`~~ ✅ — `base`/`guess`/`spectrum`/`event`, 745 lines to four modules of 30–300, public names unchanged; models as objects ✅; ~~`io/`~~ ✅ — `layout`/`hdf5`/`backend`; ~~`viz/`~~ ✅ — shipped as `plotting/`, `pair`/`grid`/`style`; ~~non-mutating operations~~ ✅ — `preprocess` was the last holdout, and the ten functions were renamed rather than only re-signatured so the break is loud; mypy override list → empty ✅; `picks/` per §4.9 ✅ | 3 | 4–6 days |
 | **6. Ship** | Full docs content, tutorial rewritten as an executed `myst-nb` page with no `os.chdir`, 0.1→1.0 "what changed" page, **1.0 release** | 4, 5 | 2–3 days |
 
 **Executing the tutorial was pulled forward out of Phase 6.** The `myst-nb`
@@ -3658,20 +3709,48 @@ changes anything shipped.
 ### Still open
 
 1. **Default estimator.** Multitaper (matching current behaviour) or FFT +
-   Konno–Ohmachi (faster, more conventional in engineering seismology)?
+   Konno–Ohmachi (more conventional in engineering seismology)? **No longer
+   blocked** — §6.6's dead `[smoothing] method` is wired up, so the second
+   option is selectable — and now measured, on the 28 PNR windows with each
+   station fitted freely:
+
+   | Against the shipped multitaper + `log_bins` | Median ΔMw | Per-station range | `fc` ratio |
+   |---|---|---|---|
+   | `fft` + `log_bins` | −0.039 | −0.85 to +1.90 | 0.003 to 5.0 |
+   | `fft` + `konno_ohmachi` | +0.027 | −0.52 to +0.51 | 0.038 to 3.2 |
+
+   **The smoothing is what makes the switch defensible, not the estimator.**
+   FFT with the shipped binner moves a station by up to 1.9 magnitude units,
+   because `log_bins` reduces the axis without reducing the variance — 151 log
+   bins over a few hundred Fourier samples is roughly one sample per bin.
+   Pairing it with a real smoother halves the worst excursion and pulls the
+   `fc` range in by a third. The median station barely moves either way.
+
+   What this event cannot settle: the *event* corner is unconstrained under all
+   three (stage-one spread 895% to 1042% of the event value), so the ensemble
+   number is not evidence. Deciding on the ensemble needs an event where it is
+   constrained.
+
+   Speed, measured rather than assumed and far too small to decide on: the
+   transform is 0.209 s against 0.323 s for the 28 windows, and the smoothing
+   adds 0.14 s (`log_bins`) to 0.83 s (`konno_ohmachi`) on top.
+
 2. **Python floor.** 3.11 is proposed. Any users stuck on 3.9/3.10?
 3. **History rewrite.** Deleting the 9.9 MB catalog and stripping the notebook
    (§5.1) shrinks the *working tree* but leaves both in history, so a fresh clone
    still pulls ~15 MiB. Rewriting history with `git-filter-repo` would recover it
    — but it rewrites every SHA, which moves what `master` and `main` currently
-   point at and invalidates any `v0.1.0` tag. Given the end state is a ~1 MB repo
+   point at and invalidates any `v0.1.1` tag. Given the end state is a ~1 MB repo
    either way, **the recommendation is to leave history alone**: a one-time 15 MiB
    clone is a much smaller cost than an unrecoverable pre-refactor record. Only
    worth revisiting if the history genuinely becomes a burden.
-4. **Which commit is "v0.1.1"?** The paper cites SpecMod v0.1.1; no such tag
-   exists and the source carries no version string (§5.2.5). Reproducing the
-   published run needs that commit identified — by submission date against the
-   history, if nothing better is available. Only you can make that call.
+4. ~~**Which commit is "v0.1.1"?**~~ **Resolved: `453c77c`**, the tip of
+   `master`, 2021-08-12 — which is what freezing `master` at that commit was
+   for (§6.7). The archaeology in §5.2.5 narrowed it to two candidates and
+   could not choose between them; the answer did not come from the repository
+   and was never going to. §5.2.6 step 2 now has a known commit to run. No
+   `v0.1.1` tag exists yet, and creating one is repository state rather than
+   something a commit can carry.
 5. ~~**Was noise rotation on for the published run?**~~ **Assumed on.** Not
    recalled, so `studies/magna_2020_paper.toml` starts from the shipped values —
    `ROTATE_NOISE = true`, `ROT_METHOD = 2`, `ROT_PARS = {inc = 0.05, space =