My Emacs configuration https://git.cjennings.net/dotemacs/atom?h=main 2026-07-10T11:00:44+00:00 2026-07-10T11:00:44+00:00 Craig Jennings c@cjennings.net 2026-07-10T11:00:44+00:00 urn:sha1:6a193a6c4b36c6bae4a5e2f2a7a8e8b9a32aed71 A doctor that refuses to install anything buys nothing that isn't already there. Every external binary is guarded at its point of use, with a message that names it: hugo-config guards hugo and the file-manager opener, org-webclipper guards pandoc, org-export-config guards zathura, and ox-pandoc guards itself upstream. Missing packages surface at load or first use. Path checks were the only new capability, and warning about them at startup contradicts the spec's own goal of keeping startup quiet, while an on-demand check nobody remembers to run is worth nothing. The spec's Problem section rested on a premise nobody verified: that none of these dependencies was checked anywhere. It came from grepping for our own warn helper by name instead of reading the modules for the behavior. The body stays as written with the correction marked, and a postmortem records that the Reuse dimension named the helper that made the feature redundant, then dismissed it in one clause. No code changed. 2026-07-10T05:32:11+00:00 Craig Jennings c@cjennings.net 2026-07-10T05:32:11+00:00 urn:sha1:9b0825e67311731c5ecd40a61c9043ce8a4595c9 A read-only cj/org-workflow-doctor that reports whether the Org workflow's paths, binaries, and lazily-loaded packages are present. Nothing checks them today, so a missing prerequisite surfaces mid-capture in whatever shape the first module to trip over it produces. One probed finding is why the spec exists. The obvious package check is featurep, and it's wrong here: this config loads Org packages lazily, so org-noter and org-web-tools report featurep nil while locate-library finds them. A doctor built on featurep would report false failures for exactly the packages the config defers, which teaches you to ignore it. Both decisions are resolved, so it's ready for spec-review.