docs: correct three unverified capability claims

[sundargthb]

Docs only. Three claims in the README described behaviour the node does not have. Found while doing a pre-release check of the docs going out with the launch, and they are the same class of error as the AI Agent comparison corrected in #77.

1. "Session length: up to 8 hours"

The 28800-second figure appears twice in the SDK types, and neither is a harness session:

• LifecycleConfiguration.maxLifetime — default 28800s, but that is the AgentCore Runtime instance lifetime, not a harness session
• SessionConfiguration.sessionTimeoutInSeconds — max 28800s, but that is MCP Gateway session config

The node never sends either field (grep -rn "maxLifetime\|idleRuntimeSessionTimeout" nodes/ credentials/ returns nothing). The only duration it sends is the per-invocation timeoutSeconds, default 600, described in the UI as "wall-clock timeout for the entire invocation". So no user could reach eight hours through this node.

Now reads: Long-running sessions, with a per-invocation timeout you set

2. "Streaming responses" listed as a shipped feature

consumeStream() reads the event stream and accumulates — the doc comment at the top of helpers/stream.ts says so. grep -rn "sendChunk\|isStreaming" nodes/ returns nothing, so nothing reaches n8n's streaming UI. The node consumes a streaming API; it does not stream.

This matters because an n8n user reading the feature list would reasonably expect token-by-token output in the chat panel. An FSI SA asked about exactly this and offered to file a feature request.

Renamed to Structured responses, with the distinction stated explicitly, and streaming moved from the v0.1 roadmap row to later.

3. "Firecracker microVM per session"

AWS public documentation for AgentCore says "isolated microVM" and "session isolation" without naming the hypervisor. The only source for Firecracker in this repo is our own docs/SPEC.md, so the claim was circular. The comparison table and docs/SPEC.md (prose plus the ASCII diagram) now say "isolated microVM", matching the AgentCore docs.

Why now

npm currently serves the pre-#77 README, so the next release is what puts the corrected text on the npm page. That release lines up with the n8n partner blog and the AWS channel post, so this is the last chance to get the docs right before traffic arrives.

Checks run locally

typecheck, lint, format:check, test (114 passing / 12 files), secrets:check — all pass. No code touched, so no behaviour change and no node typeVersion bump.

[notgitika]

LGTM
Let's explore changelog changes being auto generated instead of manual code changes