@codyswann/lisa 4.62.4 → 4.63.0

package/package.json

@@ -187,7 +187,7 @@
     "zod-validation-error": "^4.0.0"
   },
   "name": "@codyswann/lisa",
-  "version": "4.62.4",
+  "version": "4.63.0",
   "description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
   "main": "dist/index.js",
   "exports": {
@@ -336,7 +336,7 @@
     "test": "tests"
   },
   "types": "./dist/index.d.ts",
-  "lisaReleaseCommit": "8719a1c8b417337e85e48399e43560302e219aa7",
-  "gitHead": "8719a1c8b417337e85e48399e43560302e219aa7",
-  "lisaReleaseTag": "v4.62.4"
+  "lisaReleaseCommit": "e771330eff75036e3199b7b7b4ff2dc5e62065b8",
+  "gitHead": "e771330eff75036e3199b7b7b4ff2dc5e62065b8",
+  "lisaReleaseTag": "v4.63.0"
 }

package/plugins/lisa/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "4.62.4",
+  "version": "4.63.0",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "4.62.4",
+  "version": "4.63.0",
   "description": "Universal governance: agents, skills, commands, hooks, and rules for all projects.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa/.codex-plugin/skills/lisa-setup-automations/SKILL.md

@@ -197,6 +197,26 @@ closed by the next run's dedupe or the human), not mutual exclusion; manual
 runs should first confirm the cron is not due or running. Tear-down removes
 it with the rest of the `lisa-auto-<project>-*` set.
 
+**Optional automation — starter sync.** Read `starter.sync.auto` from the
+project's current config. Only the boolean `true` opts in (default **false**).
+When true, reconcile exactly one `lisa-auto-<project>-starter-sync` registration
+running `/lisa:starter-sync` once a **day** (`FREQ=DAILY;INTERVAL=1`) in the
+verified durable project checkout. Use the current runtime's native scheduler
+and update an existing registration by its exact name rather than duplicating
+it. Its prompt must identify this as a scheduled invocation, require a fresh
+check of `starter.sync.auto` before mutation, and carry the literal command on
+its own line. The `lisa-starter-sync` skill calls the shipped CLI and preserves
+its configured landing strategy; an open PR is not an applied update.
+
+When false or absent, remove any exact `lisa-auto-<project>-starter-sync`
+registration using that same native scheduler, leaving all other schedules
+alone. Read the scheduler back after either operation and report the observed
+name, target, cadence, or verified absence. Saving the console toggle only saves
+config: run this reconciliation to change the registration. If scheduler access
+is unavailable, report registration/removal as **unverified**, not successful;
+do not write its backing files or install another scheduler. This representation
+gap applies to any runtime without a native recurring-task tool.
+
 **Optional automation — the health cron.** When `health.schedule` in
 `.lisa.config.json` is `daily` or `weekly` (default **off**, which registers
 nothing), additionally create `lisa-auto-<project>-health-drift` running

package/plugins/lisa/.codex-plugin/skills/lisa-starter-sync/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: lisa-starter-sync
+description: "Run one starter sync using…"
+allowed-tools: ["Bash", "Read", "Skill"]
+---
+
+# Sync the project's starter
+
+Run one `lisa starter sync --json` in the verified project checkout using the
+installed Lisa CLI. The CLI owns diffing, ownership rules, isolated PR worktrees,
+direct-when-clean refusal, and reuse of an existing PR. Do not reproduce them.
+
+For a scheduled invocation, re-read `starter.sync.auto` from the project's
+current config before any mutation. If it is not exactly `true`, report
+`no-change — automatic starter sync is off` and stop. A stale registration must
+not keep applying changes after the operator turns the setting off.
+
+Use a real existing work item when supplied (`--work-item <ref>`) and the actual
+runtime's identity with `--co-author <identity>`. Never invent attribution,
+disable hooks, or open a ticket merely to make an empty sync pass. If project
+commit policy needs attribution that is unavailable, surface that requirement.
+
+Report the returned outcome accurately:
+
+- `current`: **nothing to do**; no changes landed.
+- `committed`: name the resulting commit.
+- `pull-request`: link the existing or newly opened PR; it is awaiting review,
+  not merged and not an advanced consumer baseline. Continue the existing
+  `lisa-drive-pr-to-merge` review workflow with `auto_merge=false` when available.
+- Nonzero exit or malformed output: report the actual failure and any retained
+  worktree location. Do not reset or delete those recovery files.
+
+Never write to the starter repository. Never enable auto-merge as part of this
+command. The same skill is distributed to all six agent runtimes; native slash
+commands use `/lisa:starter-sync`, and Codex uses `$lisa-starter-sync`.

package/plugins/lisa/.codex-plugin/skills/lisa-starter-sync/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "Starter Sync"
+short_description: "Run one starter sync using…"
+default_prompt:
+  - "Use $lisa-starter-sync: Run one starter sync using…."

package/plugins/lisa/commands/starter-sync.md

@@ -0,0 +1,6 @@
+---
+description: "Run one starter sync using the project's existing landing strategy."
+argument-hint: "[--work-item <ref>]"
+---
+
+Use the /lisa-starter-sync skill for one real sync in the current project. $ARGUMENTS

package/plugins/lisa/scripts/automation-status-expected-fleet.mjs

@@ -41,6 +41,10 @@ export const AUTOMATION_EXPECTED_CADENCES = {
     human: "once a day",
     rrule: "FREQ=DAILY;INTERVAL=1",
   },
+  "starter-sync": {
+    human: "once a day",
+    rrule: "FREQ=DAILY;INTERVAL=1",
+  },
   "learnings-audit": {
     human: "once a week",
     rrule: "FREQ=WEEKLY;INTERVAL=1",
@@ -336,6 +340,17 @@ export function resolveExpectedAutomationFleet(input = {}) {
     );
   }
 
+  if (config.starter?.sync?.auto === true) {
+    expected.push(
+      createExpectedEntry(
+        identity,
+        "starter-sync",
+        "/lisa:starter-sync",
+        "opt-in"
+      )
+    );
+  }
+
   return {
     ...identity,
     expected,

package/plugins/lisa/skills/lisa-setup-automations/SKILL.md

@@ -197,6 +197,26 @@ closed by the next run's dedupe or the human), not mutual exclusion; manual
 runs should first confirm the cron is not due or running. Tear-down removes
 it with the rest of the `lisa-auto-<project>-*` set.
 
+**Optional automation — starter sync.** Read `starter.sync.auto` from the
+project's current config. Only the boolean `true` opts in (default **false**).
+When true, reconcile exactly one `lisa-auto-<project>-starter-sync` registration
+running `/lisa:starter-sync` once a **day** (`FREQ=DAILY;INTERVAL=1`) in the
+verified durable project checkout. Use the current runtime's native scheduler
+and update an existing registration by its exact name rather than duplicating
+it. Its prompt must identify this as a scheduled invocation, require a fresh
+check of `starter.sync.auto` before mutation, and carry the literal command on
+its own line. The `lisa-starter-sync` skill calls the shipped CLI and preserves
+its configured landing strategy; an open PR is not an applied update.
+
+When false or absent, remove any exact `lisa-auto-<project>-starter-sync`
+registration using that same native scheduler, leaving all other schedules
+alone. Read the scheduler back after either operation and report the observed
+name, target, cadence, or verified absence. Saving the console toggle only saves
+config: run this reconciliation to change the registration. If scheduler access
+is unavailable, report registration/removal as **unverified**, not successful;
+do not write its backing files or install another scheduler. This representation
+gap applies to any runtime without a native recurring-task tool.
+
 **Optional automation — the health cron.** When `health.schedule` in
 `.lisa.config.json` is `daily` or `weekly` (default **off**, which registers
 nothing), additionally create `lisa-auto-<project>-health-drift` running

package/plugins/lisa/skills/lisa-starter-sync/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: lisa-starter-sync
+description: "Run one starter sync using Lisa's existing engine and landing command. Also used by the opt-in daily starter-sync automation."
+allowed-tools: ["Bash", "Read", "Skill"]
+---
+
+# Sync the project's starter
+
+Run one `lisa starter sync --json` in the verified project checkout using the
+installed Lisa CLI. The CLI owns diffing, ownership rules, isolated PR worktrees,
+direct-when-clean refusal, and reuse of an existing PR. Do not reproduce them.
+
+For a scheduled invocation, re-read `starter.sync.auto` from the project's
+current config before any mutation. If it is not exactly `true`, report
+`no-change — automatic starter sync is off` and stop. A stale registration must
+not keep applying changes after the operator turns the setting off.
+
+Use a real existing work item when supplied (`--work-item <ref>`) and the actual
+runtime's identity with `--co-author <identity>`. Never invent attribution,
+disable hooks, or open a ticket merely to make an empty sync pass. If project
+commit policy needs attribution that is unavailable, surface that requirement.
+
+Report the returned outcome accurately:
+
+- `current`: **nothing to do**; no changes landed.
+- `committed`: name the resulting commit.
+- `pull-request`: link the existing or newly opened PR; it is awaiting review,
+  not merged and not an advanced consumer baseline. Continue the existing
+  `lisa-drive-pr-to-merge` review workflow with `auto_merge=false` when available.
+- Nonzero exit or malformed output: report the actual failure and any retained
+  worktree location. Do not reset or delete those recovery files.
+
+Never write to the starter repository. Never enable auto-merge as part of this
+command. The same skill is distributed to all six agent runtimes; native slash
+commands use `/lisa:starter-sync`, and Codex uses `$lisa-starter-sync`.

package/plugins/lisa/skills/lisa-starter-sync/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "Starter Sync"
+short_description: "Run one starter sync using Lisa's existing engine and landing command"
+default_prompt:
+  - "Use $lisa-starter-sync: Run one starter sync using Lisa's existing engine and landing command."

package/plugins/lisa-agy/commands/lisa/starter-sync.md

@@ -0,0 +1,6 @@
+---
+description: "Run one starter sync using the project's existing landing strategy."
+argument-hint: "[--work-item <ref>]"
+---
+
+Use the /lisa-starter-sync skill for one real sync in the current project. $ARGUMENTS

package/plugins/lisa-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "4.62.4",
+  "version": "4.63.0",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-agy/scripts/automation-status-expected-fleet.mjs

@@ -41,6 +41,10 @@ export const AUTOMATION_EXPECTED_CADENCES = {
     human: "once a day",
     rrule: "FREQ=DAILY;INTERVAL=1",
   },
+  "starter-sync": {
+    human: "once a day",
+    rrule: "FREQ=DAILY;INTERVAL=1",
+  },
   "learnings-audit": {
     human: "once a week",
     rrule: "FREQ=WEEKLY;INTERVAL=1",
@@ -336,6 +340,17 @@ export function resolveExpectedAutomationFleet(input = {}) {
     );
   }
 
+  if (config.starter?.sync?.auto === true) {
+    expected.push(
+      createExpectedEntry(
+        identity,
+        "starter-sync",
+        "/lisa:starter-sync",
+        "opt-in"
+      )
+    );
+  }
+
   return {
     ...identity,
     expected,

package/plugins/lisa-agy/skills/lisa-setup-automations/SKILL.md

@@ -197,6 +197,26 @@ closed by the next run's dedupe or the human), not mutual exclusion; manual
 runs should first confirm the cron is not due or running. Tear-down removes
 it with the rest of the `lisa-auto-<project>-*` set.
 
+**Optional automation — starter sync.** Read `starter.sync.auto` from the
+project's current config. Only the boolean `true` opts in (default **false**).
+When true, reconcile exactly one `lisa-auto-<project>-starter-sync` registration
+running `/lisa:starter-sync` once a **day** (`FREQ=DAILY;INTERVAL=1`) in the
+verified durable project checkout. Use the current runtime's native scheduler
+and update an existing registration by its exact name rather than duplicating
+it. Its prompt must identify this as a scheduled invocation, require a fresh
+check of `starter.sync.auto` before mutation, and carry the literal command on
+its own line. The `lisa-starter-sync` skill calls the shipped CLI and preserves
+its configured landing strategy; an open PR is not an applied update.
+
+When false or absent, remove any exact `lisa-auto-<project>-starter-sync`
+registration using that same native scheduler, leaving all other schedules
+alone. Read the scheduler back after either operation and report the observed
+name, target, cadence, or verified absence. Saving the console toggle only saves
+config: run this reconciliation to change the registration. If scheduler access
+is unavailable, report registration/removal as **unverified**, not successful;
+do not write its backing files or install another scheduler. This representation
+gap applies to any runtime without a native recurring-task tool.
+
 **Optional automation — the health cron.** When `health.schedule` in
 `.lisa.config.json` is `daily` or `weekly` (default **off**, which registers
 nothing), additionally create `lisa-auto-<project>-health-drift` running

package/plugins/lisa-agy/skills/lisa-starter-sync/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: lisa-starter-sync
+description: "Run one starter sync using Lisa's existing engine and landing command. Also used by the opt-in daily starter-sync automation."
+allowed-tools: ["Bash", "Read", "Skill"]
+---
+
+# Sync the project's starter
+
+Run one `lisa starter sync --json` in the verified project checkout using the
+installed Lisa CLI. The CLI owns diffing, ownership rules, isolated PR worktrees,
+direct-when-clean refusal, and reuse of an existing PR. Do not reproduce them.
+
+For a scheduled invocation, re-read `starter.sync.auto` from the project's
+current config before any mutation. If it is not exactly `true`, report
+`no-change — automatic starter sync is off` and stop. A stale registration must
+not keep applying changes after the operator turns the setting off.
+
+Use a real existing work item when supplied (`--work-item <ref>`) and the actual
+runtime's identity with `--co-author <identity>`. Never invent attribution,
+disable hooks, or open a ticket merely to make an empty sync pass. If project
+commit policy needs attribution that is unavailable, surface that requirement.
+
+Report the returned outcome accurately:
+
+- `current`: **nothing to do**; no changes landed.
+- `committed`: name the resulting commit.
+- `pull-request`: link the existing or newly opened PR; it is awaiting review,
+  not merged and not an advanced consumer baseline. Continue the existing
+  `lisa-drive-pr-to-merge` review workflow with `auto_merge=false` when available.
+- Nonzero exit or malformed output: report the actual failure and any retained
+  worktree location. Do not reset or delete those recovery files.
+
+Never write to the starter repository. Never enable auto-merge as part of this
+command. The same skill is distributed to all six agent runtimes; native slash
+commands use `/lisa:starter-sync`, and Codex uses `$lisa-starter-sync`.

package/plugins/lisa-cdk/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "4.62.4",
+  "version": "4.63.0",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "4.62.4",
+  "version": "4.63.0",
   "description": "AWS CDK-specific Lisa plugin.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "4.62.4",
+  "version": "4.63.0",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "4.62.4",
+  "version": "4.63.0",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "4.62.4",
+  "version": "4.63.0",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "4.62.4",
+  "version": "4.63.0",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-copilot/commands/lisa/starter-sync.md

@@ -0,0 +1,6 @@
+---
+description: "Run one starter sync using the project's existing landing strategy."
+argument-hint: "[--work-item <ref>]"
+---
+
+Use the /lisa-starter-sync skill for one real sync in the current project. $ARGUMENTS

package/plugins/lisa-copilot/scripts/automation-status-expected-fleet.mjs

@@ -41,6 +41,10 @@ export const AUTOMATION_EXPECTED_CADENCES = {
     human: "once a day",
     rrule: "FREQ=DAILY;INTERVAL=1",
   },
+  "starter-sync": {
+    human: "once a day",
+    rrule: "FREQ=DAILY;INTERVAL=1",
+  },
   "learnings-audit": {
     human: "once a week",
     rrule: "FREQ=WEEKLY;INTERVAL=1",
@@ -336,6 +340,17 @@ export function resolveExpectedAutomationFleet(input = {}) {
     );
   }
 
+  if (config.starter?.sync?.auto === true) {
+    expected.push(
+      createExpectedEntry(
+        identity,
+        "starter-sync",
+        "/lisa:starter-sync",
+        "opt-in"
+      )
+    );
+  }
+
   return {
     ...identity,
     expected,

package/plugins/lisa-copilot/skills/lisa-setup-automations/SKILL.md

@@ -197,6 +197,26 @@ closed by the next run's dedupe or the human), not mutual exclusion; manual
 runs should first confirm the cron is not due or running. Tear-down removes
 it with the rest of the `lisa-auto-<project>-*` set.
 
+**Optional automation — starter sync.** Read `starter.sync.auto` from the
+project's current config. Only the boolean `true` opts in (default **false**).
+When true, reconcile exactly one `lisa-auto-<project>-starter-sync` registration
+running `/lisa:starter-sync` once a **day** (`FREQ=DAILY;INTERVAL=1`) in the
+verified durable project checkout. Use the current runtime's native scheduler
+and update an existing registration by its exact name rather than duplicating
+it. Its prompt must identify this as a scheduled invocation, require a fresh
+check of `starter.sync.auto` before mutation, and carry the literal command on
+its own line. The `lisa-starter-sync` skill calls the shipped CLI and preserves
+its configured landing strategy; an open PR is not an applied update.
+
+When false or absent, remove any exact `lisa-auto-<project>-starter-sync`
+registration using that same native scheduler, leaving all other schedules
+alone. Read the scheduler back after either operation and report the observed
+name, target, cadence, or verified absence. Saving the console toggle only saves
+config: run this reconciliation to change the registration. If scheduler access
+is unavailable, report registration/removal as **unverified**, not successful;
+do not write its backing files or install another scheduler. This representation
+gap applies to any runtime without a native recurring-task tool.
+
 **Optional automation — the health cron.** When `health.schedule` in
 `.lisa.config.json` is `daily` or `weekly` (default **off**, which registers
 nothing), additionally create `lisa-auto-<project>-health-drift` running

package/plugins/lisa-copilot/skills/lisa-starter-sync/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: lisa-starter-sync
+description: "Run one starter sync using Lisa's existing engine and landing command. Also used by the opt-in daily starter-sync automation."
+allowed-tools: ["Bash", "Read", "Skill"]
+---
+
+# Sync the project's starter
+
+Run one `lisa starter sync --json` in the verified project checkout using the
+installed Lisa CLI. The CLI owns diffing, ownership rules, isolated PR worktrees,
+direct-when-clean refusal, and reuse of an existing PR. Do not reproduce them.
+
+For a scheduled invocation, re-read `starter.sync.auto` from the project's
+current config before any mutation. If it is not exactly `true`, report
+`no-change — automatic starter sync is off` and stop. A stale registration must
+not keep applying changes after the operator turns the setting off.
+
+Use a real existing work item when supplied (`--work-item <ref>`) and the actual
+runtime's identity with `--co-author <identity>`. Never invent attribution,
+disable hooks, or open a ticket merely to make an empty sync pass. If project
+commit policy needs attribution that is unavailable, surface that requirement.
+
+Report the returned outcome accurately:
+
+- `current`: **nothing to do**; no changes landed.
+- `committed`: name the resulting commit.
+- `pull-request`: link the existing or newly opened PR; it is awaiting review,
+  not merged and not an advanced consumer baseline. Continue the existing
+  `lisa-drive-pr-to-merge` review workflow with `auto_merge=false` when available.
+- Nonzero exit or malformed output: report the actual failure and any retained
+  worktree location. Do not reset or delete those recovery files.
+
+Never write to the starter repository. Never enable auto-merge as part of this
+command. The same skill is distributed to all six agent runtimes; native slash
+commands use `/lisa:starter-sync`, and Codex uses `$lisa-starter-sync`.

package/plugins/lisa-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "4.62.4",
+  "version": "4.63.0",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cursor/commands/lisa/starter-sync.md

@@ -0,0 +1,6 @@
+---
+description: "Run one starter sync using the project's existing landing strategy."
+argument-hint: "[--work-item <ref>]"
+---
+
+Use the /lisa-starter-sync skill for one real sync in the current project. $ARGUMENTS

package/plugins/lisa-cursor/scripts/automation-status-expected-fleet.mjs

@@ -41,6 +41,10 @@ export const AUTOMATION_EXPECTED_CADENCES = {
     human: "once a day",
     rrule: "FREQ=DAILY;INTERVAL=1",
   },
+  "starter-sync": {
+    human: "once a day",
+    rrule: "FREQ=DAILY;INTERVAL=1",
+  },
   "learnings-audit": {
     human: "once a week",
     rrule: "FREQ=WEEKLY;INTERVAL=1",
@@ -336,6 +340,17 @@ export function resolveExpectedAutomationFleet(input = {}) {
     );
   }
 
+  if (config.starter?.sync?.auto === true) {
+    expected.push(
+      createExpectedEntry(
+        identity,
+        "starter-sync",
+        "/lisa:starter-sync",
+        "opt-in"
+      )
+    );
+  }
+
   return {
     ...identity,
     expected,

package/plugins/lisa-cursor/skills/lisa-setup-automations/SKILL.md

@@ -197,6 +197,26 @@ closed by the next run's dedupe or the human), not mutual exclusion; manual
 runs should first confirm the cron is not due or running. Tear-down removes
 it with the rest of the `lisa-auto-<project>-*` set.
 
+**Optional automation — starter sync.** Read `starter.sync.auto` from the
+project's current config. Only the boolean `true` opts in (default **false**).
+When true, reconcile exactly one `lisa-auto-<project>-starter-sync` registration
+running `/lisa:starter-sync` once a **day** (`FREQ=DAILY;INTERVAL=1`) in the
+verified durable project checkout. Use the current runtime's native scheduler
+and update an existing registration by its exact name rather than duplicating
+it. Its prompt must identify this as a scheduled invocation, require a fresh
+check of `starter.sync.auto` before mutation, and carry the literal command on
+its own line. The `lisa-starter-sync` skill calls the shipped CLI and preserves
+its configured landing strategy; an open PR is not an applied update.
+
+When false or absent, remove any exact `lisa-auto-<project>-starter-sync`
+registration using that same native scheduler, leaving all other schedules
+alone. Read the scheduler back after either operation and report the observed
+name, target, cadence, or verified absence. Saving the console toggle only saves
+config: run this reconciliation to change the registration. If scheduler access
+is unavailable, report registration/removal as **unverified**, not successful;
+do not write its backing files or install another scheduler. This representation
+gap applies to any runtime without a native recurring-task tool.
+
 **Optional automation — the health cron.** When `health.schedule` in
 `.lisa.config.json` is `daily` or `weekly` (default **off**, which registers
 nothing), additionally create `lisa-auto-<project>-health-drift` running

package/plugins/lisa-cursor/skills/lisa-starter-sync/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: lisa-starter-sync
+description: "Run one starter sync using Lisa's existing engine and landing command. Also used by the opt-in daily starter-sync automation."
+allowed-tools: ["Bash", "Read", "Skill"]
+---
+
+# Sync the project's starter
+
+Run one `lisa starter sync --json` in the verified project checkout using the
+installed Lisa CLI. The CLI owns diffing, ownership rules, isolated PR worktrees,
+direct-when-clean refusal, and reuse of an existing PR. Do not reproduce them.
+
+For a scheduled invocation, re-read `starter.sync.auto` from the project's
+current config before any mutation. If it is not exactly `true`, report
+`no-change — automatic starter sync is off` and stop. A stale registration must
+not keep applying changes after the operator turns the setting off.
+
+Use a real existing work item when supplied (`--work-item <ref>`) and the actual
+runtime's identity with `--co-author <identity>`. Never invent attribution,
+disable hooks, or open a ticket merely to make an empty sync pass. If project
+commit policy needs attribution that is unavailable, surface that requirement.
+
+Report the returned outcome accurately:
+
+- `current`: **nothing to do**; no changes landed.
+- `committed`: name the resulting commit.
+- `pull-request`: link the existing or newly opened PR; it is awaiting review,
+  not merged and not an advanced consumer baseline. Continue the existing
+  `lisa-drive-pr-to-merge` review workflow with `auto_merge=false` when available.
+- Nonzero exit or malformed output: report the actual failure and any retained
+  worktree location. Do not reset or delete those recovery files.
+
+Never write to the starter repository. Never enable auto-merge as part of this
+command. The same skill is distributed to all six agent runtimes; native slash
+commands use `/lisa:starter-sync`, and Codex uses `$lisa-starter-sync`.

package/plugins/lisa-expo/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "4.62.4",
+  "version": "4.63.0",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "4.62.4",
+  "version": "4.63.0",
   "description": "Expo and React Native-specific skills, agents, rules, and MCP servers.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "4.62.4",
+  "version": "4.63.0",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "4.62.4",
+  "version": "4.63.0",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "4.62.4",
+  "version": "4.63.0",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"