@aperant/framework 0.6.3 → 0.6.4

package/skills/apt/SKILL.md

@@ -9,6 +9,7 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: none
 default_execution_mode: auto
 execution_modes:
   - auto
@@ -139,13 +140,118 @@ Show current state summary and autonomy flags (`--supervised`, `--guided`, `--au
 
 The user invoked a specific skill by name (e.g., `/apt plan`, `/apt resume`,
 `/apt:ship`). The router matched the first word against the installed skill
-set and filled in `skill`, `skill_args`, `spawn_agent`, and `agent`.
+set and filled in `skill`, `skill_args`, `spawn_agent`, `agent`, AND
+`task_context` + (optional) `default_track`.
 
-**If `spawn_agent` is true:**
-Spawn the appropriate agent from the routing result. Pass `skill_args` as context.
+Dispatch on `task_context` — never just on `spawn_agent`. The four-branch
+policy below is hardcoded contract; do NOT improvise. See
+`docs/frameworks/spec-gaps.md#g25` for the defect that motivated this.
 
-**If `spawn_agent` is false:**
-Invoke the skill directly: call `apt:{skill}` with `skill_args`.
+### Missing `task_context` — fail-closed
+
+When the envelope's `task_context` is null (the `?? null` fallback in
+`route.mjs:skillIndex.taskContextOf`), print verbatim and STOP. Do NOT
+invoke the skill:
+
+```
+[APT] ERROR — skill "apt:{skill}" has no task_context declared in SKILL.md frontmatter.
+       Cannot dispatch safely until the policy is set. Run /apt:author-skill validate
+       packages/framework/skills/apt-{skill}/SKILL.md to see required keys.
+```
+
+**Note:** In practice, a skill missing `task_context` is dropped by
+`discoverSkills` during the Zod schema validation step and will never reach
+the skill-passthrough branch — it will be absent from `knownSlugs`. The
+user sees the skill disappear silently from routing; run
+`apt-tools route .` to surface dropped skills logged to
+`.aperant/logs/route-dropped.jsonl`. The `task_context: null` path is
+reachable if the field is marked optional in a future schema version —
+this error fires in that case.
+
+### `task_context = none`
+
+No task semantics. Invoke the skill directly with `skill_args` (or spawn
+`agent` when `spawn_agent` is true). No `task create`, no worktree banner.
+
+### `task_context = self-managed`
+
+The skill manages its own task / worktree lifecycle (e.g. `apt:run` calls
+`task create` in its own Step 2; `apt:pr-review` sets up a PR-scoped
+worktree). Dispatch identically to `none` — the skill's own SKILL.md is
+responsible for any task record + worktree banner.
+
+### `task_context = create-new`
+
+Resolve the track, then create a fresh task record before invoking the skill.
+
+**Track resolution chain (first match wins):**
+
+1. Explicit user flag in `skill_args` — `--quick` → `QUICK`, `--deep` → `DEEP`,
+   `--debug` → `DEBUG`.
+2. `envelope.default_track` if present (the skill's declared default).
+3. Per-slug hardcoded fallback:
+   - `quick` → `QUICK`
+   - `debug` → `DEBUG`
+   - `plan` → `STANDARD`
+   - everything else with `task_context: create-new` → `STANDARD`
+
+Then run:
+
+```bash
+node packages/framework/bin/apt-tools.mjs task create . --description "{slug}" --track {track} --autonomy {autonomy} [--scope {scope}]
+```
+
+**Security note:** Do NOT interpolate `{skill_args}` directly into `--description "..."`. `skill_args` is verbatim user input and can contain double-quote characters that break out of the argument boundary and inject extra flags (e.g. `--autonomy`, `--scope`). The task slug is sufficient as the description; `skill_args` is passed to the skill separately after the task record is created.
+
+(Use `--scope framework` only when the user is on a framework-scoped task —
+otherwise omit and let the default `project` scope apply.)
+
+Parse `task_id`, `task_dir`, and (if present) `worktree.worktree_path` /
+`worktree.branch` / `worktree.base_branch` from the result. Print the
+worktree banner when `worktree` is returned:
+
+```
+[APT] Working in isolated worktree: {worktree_path}
+[APT] Task branch: {branch} (from {base_branch})
+```
+
+Then invoke `apt:{skill}` with `skill_args` + the new task context
+(`task_id`, `task_dir`, `worktree_path`). When `spawn_agent` is true, spawn
+`agent` with the same context.
+
+### `task_context = require-existing`
+
+Resolve which active task this invocation refers to, then dispatch. Read
+`state.active_tasks` from `.aperant/state.json`.
+
+**Active-task resolution chain (first match wins):**
+
+1. `--task-id <id>` flag present in `skill_args` → use it. If `<id>` is not
+   in `state.active_tasks`, error and stop.
+2. `state.active_tasks` has exactly one entry AND that entry's
+   `lifecycle_phase` is non-terminal (`planning`, `executing`, `verifying`,
+   `reviewing`) → use it. If the single entry is in a terminal phase
+   (`shipped-pending-merge` or `rejected`), fall through to step 4.
+3. `state.active_tasks` has more than one entry with exactly one in a
+   non-terminal lifecycle phase (`planning`, `executing`, `verifying`,
+   `reviewing`) → use it.
+   (Terminal phases in `active_tasks` are `shipped-pending-merge` and
+   `rejected`. Note: `completed` tasks are removed from `active_tasks`
+   entirely at close and can never appear here.)
+4. Otherwise, print the numbered menu and STOP. Auto-mode (autonomy 2/3)
+   does NOT bypass this prompt — multi-task ambiguity is the user's call,
+   never the framework's guess:
+
+   ```
+   [APT] Multiple active tasks — pick one with `--task-id <id>`:
+     1. {task-id-1}  {description}  ({lifecycle_phase})
+     2. {task-id-2}  {description}  ({lifecycle_phase})
+     ...
+   ```
+
+Once resolved, print the worktree banner if the task has a `worktree_path`,
+then invoke `apt:{skill}` with `skill_args` + the resolved `task_id`. When
+`spawn_agent` is true, spawn `agent` with the same context.
 
 ---
 

package/skills/apt-author-skill/SKILL.md

@@ -9,6 +9,7 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: create-new
 default_execution_mode: step
 execution_modes:
   - auto
@@ -129,6 +130,16 @@ the author sees the full checklist of gaps to fill. Group by section:
 The generated structural test only checks tags and numbered steps — the
 TODOs are the semantic gaps the author must close.
 
+**Required frontmatter field — `task_context`.** The scaffold ships with
+`task_context: create-new` as the safest default (the new skill will get a
+fresh task record + worktree via `apt-tools task create` when invoked as
+`/apt <slug>`). Verify this is correct for your skill before merging — the
+allowed values are `create-new | require-existing | self-managed | none`.
+See `packages/framework/docs/skill-passthrough.md` for the four-policy
+contract and the orchestrator dispatch behavior. Missing or wrong values
+are caught by the structural test in
+`packages/framework/src/__tests__/skill-frontmatter-task-context.test.ts`.
+
 ## 4. Show the Structural Test
 
 Read the generated structural test file and echo its contents so the

package/skills/apt-bootstrap/SKILL.md

@@ -9,6 +9,7 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: none
 default_execution_mode: auto
 execution_modes:
   - auto

package/skills/apt-classify/SKILL.md

@@ -9,6 +9,7 @@ user_invocable: false
 internal: true
 spawns_agent: false
 agent_name: null
+task_context: none
 default_execution_mode: auto
 execution_modes:
   - auto

package/skills/apt-close-task/SKILL.md

@@ -9,6 +9,7 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: require-existing
 default_execution_mode: auto
 execution_modes:
   - auto

package/skills/apt-create-docs/SKILL.md

@@ -9,6 +9,7 @@ user_invocable: true
 internal: false
 spawns_agent: true
 agent_name: apt-docs-author
+task_context: create-new
 default_execution_mode: auto
 execution_modes:
   - auto

package/skills/apt-debug/SKILL.md

@@ -9,6 +9,8 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: create-new
+default_track: DEBUG
 default_execution_mode: auto
 execution_modes:
   - auto

package/skills/apt-design/SKILL.md

@@ -9,6 +9,8 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: create-new
+default_track: STANDARD
 default_execution_mode: step
 execution_modes:
   - auto

package/skills/apt-discuss/SKILL.md

@@ -9,6 +9,8 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: create-new
+default_track: STANDARD
 default_execution_mode: step
 execution_modes:
   - auto

package/skills/apt-docs/SKILL.md

@@ -9,6 +9,8 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: create-new
+default_track: STANDARD
 default_execution_mode: auto
 execution_modes:
   - auto

package/skills/apt-execute/SKILL.md

@@ -9,6 +9,7 @@ user_invocable: true
 internal: false
 spawns_agent: true
 agent_name: "apt-executor"
+task_context: require-existing
 default_execution_mode: auto
 execution_modes:
   - auto

package/skills/apt-mockup/SKILL.md

@@ -9,6 +9,8 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: create-new
+default_track: STANDARD
 default_execution_mode: step
 execution_modes:
   - auto

package/skills/apt-pause/SKILL.md

@@ -9,6 +9,7 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: none
 default_execution_mode: auto
 execution_modes:
   - auto

package/skills/apt-personas/SKILL.md

@@ -9,6 +9,7 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: none
 default_execution_mode: auto
 execution_modes:
   - auto

package/skills/apt-plan/SKILL.md

@@ -9,6 +9,8 @@ user_invocable: true
 internal: false
 spawns_agent: true
 agent_name: "apt-planner"
+task_context: create-new
+default_track: STANDARD
 default_execution_mode: auto
 execution_modes:
   - auto

package/skills/apt-pr-review/SKILL.md

@@ -9,6 +9,7 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: self-managed
 default_execution_mode: auto
 execution_modes:
   - auto

package/skills/apt-quick/SKILL.md

@@ -9,6 +9,8 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: create-new
+default_track: QUICK
 default_execution_mode: auto
 execution_modes:
   - auto

package/skills/apt-resume/SKILL.md

@@ -9,6 +9,7 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: none
 default_execution_mode: auto
 execution_modes:
   - auto

package/skills/apt-review/SKILL.md

@@ -9,6 +9,7 @@ user_invocable: true
 internal: false
 spawns_agent: true
 agent_name: "apt-reviewer"
+task_context: require-existing
 default_execution_mode: auto
 execution_modes:
   - auto

package/skills/apt-roadmap/SKILL.md

@@ -9,6 +9,7 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: none
 default_execution_mode: step
 execution_modes:
   - auto

package/skills/apt-roundtable/SKILL.md

@@ -9,6 +9,8 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: create-new
+default_track: DEEP
 default_execution_mode: auto
 execution_modes:
   - auto

package/skills/apt-run/SKILL.md

@@ -9,6 +9,7 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: self-managed
 default_execution_mode: auto
 execution_modes:
   - auto

package/skills/apt-scan/SKILL.md

@@ -9,6 +9,7 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: none
 default_execution_mode: auto
 execution_modes:
   - auto

package/skills/apt-setup/SKILL.md

@@ -9,6 +9,7 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: none
 default_execution_mode: step
 execution_modes:
   - auto

package/skills/apt-ship/SKILL.md

@@ -9,6 +9,7 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: require-existing
 default_execution_mode: auto
 execution_modes:
   - auto
@@ -288,6 +289,8 @@ Capture the PR URL from the output into `pr_url` (for example, the last line of
 node packages/framework/bin/apt-tools.mjs task update . --id {task-id} --pr-url {PR_URL}
 ```
 
+This same call **atomically flips `lifecycle_phase` from `reviewing` to `shipped-pending-merge`** when the task is in `reviewing` and no explicit `--lifecycle-phase` flag is passed. Section 6 is now the single load-bearing step that both records the PR and transitions the lifecycle; Section 8 below documents the semantics but no longer issues a separate command.
+
 Display the resolution so users see which branch/base was used:
 
 ```
@@ -338,7 +341,7 @@ suggest_mode=$(jq -r '.pr_review.suggest_after_ship // "always"' .aperant/config
   ```
   [APT:ship] Run /apt:pr-review --pr {pr_number} now for deep multi-agent review? [Y/n]
   ```
-  On `Y` (or empty enter), invoke `/apt:pr-review --pr {pr_number}` inline after Section 8 flips the task to `shipped-pending-merge` — do NOT block the lifecycle transition. On `N` or any other response, proceed silently to Section 8.
+  On `Y` (or empty enter), invoke `/apt:pr-review --pr {pr_number}` inline — the task has already been flipped to `shipped-pending-merge` atomically by the `--pr-url` recording in Section 6, so the deep-review hint does NOT need to block on Section 8. On `N` or any other response, proceed silently to Section 8.
 
 - **`never`** — silent. Proceed directly to Section 8.
 
@@ -346,11 +349,9 @@ suggest_mode=$(jq -r '.pr_review.suggest_after_ship // "always"' .aperant/config
 
 ## 8. Transition lifecycle to `shipped-pending-merge` (C56 B5)
 
-Ship is NOT the final closer. The PR has just been opened — it won't merge for minutes, hours, or days, and no agent will be present on merge. Instead of closing the task now, flip its lifecycle to `shipped-pending-merge` — the intermediate state between `reviewing` and `completed`. `/apt:close-task` runs post-merge (either manually via `/apt:close-task --all` or by the user when they return to the repo) and performs the actual closeout: phase flip, documentation narration, worktree GC, per-PR config strip, task archive.
+Ship is NOT the final closer. The PR has just been opened — it won't merge for minutes, hours, or days, and no agent will be present on merge. The task lifecycle is now `shipped-pending-merge` — the intermediate state between `reviewing` and `completed`. `/apt:close-task` runs post-merge (either manually via `/apt:close-task --all` or by the user when they return to the repo) and performs the actual closeout: phase flip, documentation narration, worktree GC, per-PR config strip, task archive.
 
-```bash
-node packages/framework/bin/apt-tools.mjs task update . --id {task-id} --lifecycle-phase shipped-pending-merge
-```
+Section 6 already performed this transition atomically as part of `task update --pr-url`. This section documents the semantics; no separate command is required.
 
 The task stays in `state.active_tasks[*]` with `lifecycle_phase: "shipped-pending-merge"`. Do NOT call `task close` here — that would mark it `completed` before the PR is actually merged, producing the same artifact drift C56 was built to eliminate.
 

package/skills/apt-stress-test/SKILL.md

@@ -9,6 +9,7 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: require-existing
 default_execution_mode: step
 execution_modes:
   - auto

package/skills/apt-terminal/SKILL.md

@@ -9,6 +9,7 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: none
 default_execution_mode: step
 execution_modes:
   - auto

package/skills/apt-update/SKILL.md

@@ -9,6 +9,7 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: none
 default_execution_mode: auto
 execution_modes:
   - auto
@@ -69,6 +70,8 @@ Build the flags list from the runtime ids (e.g. `--claude --codex`) and run:
 node .aperant/deps/node_modules/@aperant/framework/bin/apt-tools.mjs init . <flags>
 ```
 
+**Do NOT add `--yes`, `--solo`, `--team`, or any other Class A flag.** This command is meant to refresh runtime files only — adding `--yes` triggers a config schema migration that can silently flip `share.visibility` to `solo` and re-write `.gitignore`, which is exactly the 0.6.0/0.6.1 dogfood bug. If `init` returns a `requires_input` envelope (schema drift), surface it to the user verbatim and stop; let them decide team vs solo with the explicit flag. From 0.6.4 onward `--yes` infers visibility from existing git tracking, but the skill must still not add it — keep this command scoped to runtime refresh.
+
 Parse the init JSON. Capture for each runtime:
 - `install_root` (shortened to the basename, e.g. `.claude`)
 - `file_count`

package/skills/apt-verify/SKILL.md

@@ -9,6 +9,7 @@ user_invocable: true
 internal: false
 spawns_agent: true
 agent_name: "apt-verifier"
+task_context: require-existing
 default_execution_mode: auto
 execution_modes:
   - auto

package/skills/apt-verify-proof/SKILL.md

@@ -9,6 +9,7 @@ user_invocable: true
 internal: false
 spawns_agent: false
 agent_name: null
+task_context: require-existing
 default_execution_mode: auto
 execution_modes:
   - auto

package/src/cli/artifacts/classification.mjs

@@ -174,6 +174,11 @@ const RULES = Object.freeze([
 		class: ARTIFACT_CLASS.EPHEMERAL,
 		why: 'Append-only daily log of lifecycle transitions.',
 	},
+	{
+		pattern: '.aperant/install/**',
+		class: ARTIFACT_CLASS.EPHEMERAL,
+		why: 'Install telemetry/summaries (last-init/last-install) — runtime artifacts.',
+	},
 	{
 		pattern: '.aperant/team-status/**',
 		class: ARTIFACT_CLASS.EPHEMERAL,
@@ -249,6 +254,11 @@ const RULES = Object.freeze([
 		class: ARTIFACT_CLASS.EPHEMERAL,
 		why: 'Design-scan outputs (tokens, extracted repo, synthesis) — rebuildable.',
 	},
+	{
+		pattern: '.aperant/product-context.json',
+		class: ARTIFACT_CLASS.EPHEMERAL,
+		why: 'Derived/read-through sidecar used by CLI flows; rebuilt from onboarding context.',
+	},
 	// ── Explicit ephemeral: secrets/tokens MUST never classify committable ─
 	{
 		pattern: '.aperant/secrets/**',

package/src/cli/commands/init.mjs

@@ -15,6 +15,7 @@
  * half is replaced.
  */
 
+import { execSync } from 'node:child_process'
 import {
 	copyFileSync,
 	existsSync,
@@ -222,6 +223,51 @@ function buildRerunWithHint(projectDir, parsedFlags, requiresExplicit) {
 	return `apt-tools init ${projectDir} ${flags.join(' ')}`.trim()
 }
 
+/**
+ * Infer `share.visibility` from the target's git tracking state.
+ *
+ * Repos that already track files inside `.aperant/` or any runtime root
+ * (`.claude/`, `.codex/`, …) are *behaviourally* team-mode: contributors
+ * pull the framework's installed files via git, not via local
+ * `apt-tools init`. Treating them as solo on an upgrade (the old `--yes`
+ * default did exactly this — bumped the schema, silently wrote
+ * `visibility: 'solo'`, and the project-gitignore allow-list flipped)
+ * is a destructive, non-obvious surprise. The 0.6.0/0.6.1 dogfood
+ * incidents both hit this rake.
+ *
+ * Returns:
+ *   - `'team'` when any tracked file lives under `.aperant/` or a runtime
+ *     root.
+ *   - `'solo'` when the dir is a git repo but no such tracked file
+ *     exists.
+ *   - `undefined` when the target isn't a git repo (caller falls back to
+ *     the descriptor default, which preserves greenfield behaviour).
+ *
+ * @param {string} targetDir
+ * @returns {'team'|'solo'|undefined}
+ */
+function inferVisibilityFromGit(targetDir) {
+	try {
+		execSync('git rev-parse --is-inside-work-tree 2>/dev/null', {
+			cwd: targetDir,
+			stdio: ['ignore', 'ignore', 'ignore'],
+		})
+	} catch {
+		return undefined
+	}
+	const probePaths = ['.aperant', ...RUNTIMES.map((r) => r.installRoot)]
+	try {
+		const out = execSync(`git ls-files -- ${probePaths.map((p) => `'${p}'`).join(' ')}`, {
+			cwd: targetDir,
+			encoding: 'utf8',
+			stdio: ['ignore', 'pipe', 'ignore'],
+		}).trim()
+		return out.length > 0 ? 'team' : 'solo'
+	} catch {
+		return 'solo'
+	}
+}
+
 /**
  * Apply Class A defaults that were collapsed under --yes /
  * --accept-new-defaults back into the migrated config so finishInit
@@ -243,21 +289,36 @@ function buildRerunWithHint(projectDir, parsedFlags, requiresExplicit) {
  * writes — keeps the prototype-pollution guard and dot-path semantics in
  * one place.
  *
+ * `overrides` lets callers substitute the descriptor default for a
+ * specific shortKey — used in the upgrade path to honour
+ * `inferVisibilityFromGit`, so a team repo that ran `--yes` doesn't get
+ * silently flipped to solo.
+ *
  * @param {{ migrated: Record<string, unknown>, applied_defaults: Array<{ key: string, value: unknown, why: string, source?: string }> }} migration
  * @param {Array<{ key: string, why: string, default?: unknown }>} collapsedEntries
  * @param {string} source              `--yes` or `--accept-new-defaults`.
  * @param {unknown} templateVersion    Template's version, applied to migrated.
+ * @param {Record<string, unknown>} [overrides]  shortKey → inferred value.
  */
-function applyCollapsedClassAToMigration(migration, collapsedEntries, source, templateVersion) {
+function applyCollapsedClassAToMigration(
+	migration,
+	collapsedEntries,
+	source,
+	templateVersion,
+	overrides = {},
+) {
 	for (const r of collapsedEntries) {
 		const desc = findClassDescriptor(r.key)
 		if (!desc) continue
-		setAt(migration.migrated, desc.key, desc.default)
+		const hasOverride = Object.hasOwn(overrides, desc.shortKey)
+		const value = hasOverride ? overrides[desc.shortKey] : desc.default
+		const recordedSource = hasOverride ? `${source} (inferred from git tracking)` : source
+		setAt(migration.migrated, desc.key, value)
 		migration.applied_defaults.push({
 			key: desc.shortKey,
-			value: desc.default,
+			value,
 			why: r.why,
-			source,
+			source: recordedSource,
 		})
 	}
 	if (templateVersion !== undefined) {
@@ -318,7 +379,24 @@ function nonInteractiveAnswers(targetDir, canonicalRoot, archetype, parsedFlags)
 		// solo-mode — re-introducing the 0.6.0 dogfood bug.
 		let requires = migration.requires_explicit
 		if (parsedFlags.yes && requires.length > 0) {
-			applyCollapsedClassAToMigration(migration, requires, '--yes', templateConfig.version)
+			// Prefer evidence over descriptor defaults: a repo that already
+			// tracks `.aperant/` or any runtime root is team-mode by
+			// behaviour. Without this, `--yes` flips long-tracked repos to
+			// solo on the v3→v4 schema bump (0.6.0/0.6.1 dogfood incidents).
+			// Explicit --solo/--team in parsedFlags wins; only collapse-time
+			// inference runs here.
+			const overrides = {}
+			if (!parsedFlags.visibility && requires.some((r) => r.key === 'visibility')) {
+				const inferred = inferVisibilityFromGit(targetDir)
+				if (inferred !== undefined) overrides.visibility = inferred
+			}
+			applyCollapsedClassAToMigration(
+				migration,
+				requires,
+				'--yes',
+				templateConfig.version,
+				overrides,
+			)
 			requires = []
 		} else if (parsedFlags.accept_new_defaults && requires.length > 0) {
 			// --accept-new-defaults applies template defaults for new Class A