feat: career-mode handler surface (tech / kc / sci / contracts / launch / actiongroups)

[jonpepler]

⚠️ I've used Claude to make these changes and draft most of the description below. Built, tested locally in KSP, and happy with the result, so sharing here.

Summary

Six new handlers + ~50 data keys covering more of the career-mode UI surface - useful for external dashboards that want to mirror or drive R&D, KSC, science, contracts, and launch/recovery from outside Flight. All new keys are AlwaysEvaluable = true so they're queryable from Space Center / Editor / Tracking Station.

Builds on #84 (now merged) for the AlwaysEvaluable attribute to take effect on the new action keys.

The branch has grown since the first review - a Strategies / Administration Building handler and a CurrencyModifierQuery-aware effective-cost layer have been added on top of the original six handlers. See "Updates since first review" below.

New handlers

Handler	Sample keys
TechTreeDataLinkHandler	tech.nodes, tech.unlock[id], tech.unlockedIds, tech.unlockedPartCount, tech.affordable
KscDataLinkHandler	kc.facilityLevels, kc.upgradeFacility[name], kc.crewRoster, kc.scene, kc.savedShips, kc.partsAvailable
ScienceInstrumentsDataLinkHandler	sci.instruments, sci.experimentBreakdown, sci.experiments, sci.canRecoverTotal, sci.canTransmitTotal, sci.deploy[partFlightId, experimentId], sci.transmit[partFlightId]
ContractsDataLinkHandler	contracts.active, contracts.offered, contracts.completedRecent, contracts.accept[id], contracts.decline[id], contracts.cancel[id]
LaunchDataLinkHandler	ksp.launch[ship, facility, site, crew], ksp.recover, ksp.revertToLaunch, ksp.revertToEditor[vab|sph], ksp.toSpaceCenter, ksp.toTrackingStation, ksp.canRevert*
ActionGroupBindingsDataLinkHandler	f.ag.bindings (which parts/modules/actions are bound to each AG)
StrategiesDataLinkHandler	strategies.all, strategies.activate[id, factor], strategies.deactivate[id]

Design notes

Contracts long ids as strings. Contract IDs frequently exceed 2^53 and silently lose precision when serialised as JSON numbers. contracts.* rows emit "id": "<digits>" and the action handlers accept both string and number forms for back-compat. Contract parameter rows include the parameter's runtime type plus typed fields (parameterType / minAltitude / maxAltitude / body / situation / partName) so consumers can render real progress bars without name-string heuristics.

Action handlers fire from any scene. ksp.launch refuses outside SC/Editor; ksp.revertToLaunch refuses outside Flight; tech.unlock refuses unaffordably-priced nodes; etc. - internal state checks, not blanket scene gates.

ksp.launch always builds a VesselCrewManifest even for unmanned launches. Passing null NREs inside setStartupNewVessel and leaves Flight half-initialised (frozen HUD, sentinel values).

Recovery / crash / flight-log keys are NOT in this PR - they're separately submitted as event-driven snapshot handlers in #85.

Updates since first review

Two follow-on areas have been added in the same career-mode surface. Both ride this branch.

Tech-tree enrichment

tech.nodes rows now include:

• description - parsed from the tech tree's underlying RDNode config and run through Localizer.Format so it matches what KSP shows in the R&D dialog.
• parts - one entry per AvailablePart assigned to the node, with name / title / manufacturer / category / entryCost / purchased. Built once per game-load by indexing PartLoader.LoadedPartsList by TechRequired.

kc.facilityLevels rows now include currentLevelText and nextLevelText (from UpgradeableFacility.GetLevelText(int)) so consumers can show KSP's multi-line upgrade dialog text without mirroring it locally.

Strategies / Administration Building

A new StrategiesDataLinkHandler adds three keys: strategies.all, strategies.activate[id, factor], strategies.deactivate[id]. The interesting bit is that all three work from any scene.

KSP's Strategy.CanBeActivated / Activate / Deactivate dereference Administration.Instance, a MonoBehaviour that's only alive while the Admin Building dialog is open. That makes the stock methods unusable from a remote dashboard when the player isn't in front of the dialog. The handler replicates each check and mutation against publicly-accessible state (StrategySystem, GameVariables, ScenarioUpgradeableFacilities, Funding, Reputation, ResearchAndDevelopment, Planetarium) so the same operations work from Space Center, Editor, Flight, or Tracking Station. Reflection is used only to write Strategy.isActive and Strategy.dateActivated; everything else is a public API call. Behaviour matches stock KSP 1.12.

The replica section is cleanly fenced inside the handler with header/footer comments so the boundary against stock behaviour is obvious to anyone reading the file.

Currency-modifier effective costs

KSP's {Funding, ResearchAndDevelopment, Reputation}.Add* methods apply the mutation before firing GameEvents.Modifiers.OnCurrencyModifierQuery, so consumers can't adjust the deduction by listening - they have to pre-query the modifier separately. Without that step, dashboards showing the nominal cost of a launch / facility upgrade / tech purchase will be wrong whenever a strategy is active (e.g. Aggressive Negotiations advertises -1.5% on launches and R&D purchases, and -0.05% on facility construction).

A new CurrencyModifiers helper wraps the pre-query in a one-liner. Existing rows now include a sidecar field next to each cost:

Existing field	New sidecar	Transaction reason
kc.facilityLevels.upgradeFunds	upgradeFundsEffective	StructureConstruction
kc.savedShips.requiresFunds	requiresFundsEffective	VesselRollout
tech.nodes.scienceCost	scienceCostEffective	RnDTechResearch
tech.nodes.parts[].entryCost	entryCostEffective	RnDPartPurchase

strategies.all also includes effectiveCostReputation per strategy, which mirrors Reputation.addReputation_granular's per-unit walk against GameVariables.reputationSubtraction. The rep curve makes losses near the cap cost meaningfully more than at zero - a 14.5-nominal cost can deduct ~27 at 976 rep, so the nominal figure on its own is misleading.

Validation

Tested locally on KSP 1.12.x with a custom HTTP/WS dashboard, in a career save:

• Tech tree: tech.nodes listed every node + its unlocked state from the Space Center; tech.unlock[experimentalRocketry] deducted science and unlocked the node in the R&D UI on the next tick. Per-node description and parts matched the in-game R&D dialog content.
• KSC: kc.facilityLevels returned the expected building list with current/max upgrade levels and currentLevelText / nextLevelText matching the in-game upgrade dialog; kc.upgradeFacility[LaunchPad] deducted funds and started the upgrade animation. kc.crewRoster exposed the full kerbal roster including experience and current assignment fields.
• Contracts: contracts.active rows included parameterType plus the typed fields for the well-known parameter classes (altitude, body, situation, part). Long contract IDs round-tripped correctly as strings.
• Launch: ksp.launch[Stayputnik X, VAB, LaunchPad, Jeb;Bill] launched the saved craft with the named crew aboard. Refuses outside SC/Editor as designed.
• Scene-transition battery: ran the full sequence Flight → Space Center → Tracking Station → (refused-launch from TS) → Space Center → launch → recover → Tracking Station. All six ksp.* scene actions worked correctly.
• Action groups: f.ag.bindings returned one row per (action, group) pair on a vessel with multiple custom bindings.
• Strategies: strategies.all returned from the Space Center without the Admin dialog being open; the currently-active strategy showed isActive: true / canDeactivate: true and every other strategy was blocked by the stock 1-active-limit gate with the localised human-readable reason. Round-tripped deactivate + activate end-to-end (Aggressive Negotiations → off, Fundraising Campaign → on at factor 0.05); change was reflected immediately in both strategies.all and the in-game Admin Building dialog. Per-strategy effectiveCostReputation matched the post-curve deduction observed on real activation to within ~1 unit.
• Currency-modifiers: tested with multiple strategies and confirmed their modifiers are correctly applied into values marked effective.
• No regression in any existing Flight-scene key while these were queried.