Shelved PR 370 arty cache objective

Shelved: PR #370 — Arty Cache capturable static-gun side-objective

State: Ray-shelved 2026-07-03 (Build 89 pick round). PR #370 was closed without merging; nothing from it is in Build 88/89.

WHAT

Adds a default-off "arty cache" event on Chernarus: a neutral static gun (D30_CDF) sits at a fixed mid-map spot with a yellow objective marker. The first side to clear and hold an 80m zone around it captures the cache and earns a one-time 1500-supply bonus (later re-captures pay nothing). The marker recolors on each flip and captures are announced to all players. An optional sub-flag lets the gun physically change hands with spawned AI crew on later re-captures.

WHERE

• PR: #370 — "feat(t34): Arty Cache - capturable neutral static-gun side-objective (Chernarus)".
• Branch / head commit: fable/arty-cache-objective @ a6301c9f9ed6b114a53d8be3c8a5c681cd03fa08.
• Flag (if any): WFBE_C_ARTY_CACHE = 0 (master gate, default OFF; also worldName-gated to Chernarus only). Tunables: WFBE_C_ARTY_CACHE_CLASS = "D30_CDF", WFBE_C_ARTY_CACHE_POS = [7300,7900,0], WFBE_C_ARTY_CACHE_RADIUS = 80, WFBE_C_ARTY_CACHE_SCAN_INTERVAL = 15, WFBE_C_ARTY_CACHE_BONUS = 1500, WFBE_C_ARTY_CACHE_GUN_TRANSFER = 0, WFBE_C_ARTY_CACHE_CREW_CLASS = "RU_Soldier".
• Files touched: new Server/Server_ArtyCache.sqf (209 lines); Server/Init/Init_Server.sqf (flag-gated execVM launch after the Oilfields block); Common/Init/Init_CommonConstants.sqf (8 constants). Mirrored Chernarus + Takistan.

WHY SHELVED

Ray was offered a choice between two "capturable neutral relic/gun side-objective" designs — the T-34 relic (#388) and this Arty Cache static-gun (#370) — and on 2026-07-03 picked "C, neither". Both sibling PRs are shelved together; neither is going into Build 88/89. The feature was default-off and CH-gated, so nothing was live.

Code-quality caveat (must fix if revived): this PR reportedly carries an NSSETVAR3 lint finding — a 3-argument setVariable (the [name, value, broadcast] global-broadcast form) that should be reviewed for correctness/intent before any revival. Do not re-land without resolving that lint. Note also that the sibling #388 covers the same "capturable neutral relic/gun side-objective" design space, so at most one of the two should ever ship.

HOW TO REVIVE

• Recover from branch fable/arty-cache-objective @ a6301c9f9ed6b114a53d8be3c8a5c681cd03fa08; the whole feature is gated behind WFBE_C_ARTY_CACHE (and Chernarus-only), so it can be reintroduced default-off.
• Resolve the NSSETVAR3 lint first — audit the 3-arg setVariable broadcast call flagged by the linter before re-landing.
• Decide the design question: Ray declined the entire "neutral capturable relic/gun" niche this round (both #370 and #388) — a revival needs a fresh design pitch, and should pick only ONE of the two siblings.
• Validate in-engine: the spawn position [7300,7900,0] is a rough guess the PR author flagged for author validation; confirm the supply-credit path (WFBE_SE_FNC_HandleSideSupplyChange) actually pays, and if GUN_TRANSFER is used, watch the AI-crew/group-budget cost.