Repository navigation
feat: the content-freshness plugin - #8
Merged
Merged
Conversation
… plugins Copied unchanged from the proof-of-concept repository at ef4884d, where the content plugins use them: `chain.ts` carries a sweep across cron runs with alternating one-shot follow-ups, and `listCollections()` finds every collection through `schema:read`. `parseCollections()` stays for now. The floor rises to 0.39.0 because `ctx.schema` first exists there; the analytics plugin already requires 0.39.0.
Imported from the proof-of-concept repository at ef4884d as fresh files. A scheduled, network-free audit: overdue schedules, missing or badly sized SEO descriptions, stale entries, forgotten drafts, and routable collections without a URL pattern. Capabilities `content:read` and `schema:read`; it reports and never edits. Aligned with the workspace on the way in: `registry:publish` and `registry:login` instead of the generated `publish` and `login`, `prepublishOnly` builds, repository metadata for trusted publishing, a peer range with a floor and no ceiling, and the analytics plugin's vitest limits (30 s timeouts, one test file at a time). Toolchain unchanged from the proof of concept: plugin-cli 0.12.0, plugin-test 0.2.1, EmDash 0.39.1.
The full-audit test pinned the host's scheduler clock to 04:00:05 on 2026-09-25, but the plugin schedules its follow-up runs from `Date.now()`. While that night lay ahead of the real time, follow-ups fell due; since then they land after the host's clock, never run, and the sweep never finishes. The test now uses tomorrow's night, which is always ahead of the wall clock. It still fails if a follow-up is lost.
This was referenced Sep 25, 2026
…s-import # Conflicts: # pnpm-lock.yaml
The release workflow publishes every public package whose version is missing from npm, with or without a changeset: the run after #11 listed "These packages will be published as they were not found in the registry". Merged public, content-freshness@0.1.0 would have been in the next publish plan, and as a package npm does not know yet it cannot use trusted publishing, so every later release run would fail on it. The release PR removes the flag and adds the first changeset. AGENTS.md says so for any package that follows.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Imports the content-freshness plugin from the private proof-of-concept repository as fresh files, the same way analytics came across. Nothing is published: no changeset, and the storage layout changes before a first release.
What is in it
packages/content-freshness:@eisbachcode/emdash-plugin-content-freshness. A scheduled audit that needs no network access: overdue schedules, missing or badly sized SEO descriptions, stale entries, forgotten drafts, and routable collections without a URL pattern. It usescontent:readandschema:read, and reports without ever editing. See its README.packages/shared:chain.ts(a sweep carried across cron runs) andlistCollections(), copied unchanged from the proof of concept.parseCollections()stays. The shared floor rises to 0.39.0, wherectx.schemafirst exists.registry:publishandregistry:loginreplace the generatedpublishandlogin.prepublishOnlybuilds the package.The toolchain is unchanged from the proof of concept: plugin-cli 0.12.0, plugin-test 0.2.1, EmDash 0.39.1. The move to 0.40.1 is a separate PR.
Verified
emdash-plugin validate, typecheck, build.ef4884ddoes not exist in this repository.