Skip to main content

n3Plugins Live Client Boundary

This document defines what you can and cannot prove without a running RuneLite/game environment.

1. Static Development Capability​

A normal repository checkout can support:

source inspection
editing
compilation
unit tests
integration tests
packaging
SDK analysis
state-machine analysis
reference-resource inspection
static packet/revision analysis

These are valid forms of engineering validation.

2. Live Validation Capability​

Actual live validation requires a functioning path to:

RuneLite
OSRS client state
n3Plugins runtime
relevant account/game state

Potential live interfaces include:

local RuneLite development environment
n3 Agent Server
authenticated remote MCP/API bridge
other explicitly supported runtime tooling

Do not infer availability.

3. Localhost Boundary​

127.0.0.1 always means the machine where the process is running.

Therefore:

Cloud workspace 127.0.0.1

does not refer to:

user's Windows 127.0.0.1

A local n3 Agent Server cannot be accessed from cloud merely because both systems use the same port number.

4. n3 Agent Server​

The existing Agent Server/runtime bridge may expose state and controlled actions.

Engineer any remote cloud connection.

Required protections for a remote action-capable endpoint include:

authentication
TLS
authorization
network restrictions
rate limiting
action pacing
runtime readiness gates
audit logging
explicit enablement

Never expose an unrestricted action endpoint publicly.

Runtime Read​

May expose diagnostics such as:

client state
widgets
inventory
NPCs
objects
ground items
skills
bank state
plugins
menu entries
recent interactions
varbits/varplayers

Runtime Action​

Higher-risk operations such as:

clicking widgets
inventory interaction
NPC/object interaction
walking
banking
dialogue actions
plugin control
item-on-target interactions

must remain separately controlled.

6. Validation Language​

Without a real client/runtime path, use:

Live client verification: pending

Do not claim:

verified in RuneLite
verified against live revision
confirmed widget interaction
confirmed packet behavior
confirmed navigation

unless you observed that behavior.

7. Cloud Work Should Still Continue​

Treat live verification as a separate validation stage rather than abandoning otherwise valid engineering work.

8. Offline Scenario Simulation for Cloud Agents​

While live client verification remains pending, cloud agents should use the project's event snapshot and scenario testing infrastructure to validate state machines and workflow logic offline:

com.n3plugins.sdk.events.fixture.*
com.n3plugins.sdk.events.scenario.*

Cloud agents can:

  • construct deterministic event envelopes and state snapshots,
  • test state-machine transition outputs without a running GUI client,
  • assert expected InteractionResult responses against simulated game tick streams,
  • verify clean transient state reset on logout/hop events.

This allows robust behavioral validation in isolated cloud environments while explicitly tracking:

Live client verification: pending

9. Agentic Live Validation​

When available, n3Plugins supports a headless Agentic Test Loop (./scripts/agent-test-loop.sh). This enables live client verification in Cloud or Local environments by bootstrapping the client through TestRunnerPlugin and the surviving n3 Profiles store, wrapping feature scripts inside a Test Runner, and leveraging an autonomous AI CLI to read serialized TestResult feedback and automatically heal failures.

This is the ONLY approved way for cloud agents to execute live gameplay validation. Profiles used for this loop must contain the string TEST in their name.

See docs/agent/AGENTIC_TESTING_LOOP.md for full implementation details.