feat(encounters): author cross-stack bat, orc, and offering-site pilots

[zoeyrose]

Architecture amendment — one authored content source (2026-08-13)

Initiative atrinik/atrinik#357 supersedes every future live-branch instruction below. atrinik/content@main is the sole mutable authored content source. Future authored changes belong only on main; supported Classic artifacts must be derived from the same immutable main revision. Do not create, restore, author, backport, validate, publish, select, profile, or channel content through a live 1.x branch or content-1x checkout.

Exact historical commits, release tags, artifacts, checksums, and archived comparisons remain valid evidence. This amendment does not alter the issue's other feature, implementation, validation, licensing, or acceptance requirements.

Camp-site pilot amendment (2026-08-23)

The pilot must include the camp-preservation contract in content#241 —
preserve camp-spot identity during dynamic spawn migration,
either through a representative preserved camp fixture or a deterministic
camp-site conformance fixture alongside the bat/orc areas:

• the old physical footprint remains recognizable while named definitions are
  centralized;
• an appropriate named rare/elite affinity is higher at the preserved site
  but remains global-cap, cooldown, reservation, persistence, and placement
  bounded; and
• a story/key-holder/static named actor is excluded and retains exact reward
  and progression behavior.

Pilot reports must include named sighting frequency, cap contention, local
composition, and blocked/full/restart outcomes in addition to ordinary threat
and population metrics.

Outcome

Author and tune a small cross-stack vertical slice that proves dynamic areas,
role-composed packs, centralized pacing, and a themed offering-site encounter
before broader migration.

Use separately reviewed/delivered main and 1.x changes. Shared product
semantics and IDs should align where compatible, while each line keeps its own
supported source/runtime representation and generated output.

Pilot content

• One bat area proves a single-family swarm with bounded density and refill
  pacing.
• One orc area proves frontline, ranged, caster/support, and leader roles
  selected under entity and threat budgets. Prefer an area compatible with the
  replacement M3 map chain and a Classic area that also exercises tiled-map
  lifecycle; exact maps are chosen and recorded before authoring.
• Fixed ordinary placements inside each selected area are removed or disabled,
  while quest, scripted, named, connected, static, and schedule-special
  exceptions remain explicit.
• The orc hunt includes one themed offering site with left, center, and right
  slots. A centerpiece trophy comes from an elite/leader and matching flank
  components come from ordinary local monsters. The accepted arrangement
  requests one telegraphed bounded encounter directive and has documented
  cooldown, attribution, drop, and reward economics.
• The offering outcome must be mechanically legible and locally meaningful;
  it cannot be only a hidden stat multiplier or an arbitrary unrelated recipe.

Acceptance criteria

• Both pilots use stable family/roster/profile/policy/zone IDs and contain
  no exact ordinary live count or fixed ordinary spawn coordinate beyond
  documented exceptions.
• The bat area and orc area compile/collect through the owning line's tools
  and run through the applicable Classic/replacement consumer fixtures.
• The orc pack maintains documented role and threat bounds rather than
  independent random monster picks.
• Low/normal/high difficulty and one/two/four-player deterministic reports
  record target/alive/reserved threat, entity and role distribution, refill
  latency, encounter downtime, and placement rejection reasons.
• No pack appears on occupied/blocked/protected/exit tiles or inside the
  configured player proximity/visibility envelope; a full area backs off
  without a partial pack or busy loop.
• Target reduction does not remove living monsters; unload/reload and
  restart do not reroll or accumulate an instant population burst.
• The three-slot offering consumes items only after the directive is
  accepted. Invalid layouts, two simultaneous activations, full population,
  active cap, cooldown, disconnect, unload, blocked placement, and restart
  cannot lose/duplicate items or encounters.
• The offered encounter is visibly telegraphed, finite, party-attributed,
  and pays ordinary plus special rewards exactly once under documented
  eligibility rules.
• Existing loot, XP, aggression, faction, leash/return, quest credit, map
  reset, and named-variant behavior remain correct.
• Main and 1.x PRs follow the repository's paired-release-line rules,
  identify their canonical closing path, and share no generated trees.

Dependencies

Depends on the parent authored contract, the applicable Classic and Go runtime
children, the toolkit compiled contract for replacement, and
server#55 for the replacement
M3 slice. Reuse #22 role rosters
and #23 rare-variant profiles;
do not duplicate them.