packaging refinements

Author: MattDHill

packaging/src/actions.md

@@ -132,8 +132,8 @@ The recommended pattern:
 3. **Provide a toggle action** that reads the current registration state, flips it, and writes back.
 
 ```typescript
-// In init/initializeService.ts
-export const initializeService = sdk.setupOnInit(async (effects, kind) => {
+// In init/taskDisableRegistrations.ts
+export const taskDisableRegistrations = sdk.setupOnInit(async (effects, kind) => {
   if (kind !== "install") return;
   await sdk.action.createOwnTask(effects, toggleRegistrations, "important", {
     reason:
@@ -390,7 +390,7 @@ export const main = sdk.setupMain(async ({ effects }) => {
 
 ### 5. Initialize with SMTP Disabled
 
-In `init/initializeService.ts`, set the default SMTP state alongside any internal-only secrets the service needs. The admin password is set by the `setAdminPassword` action when the user runs its critical task (see [Prompt User to Create Admin Credentials](./recipe-admin-credentials.md)):
+In `init/seedFiles.ts`, set the default SMTP state alongside any internal-only secrets the service needs. The admin password is set by the `setAdminPassword` action when the user runs its critical task (see [Prompt User to Create Admin Credentials](./recipe-admin-credentials.md)):
 
 ```typescript
 await storeJson.merge(effects, {

packaging/src/init.md

@@ -16,7 +16,7 @@
 For one-time setup that generates new state. Internal-only secrets (DB password, JWT secret, etc.) **are** generated here, because no user interaction is involved:
 
 ```typescript
-export const initializeService = sdk.setupOnInit(async (effects, kind) => {
+export const seedFiles = sdk.setupOnInit(async (effects, kind) => {
   if (kind !== 'install') return
 
   // Internal secret consumed by setupMain — never shown to the user
@@ -33,7 +33,7 @@ User-facing admin credentials follow a different pattern — see [Watch State an
 For setup that should also run when restoring from backup (but not on container rebuild):
 
 ```typescript
-export const initializeService = sdk.setupOnInit(async (effects, kind) => {
+export const reRegisterWebhook = sdk.setupOnInit(async (effects, kind) => {
   if (kind === null) return // Skip on container rebuild
 
   // Runs on both install and restore — e.g. re-register a webhook with an
@@ -47,7 +47,7 @@ export const initializeService = sdk.setupOnInit(async (effects, kind) => {
 For registering `.const()` triggers that need to persist for the container's lifetime. These re-register on container rebuild:
 
 ```typescript
-export const initializeService = sdk.setupOnInit(async (effects, kind) => {
+export const registerWatchers = sdk.setupOnInit(async (effects, kind) => {
   // Runs on install, restore, AND container rebuild
 
   // Register a watcher that lives for the container lifetime
@@ -148,7 +148,7 @@ export const setAdminPassword = sdk.Action.withoutInput(
 
 If the upstream service needs the password applied via CLI or API rather than just read from the store at startup, wrap the work in `sdk.SubContainer.withTemp()` inside the action handler — see the [Reset a Password](recipe-reset-password.md) recipe.
 
-## Registering initializeService
+## Registering a custom init function
 
 Add your custom init function to `init/index.ts`:
 
@@ -159,15 +159,15 @@ import { setInterfaces } from '../interfaces'
 import { versionGraph } from '../versions'
 import { actions } from '../actions'
 import { restoreInit } from '../backups'
-import { initializeService } from './initializeService'
+import { seedFiles } from './seedFiles'
 
 export const init = sdk.setupInit(
   restoreInit,
   versionGraph,
   setInterfaces,
   setDependencies,
   actions,
-  initializeService, // Add this
+  seedFiles, // Add this
 )
 
 export const uninit = sdk.setupUninit(versionGraph)
@@ -316,7 +316,7 @@ Severity levels: `'critical'`, `'important'`, `'optional'`
 ### Checking Init Kind
 
 ```typescript
-export const initializeService = sdk.setupOnInit(async (effects, kind) => {
+export const seedFiles = sdk.setupOnInit(async (effects, kind) => {
   // kind === 'install': Fresh install
   // kind === 'update': After version upgrade
   // kind === 'restore': Restoring from backup

packaging/src/main.md

@@ -177,7 +177,7 @@ Oneshots are tasks that run on every startup before daemons. Use them for idempo
 ```
 
 > [!WARNING]
-> Do NOT put one-time setup tasks (like `createsuperuser`) in `main.ts` oneshots -- they run on every startup and will fail on subsequent runs. Use `init/initializeService.ts` instead. See [Initialization Patterns](./init.md) for details.
+> Do NOT put one-time setup tasks (like `createsuperuser`) in `main.ts` oneshots -- they run on every startup and will fail on subsequent runs. Use a custom init file (e.g. `init/seedFiles.ts`) instead. See [Initialization Patterns](./init.md) for details.
 
 ## Exec Command
 
@@ -468,7 +468,7 @@ The `user` option is optional. If omitted, commands run as the default user defi
 **Use `execFail()` when:**
 
 - The command must succeed for the service to work correctly
-- You are in `initializeService.ts` and want installation to fail if setup fails
+- You are in a custom init file (e.g. `seedFiles.ts`) and want installation to fail if setup fails
 - You want automatic error propagation
 
 **Use `exec()` when:**

packaging/src/versions.md

@@ -270,8 +270,8 @@ export const seedFiles = sdk.setupOnInit(async (effects, kind) => {
 Tasks reference actions, so they must be created in a `setupOnInit` that runs after actions are registered in the init sequence:
 
 ```typescript
-// init/initializeService.ts
-export const initializeService = sdk.setupOnInit(async (effects, kind) => {
+// init/taskDisableRegistrations.ts
+export const taskDisableRegistrations = sdk.setupOnInit(async (effects, kind) => {
   if (kind !== 'install') return
   await sdk.action.createOwnTask(effects, toggleRegistrations, 'important', {
     reason: 'After creating your admin account, disable registrations.',