auto-sync-back-when-enabled

Auto Sync-Back When Enabled — Don’t Ask, Just Spawn

Always-loaded behavioral rule. Flags ON + a sync-queue reminder ⇒ spawn the background sub-agent immediately, without asking for approval.

Rule

If features.autoLessonSync, features.autoLibrarySync, or features.autoIssueSubmission is true in the resolved t1k-config-*.json (check .claude/t1k-config-core.json), then on seeing [t1k:lib-sync-queue], [t1k:lesson-queue] / [t1k:lesson-queued], or [t1k:auto-issue], the assistant MUST immediately spawn the prescribed background sub-agent (t1k-kit-developer, run_in_background: true) per the reminder’s Action block — and MUST NOT pause to ask “want me to sync-back?” / “should I open the PRs?”.

Asking for approval to sync-back when these flags are ON is a rule violation. The flags ARE the standing approval. Report the resulting URL after the agent returns; never gate the spawn on a confirmation.

Auto-spawn covers OPENING the PR/issue only — merge, force-push, and conflict resolution still follow kit-pr-workflow-boundary.md (consumer opens, kit maintainer merges).

When NOT to auto-spawn

The relevant flag is false → fall back to offering (the user opted out of automation).
The reminder is a duplicate of an entry already submitted this session (dedup cache / writeback submitted:true).
You are at the leaf of the depth budget (depth 3) or would exceed your depth’s fan-out cap, per agent-security-boilerplate.md — report the queue entry up instead of spawning.

Full details

Flag-resolution procedure, the reminder→flag table, the originating incident (2026-06-04/05 Amplify/Feel cook) and full cross-references: docs/auto-sync-back-when-enabled.md.

error-recovery.md (spawn pattern) · orchestration-rules.md (background-only) · kit-pr-workflow-boundary.md · skills/t1k-sync-back/SKILL.md § “Pre-flight Step 0 — Kit-Freshness Guard” · telemetry.md