@http-forge/core 0.4.7 → 0.4.8

package/README.md

@@ -252,6 +252,35 @@ if (pm.response.headers.has('Set-Cookie')) {
 }
 ```
 
+#### Response Body Type
+
+Like Postman, `pm.response.body` is the **raw response string** — it is not eagerly parsed. Parse JSON on demand:
+
+```javascript
+const data = pm.response.json();          // parsed object (null if not JSON)
+const text = pm.response.text();          // raw string
+const obj  = JSON.parse(pm.response.body); // body is a string
+```
+
+`json()` tolerates an already-parsed object body for backward compatibility, but new code should treat `pm.response.body` as a string.
+
+#### Legacy Postman Globals
+
+Older Postman scripts and many Newman-exported collections rely on bare globals from the pre-`pm.*` sandbox. The core injects these so legacy scripts run unchanged.
+
+Available in **both** pre-request and test scripts: `request` (`{ id, name, description, url, method, headers, data }`), `environment` (read snapshot), `globals` (read snapshot), `data` (iteration row), `iteration` (index), and `tv4` (`tv4.validate(data, schema)` — when the optional `tv4` module is installed).
+
+Available in **test** scripts only: `responseBody` (raw string), `responseCode` (`{ code, name, detail }`), `responseHeaders`, `responseTime`, `responseCookies` (`[{ name, value }]`), `tests` (`tests['name'] = boolean`), plus `postman.getResponseHeader(name)` and `postman.getResponseCookie(name)` (case-insensitive, return `null` if absent).
+
+```javascript
+// Legacy-style test script — runs unmodified
+tests['status 200'] = responseCode.code === 200;
+tests['has token'] = JSON.parse(responseBody).token !== undefined;
+tests['is json'] = /application\/json/.test(postman.getResponseHeader('Content-Type'));
+```
+
+> `environment` and `globals` are read snapshots — direct assignment was never persisted in legacy Postman either. Use `postman.setEnvironmentVariable()` / `postman.setGlobalVariable()` (or the modern `pm.environment.set()` / `pm.globals.set()`) to persist changes.
+
 #### Script Scope
 
 Control how script levels (collection → folder → request) and the pre-request/post-response phases share a JavaScript scope via `scripts.scope` in `http-forge.config.json` (or the `scriptScope` SDK option):

package/dist/index.d.ts

@@ -20,6 +20,9 @@ export { ForgeContainer } from './container';
 export type { ForgeContainerOptions, StorageFormat } from './container';
 export { getServiceContainer, registerCoreServices, ServiceContainer, ServiceIdentifiers } from './di';
 export type { PlatformAdapters, ServiceIdentifier } from './di';
+export { buildCollectionToolDescription, buildCollectionToolName, buildFolderToolDescription, buildFolderToolName, buildRequestToolDescription, buildRequestToolName, buildSuiteToolDescription, buildSuiteToolName, mcpToolToken, parseMcpToolName, resolveFolderToken, resolveToken } from './runtime/mcp-tool-name';
+export type { McpToolKind, ParsedMcpToolName } from './runtime/mcp-tool-name';
+export { COLLECTION_INPUT_SCHEMA, FOLDER_INPUT_SCHEMA, REQUEST_INPUT_SCHEMA, SUITE_INPUT_SCHEMA } from './runtime/mcp-tool-schemas';
 export { createMcpRuntime, runCollection, runFolder, runRequest, runSuite } from './runtime/runtime-contracts';
 export type { McpRuntimeHandle, McpRuntimeOptions, RunCollectionOptions, RunRequestOptions, RunSuiteOptions } from './runtime/runtime-contracts';
 export { bootstrapNodeRuntime, createNodeContainer } from './runtime/node-bootstrap';