Migrate site to npm-backed Slugkit template #49

Merged

erik merged 1 commit from task-a1e140c0-npm-backed-template into main

2026-06-30 13:14:59 -05:00

erik commented

2026-06-30 13:10:45 -05:00

Owner

Summary

Migrates slugkit.com to the current npm-backed Slugkit template generated by @evcraddock/slug-cli@0.6.2.
Adds published @evcraddock/slug-* runtime package dependencies and template package metadata.
Preserves slugkit.com-specific site identity, Forgejo/Docker release path, local Garage dev setup, and existing migrations/data compatibility.
Carries forward Mastodon-compatible ActivityPub key behavior from the current template.

Verification

npm run build
npm test
docker build --build-arg APP_VERSION=0.1.1 -t slugkit-com:migration-check .
Local temp DB/server smoke with slug doctor --json passed public/API/package checks; auth check warned as expected because no API key was configured.

Notes

Fresh comparison template source: /tmp/slugkit-template.qftuB1/site, generated with npx -y @evcraddock/slug-cli@latest init.
Post-deploy smoke still needs to run against the deployed environment after merge/release, including slug doctor with production config and ActivityPub/Mastodon verification if federation is enabled.

## Summary - Migrates `slugkit.com` to the current npm-backed Slugkit template generated by `@evcraddock/slug-cli@0.6.2`. - Adds published `@evcraddock/slug-*` runtime package dependencies and template package metadata. - Preserves slugkit.com-specific site identity, Forgejo/Docker release path, local Garage dev setup, and existing migrations/data compatibility. - Carries forward Mastodon-compatible ActivityPub key behavior from the current template. ## Verification - `npm run build` - `npm test` - `docker build --build-arg APP_VERSION=0.1.1 -t slugkit-com:migration-check .` - Local temp DB/server smoke with `slug doctor --json` passed public/API/package checks; auth check warned as expected because no API key was configured. ## Notes - Fresh comparison template source: `/tmp/slugkit-template.qftuB1/site`, generated with `npx -y @evcraddock/slug-cli@latest init`. - Post-deploy smoke still needs to run against the deployed environment after merge/release, including `slug doctor` with production config and ActivityPub/Mastodon verification if federation is enabled.

erik added 1 commit

2026-06-30 13:10:45 -05:00

Migrate site to npm-backed Slugkit template b775b707c3

erik commented

2026-06-30 13:11:55 -05:00

Author

Owner

Review summary

The PR aligns with the npm-backed Slugkit template migration goal. It adds the published @evcraddock/slug-* dependencies and package metadata, imports shared package behavior where appropriate, preserves local deployment/dev configuration, and carries forward Mastodon-compatible ActivityPub key behavior.

Acceptance criteria

A migration branch exists in slugkit.com — task-a1e140c0-npm-backed-template.
A fresh current template generated from the latest published @evcraddock/slug-cli is used as the comparison source — generated under /tmp/slugkit-template.qftuB1/site with @evcraddock/slug-cli@0.6.2.
Existing slugkit.com configuration, CI/CD workflows, deployment files, custom assets/styles/content, and environment assumptions are preserved or explicitly merged — Forgejo workflow/local Garage dev setup remained in place; site identity and env assumptions were preserved/merged.
The site uses current published @evcraddock/slug-* package dependencies where appropriate — package deps and lockfile updated.
The current template ActivityPub Mastodon-compatible key behavior is present in slugkit.com — legacy key route and acct:<actor>@<domain> signing behavior are present with tests.
Local tests/build/typecheck pass for the migrated site — npm run build and npm test passed.
Deployment path is verified without replacing secrets or production-only config — Docker build passed with the existing release build-arg path preserved.
[~] Post-deploy smoke test passes, including Slugkit CLI doctor and ActivityPub/Mastodon verification if federation is enabled — local temp DB/server slug doctor --json passed public/API/package checks with expected auth warning; production post-deploy smoke remains after merge/release.

Blocking issues

None.

Warnings

Production post-deploy smoke is still required after merge/release, including authenticated slug doctor and ActivityPub/Mastodon verification if federation is enabled.

Verdict

Warnings — acceptable to merge after human approval, with post-deploy smoke required after deployment.

## Review summary The PR aligns with the npm-backed Slugkit template migration goal. It adds the published `@evcraddock/slug-*` dependencies and package metadata, imports shared package behavior where appropriate, preserves local deployment/dev configuration, and carries forward Mastodon-compatible ActivityPub key behavior. ## Acceptance criteria - [x] A migration branch exists in `slugkit.com` — `task-a1e140c0-npm-backed-template`. - [x] A fresh current template generated from the latest published `@evcraddock/slug-cli` is used as the comparison source — generated under `/tmp/slugkit-template.qftuB1/site` with `@evcraddock/slug-cli@0.6.2`. - [x] Existing `slugkit.com` configuration, CI/CD workflows, deployment files, custom assets/styles/content, and environment assumptions are preserved or explicitly merged — Forgejo workflow/local Garage dev setup remained in place; site identity and env assumptions were preserved/merged. - [x] The site uses current published `@evcraddock/slug-*` package dependencies where appropriate — package deps and lockfile updated. - [x] The current template ActivityPub Mastodon-compatible key behavior is present in `slugkit.com` — legacy key route and `acct:<actor>@<domain>` signing behavior are present with tests. - [x] Local tests/build/typecheck pass for the migrated site — `npm run build` and `npm test` passed. - [x] Deployment path is verified without replacing secrets or production-only config — Docker build passed with the existing release build-arg path preserved. - [~] Post-deploy smoke test passes, including Slugkit CLI `doctor` and ActivityPub/Mastodon verification if federation is enabled — local temp DB/server `slug doctor --json` passed public/API/package checks with expected auth warning; production post-deploy smoke remains after merge/release. ## Blocking issues - None. ## Warnings - Production post-deploy smoke is still required after merge/release, including authenticated `slug doctor` and ActivityPub/Mastodon verification if federation is enabled. ## Verdict Warnings — acceptable to merge after human approval, with post-deploy smoke required after deployment.

erik merged commit 1f9c26db44 into main

2026-06-30 13:14:59 -05:00

erik deleted branch task-a1e140c0-npm-backed-template

2026-06-30 13:14:59 -05:00

erik referenced this pull request from a commit

2026-06-30 13:14:59 -05:00

Merge pull request 'Migrate site to npm-backed Slugkit template' (#49) from task-a1e140c0-npm-backed-template into main