feat(mosstank): add VTank-style automation PoC

docs/architecture/acdream-architecture.md

@@ -137,6 +137,68 @@ loads none). The headless adapter projects entity snapshots on demand from the
 canonical Runtime view, subscribes to Runtime's ordered events, and borrows the
 exact Runtime selection owner; it does not mirror gameplay state.
 
+Graphical plugin panels are first-class retained windows. A plugin calls
+`IUiRegistry.AddPanel` with a BCL-only `PluginPanelDescriptor`; Core's scoped
+host authenticates the owner from the loaded manifest, and App derives the
+stable identity `plugin:{pluginId}:{windowId}`. The host, not the plugin, owns
+window geometry, z-order, persisted visibility, minimize/restore chrome, and
+the shared right-edge plugin shelf. Minimizing only hides the presentation:
+the plugin session, event subscriptions, automation policy, and binding object
+remain live. Legacy `AddMarkupPanel` registrations are enriched into the same
+first-class path, so API-v1 plugins keep working without a second lifecycle.
+The markup vocabulary includes nested groups plus retained tab, toggle,
+slider, editable-field, and retail-menu controls. Fields bind live
+`Action<string>` change/submit callbacks and menus bind an
+`IEnumerable<string>` plus selection callback, so plugin-owned profile/rule
+editors stay behind the BCL contract instead of importing App widgets. These
+are presentation bindings only and never become parallel gameplay owners.
+
+Durable plugin data uses the BCL-only `IPluginHost.Storage` contract. Core's
+manifest-authenticated scoped host prefixes every logical key with the loaded
+plugin id; graphical composition writes atomically beneath the per-user config
+root (`plugins/{pluginId}/...`). Plugins receive neither another plugin's
+namespace nor a machine-specific path. Hosts without durable storage expose
+`NoOpPluginStorage` and report the capability unavailable.
+The additive `List(prefix)` operation enumerates only keys inside that same
+authenticated namespace, allowing plugins to discover explicit import/export
+files without receiving a filesystem path or crossing plugin ownership.
+
+`IPluginHost.Automation` is the additive gameplay-automation projection. Its
+character, spell, magic, chat, combat, equipment, item, loot, fellowship,
+enchantment-observation, and navigation
+groups contain BCL-only immutable snapshots plus attempt-style commands; the
+graphical implementation borrows the exact `GameRuntime`
+character/action/entity/object/vendor/fellowship owners. Item projections also
+carry Virindi's stable ObjectClass plus ordered ObjDesc subpalette samples;
+the graphical host resolves each representative RGB directly from portal DAT
+using VTank's sample-index formula. MossTank owns all
+macro policy (buff planning, target rules, selection scoring, corpse policy,
+loot-rule ordering and action timing). In particular, `ICombatAutomation`
+does not create a plugin combat model: each hostile capture is a detached
+point-in-time projection of `RuntimeHostileTargetQuery`, and physical commands
+enter the canonical `RuntimeCombatModeState` / `RuntimeCombatAttackState`
+press-charge-release state machine. Item and loot commands similarly enter
+App's one `ItemInteractionController`: appraisal, use/apply, pickup,
+move/split/merge/drop/give, retail 0x027D salvage, and current-vendor sale
+reuse the same readiness checks, reservations, wire sends, and authoritative
+completion/object-table signals as retained retail UI. Plugins never hold an
+optimistic inventory or vendor shadow. Navigation similarly projects live and
+server-accepted position, portal/object state, and semantic movement levels;
+the App host applies those levels through Runtime's one command interpreter.
+Route sequencing, steering cones, follow breadcrumbs, checkpoint policy,
+door/lockpick decisions and portal retry behavior remain plugin-owned. The
+shared enchantment-observation group is deliberately a confirmed-cast timer
+ledger rather than another authoritative spellbook: the host records successful
+local duration casts and cooperating plugins can report their own confirmed
+casts, matching VTank's `LogSpellCast` contract. It resets at session detach;
+dispel/debuff policy remains plugin-owned. The
+inert default remains
+`NoOpAutomationSurface`, preserving one plugin code path on hosts without a
+live gameplay session.
+`ICharacterInfo.Name` projects the canonical local `ClientObject.Name` (empty
+when unavailable) solely for per-character plugin profile scoping; it does not
+introduce a second identity owner.
+
 Core `SelectionState` is the sole selected-object owner for world,
 radar, inventory, paperdoll, toolbar, use/examine consumers, and plugins;
 `IPluginHost.Selection` exposes that same state and retail-style old/new callback.
@@ -420,6 +482,10 @@ src/
     IGameState.cs             -> done
     IEvents.cs                -> done
     ISelectionService.cs      -> done
+    IPluginStorage.cs         -> manifest-scoped durable text profiles
+    Automation.cs             -> character/spell/magic/chat automation groups
+    CombatAutomation.cs       -> hostile snapshots + retail combat attempts
+    EnchantmentAutomation.cs  -> shared confirmed duration-cast timer ledger
   
   AcDream.App/               Layer 1 + Layer 4 wiring
     Platform/