atm-git-pathspec-emergency-commit

name	atm-git-pathspec-emergency-commit
description	Emergency-only runbook for a one-time path-bounded native Git commit when ATM governed commit, WIP park, or commit-candidate lanes are blocked and the owner explicitly authorizes anomaly recovery. Not a Plan 3.1 autonomous success path.
argument-hint	<ATM context>
charter-invariants-injected	true

Git Pathspec Emergency Commit Repair

Use this skill only as an emergency/anomaly repair runbook. Direct Git pathspec or native commit is emergency-only and is excluded from autonomous Plan 3.1 success metrics. Prefer ATM governed task / claim / broker / git commit / taskflow close whenever those lanes can complete. Do not treat Git pathspec as ATM core concurrency.

Authority preconditions

Enter this skill only when all of the following hold:

1. The project owner or captain explicitly grants emergency authority for a path-bounded commit, or ATM returned a hard blocker with no executable recoveryCommand.
2. Normal ATM recovery was attempted or ruled out: governed node atm.mjs git commit, WIP park, commit-candidate / broker ticket, and claim re-attach when applicable.
3. The keep-list of paths is provided by the captain/task card. Never infer the keep-list from every dirty file in the worktree.
4. You will record or reference a backlog/follow-up item explaining why ATM lacked a normal recovery route (for example same-task unowned WIP with no reclaim command).

If any precondition is missing, stop and ask for authority. Using this skill for ordinary delivery is a Plan 3.1 failure signal, not a success pattern.

Compact emergency checklist

1. Capture baseline (read-only)

git status --short
git diff --cached --name-only
node atm.mjs broker status --json

Confirm broker is understood and unrelated residue is not silently consumed.

2. Exact keep-list staging

• Build an explicit keep-list from the captain/task card.
• Stage only keep-list paths with path-bounded git add -- <paths>.
• Exact staged-set verification: git diff --cached --name-only must exactly equal the keep-list (same paths, no extras, no missing entries).
• If the staged set differs, stop. Do not commit.

Forbidden without a separate human destructive/recovery approval:

• git restore (working tree or destructive restore)
• git stash
• git clean
• git reset
• git checkout
• broad git add -A / git add .

Index-only unstage of non-keep-list paths may be used only when the captain explicitly authorizes index adjustment and working-tree content must remain unchanged.

3. Focused validators

Run focused validators for the keep-list when available. If validators fail because the WIP is incomplete, you may still create a non-delivery WIP commit, but the report must say validators are not all passing and ATM-Delivery: false.

4. Author / committer continuity

Set Git identity from the explicit actor identity before commit:

# Values come from the actor identity for this emergency (not ambient editor).
export GIT_AUTHOR_NAME="<actor-git-name>"
export GIT_AUTHOR_EMAIL="<actor-git-email>"
export GIT_COMMITTER_NAME="<actor-git-name>"
export GIT_COMMITTER_EMAIL="<actor-git-email>"

Author continuity requires GIT_AUTHOR_* and GIT_COMMITTER_* to match the authorized actor for this emergency lane.

5. Native commit command shape (emergency only)

Use --no-verify only when the owner/captain explicitly authorized hook bypass for this emergency. Include required trailers:

• ATM-Actor: <actor-id>
• ATM-Task: <task-id>
• ATM-WIP: true|false
• ATM-Delivery: false for emergency park / non-delivery WIP
• ATM-Emergency-Reason: <short reason, include ATM_* code when present>

Example shape (paths already staged and verified):

git commit --no-verify \
  -m "wip(<task-id>): preserve emergency keep-list work" \
  -m "Emergency non-delivery pathspec commit. Not governed ATM delivery." \
  -m "ATM-Actor: <actor-id>" \
  -m "ATM-Task: <task-id>" \
  -m "ATM-WIP: true" \
  -m "ATM-Delivery: false" \
  -m "ATM-Emergency-Reason: <reason>"

6. Post-commit verification

After commit:

1. Confirm HEAD advanced.
2. Confirm git diff --cached --name-only is empty for this keep-list.
3. Re-check node atm.mjs broker status --json.
4. Report remaining dirty files (must not silently absorb unrelated residue).

7. Push boundary

Push only when the owner/captain requested push and pre-push passes. Do not treat a successful emergency push as task close or Plan 3.1 delivery success.

Closeout and backlog rules

• Using this skill must create or reference a backlog/follow-up item when the emergency was required because ATM lacked a normal recovery route.
• Do not close the underlying task as normal delivery solely because this emergency commit landed. Close only after subsequent governed claim, validators, evidence, and taskflow close prove delivery.
• ATM-GOV-0261 (when present) owns the durable VCS-neutral commit-candidate product route. This skill remains temporary anomaly evidence until that product lane exists.

Stop conditions

Stop immediately when:

• staged set is not an exact keep-list match;
• authority or --no-verify was not granted;
• recovery would require forbidden restore / stash / clean / reset / checkout / git add -A without separate approval;
• broker-conflict-blocked appears and no ticket path is provided;
• the request is ordinary delivery disguised as emergency.

First command

node atm.mjs next --prompt "$ARGUMENTS" --json

Read playbook and blockers before choosing emergency pathspec commit.

Charter Invariants

• INV-ATM-001 ??No second registry (enforcement: gate, breaking change: yes) Rule: A host project must not create a second AtomicRegistry implementation outside of packages/core or introduce a parallel ID allocation, version tracking, or registry promotion path.
• INV-ATM-002 ??Lock before edit (enforcement: doctor, breaking change: no) Rule: No governed file mutation may occur without a valid ScopeLock recorded in .atm/locks/ for the current WorkItem. Agents must call atm lock before editing files.
• INV-ATM-003 ??Schema-validated promotion only (enforcement: gate, breaking change: yes) Rule: An UpgradeProposal must pass all automatedGates (including JSON Schema validation) before promotion. Direct registry mutation that bypasses the UpgradeProposal path is forbidden.
• INV-ATM-004 ??No competing highest authority (enforcement: doctor, breaking change: yes) Rule: No host project rule, profile, or configuration may declare itself to have authority equal to or higher than the AtomicCharter. Any rule that contradicts an invariant must go through a charter waiver proposal.
• INV-ATM-005 ??Host rule amendments require waiver flow (enforcement: waiver-required, breaking change: no) Rule: When a host project rule conflicts with a charter invariant, the host must submit a behavior.evolve UpgradeProposal with a charterWaiver field and a linked HumanReviewDecision. Silent override is not permitted.
• INV-ATM-006 ??Framework work tracking stays target-local (enforcement: doctor, breaking change: yes) Rule: The framework repository must not host downstream adopter planning queues or project-specific work tracking artifacts. ATM framework-development tasks may live in the framework repository only as ATM-managed .atm/history/tasks ledger records with CLI transition evidence.
• INV-ATM-007 ??Public framework docs remain English-only (enforcement: doctor, breaking change: yes) Rule: Public contributor-facing documentation in the framework repository must remain English-only and repository-neutral. Non-English planning notes, local experiments, or downstream operating guidance must live in the coordinating host workspace unless they are translated into neutral English framework documentation.
• INV-ATM-008 ??Broker tickets, not refusals (enforcement: doctor, breaking change: no) Rule: Every governed shared-write gate (runner-sync, build windows, release mirrors, git commit, projection regeneration) must respond with a broker ticket - execute now, enqueue with position, or batch into a shared write window - never a bare refusal. Reads and private writes (own ledger, evidence, task events, lane sessions) never queue. The only standing exceptions are the four owner-ruled cases in docs/governance/parallel-governance-charter.md; any new serialization point requires an explicit project-owner ruling before it ships.
• INV-ATM-009 ??Generalized repair and data-driven policy (enforcement: doctor, breaking change: no) Rule: Any code logic change, bug fix, or governance rule change must first be designed as the most general rule that correctly explains the observed failure class. Hard-coded special cases are allowed only with recorded evidence that the general rule is not currently safe, feasible, or economical, and that the exception is bounded and reversible. Data-shaped behavior, including thresholds, mappings, allowlists, routing choices, telemetry classifications, prompts, message text, fixtures, and domain content, must first be modeled outside control flow through schemas, registries, configuration, observed counters, or compact digest evidence instead of embedded changeable numbers or strings. The generalized solution must remain observable, testable, and no broader than the evidence supports.
• INV-ATM-010 ??Single canonical worktree and compose-first shared writes (enforcement: doctor, breaking change: no) Rule: Normal governed parallel development uses one canonical worktree, base, and HEAD. A shared physical file is compose-eligible rather than a file lock: workers declare bounded atom/CID/content-anchor/source-range intents and submit proposals, while the broker, format adapter, and transactional composer decide compose, revalidation, escalation, or queue. A neutral steward is the only shared-file writer and shared delivery records member attribution. Queueing or revalidation is a fallback for a true logical conflict, stale base/CAS failure, unsupported adapter, or fairness bound. AI workers must not use Git branches, detached worktrees, alternate indexes, merges, or rebases as normal concurrency/isolation mechanisms. The closed exceptions are emergency/anomaly recovery, historical read-only discrimination, and non-development sealed packaging; each requires a named receipt and cannot perform normal governed contribution writes.