Slice: Execute dot-repeat as a Jim.edict semantic intent

[flyingrobots]

Slice

Make dot-repeat execute a Jim-owned typed semantic intent against the current
admitted basis. The authoritative repeat program and re-resolution policy live
in Jim.edict, not TypeScript and not stored raw keys.

This is downstream product work. Do not schedule it ahead of #295 or the
Jim.edict active-observer cutover.

Target model

Jim.edict retains the parsed operation, target resolver, count/register
policy, bounded inserted material, source basis, and current-basis resolution
policy. Raw keys remain provenance/display evidence. On repeat, Jim.edict
requests the required bounded reading, resolves the target at the current basis,
derives the operation intent, handles the outcome, and advances Jim state.

Acceptance criteria

• Define a closed Edict representation for repeatable semantic intents.
• Record it only after the original command reaches its admitted terminal
  posture.
• Retain raw keys for provenance without using them as the executable
  program.
• Resolve the semantic target from a basis-bound reading inside Jim law.
• Invoke the Jim-owned child operation through the active-observer corridor.
• Preserve operator, motion/text-object, count, register, shape, and bounded
  inserted-material semantics.
• Return a typed obstruction when re-resolution is unlawful or required
  evidence is unavailable.
• Never fall back to stale offsets, raw-key execution, TypeScript semantic
  replay, local mutation, or compatibility-host execution.
• Evidence links the repeat to its source intent and newly admitted outcome.
• Restart reconstructs repeatability only from retained authoritative
  evidence.

Dependencies

• Goalpost: Run Jim.edict as an Echo-realized active observer #295 and especially Slice: Retire frontend operation orchestration and the compatibility host #298.
• WF-0118: Semantic Dot-Repeat Explanation #136 is the explanation consumer.
• Slice: Add Jim.edict semantic macro scripts and replay reports #187 owns macro sequencing.

[coderabbitai]

🔗 Related PRs

#120 - Feat: add Vim normal state machine [closed]
#122 - Add Vim power move execution [closed]
#124 - Feat: extend Vim power moves [closed]
#272 - WF-0154 - E-Brake closeout: provenance naming, guard witnesses, next-cycle designs [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!