relmio 0.2.15 → 0.3.1

package/CHANGELOG.md

@@ -7,6 +7,49 @@ checks the registry separately after publication.
 
 ## Unreleased
 
+## [0.3.1] - 2026-08-10
+
+### Changed
+
+- Make the browser wizard beginner-friendly with a modern fixed-viewport
+  layout: all five active steps fit without document scrolling on common
+  1280x720 laptops, while progress and safety context stay persistent beside
+  the active task.
+- Keep narrow-phone documents fixed to the viewport and contain unavoidable
+  long-form overflow within the active task panel instead of the page.
+- Expand the GitHub and npm walkthroughs with a hosted-install selector and
+  packaged, sanitized screenshots that document the current n8n workflow.
+
+### Security
+
+- Restore a clean hosted-web dependency audit by pinning patched `js-yaml`
+  and `nanoid` releases and using the compatible `vinext` release that does
+  not include the currently vulnerable `image-size` parser.
+
+## [0.3.0] - 2026-08-05
+
+### Added
+
+- Add a copy-ready n8n HTTP Request recipe to the local wizard, including the
+  private Chat Completions URL, Generic Credential Type → Bearer Auth fields,
+  the harmless `local-only` bearer placeholder, JSON headers, the structured
+  response-format body, and a full recipe copy action.
+- Add the same structured `gpt-5.6-sol` example and importable cURL recipe to
+  the GitHub README, npm README, and n8n configuration guide.
+- Add a repository-local changelog skill that standardizes Relmio's patch,
+  pre-1.0 feature, and stable major release numbering and metadata checks.
+
+### Changed
+
+- Treat `0.3.0` as Relmio's major feature release within the pre-1.0 series;
+  it consolidates the key improvements shipped from v0.2.10 through v0.2.14:
+  resilient Windows OAuth/bootstrap flows, native Command Prompt installation,
+  compact accessible wizard recipes, verified Homebrew/package-manager
+  preparation, and release-time package checks.
+- Keep the HTTP Request body aligned with n8n's `messages` format by targeting
+  `/v1/chat/completions`; the separate OpenAI Chat Model guidance continues to
+  support the Responses API where that node exposes the switch.
+
 ## [0.2.15] - 2026-08-05
 
 ### Fixed

package/README.md

@@ -15,21 +15,29 @@
 
 ## See it working first
 
-Before setup, this sample n8n configuration shows GPT-5.6 model aliases in the
-OpenAI Chat Model selector. The exact model list depends on the signed-in
-ChatGPT account and can change over time.
+This documented example follows a tested n8n OpenAI credential through a
+published Telegram-triggered workflow. It is a product-operation record, not
+an endorsement, sponsorship, or affiliation by OpenAI, n8n, Hostinger,
+Telegram, or AppBuildersPH.
 
 <figure>
-  <img src="https://cdn.jsdelivr.net/npm/relmio@latest/docs/images/examples/gpt-56-model-selector.png" alt="Model selector listing GPT-5.6 Sol, Luna, and Terra model aliases" width="480">
-  <figcaption>Compatibility preview: the model selector includes <code>gpt-5.6-sol</code>, <code>gpt-5.6-luna</code>, and <code>gpt-5.6-terra</code>.</figcaption>
+  <img src="https://cdn.jsdelivr.net/npm/relmio@latest/docs/images/examples/n8n-openai-credential-connected.png" alt="n8n OpenAI credential dialog showing that the connection test succeeded" width="960">
+  <figcaption>The n8n OpenAI credential connection test succeeded; the credential value itself is obscured.</figcaption>
 </figure>
 
-After Relmio completes the installation, Docker shows the existing n8n stack
-and the new private OAuth sidecar running together.
+<figure>
+  <img src="https://cdn.jsdelivr.net/npm/relmio@latest/docs/images/examples/gpt-56-model-selector.png" alt="n8n model selector with gpt-5.6-terra selected and an account-specific model list" width="500">
+  <figcaption>This signed-in account's n8n model list includes <code>gpt-5.6-terra</code>; model availability is account-dependent and can change.</figcaption>
+</figure>
+
+<figure>
+  <img src="https://cdn.jsdelivr.net/npm/relmio@latest/docs/images/examples/telegram-n8n-workflow-execution.png" alt="Successful n8n execution of a Telegram-triggered workflow with HTTP Request, Basic LLM Chain, and AI Agent branches" width="960">
+  <figcaption>The published Telegram-triggered n8n workflow completed successfully across its HTTP Request, Basic LLM Chain, and AI Agent branches.</figcaption>
+</figure>
 
 <figure>
-  <img src="https://cdn.jsdelivr.net/npm/relmio@latest/docs/images/examples/sidecar-docker-containers-running.png" alt="Docker Desktop showing the n8n and n8n-openai-oauth containers running" width="960">
-  <figcaption>Completed setup: the existing <code>n8n</code> stack and the <code>n8n-openai-oauth</code> sidecar are both running.</figcaption>
+  <img src="https://cdn.jsdelivr.net/npm/relmio@latest/docs/images/examples/telegram-model-results.png" alt="Telegram conversation receiving HTTP Request, Basic LLM Chain, and AI Agent outputs" width="682">
+  <figcaption>Telegram received the HTTP Request, Basic LLM Chain, and AI Agent outputs sent by that workflow.</figcaption>
 </figure>
 
 Relmio is a local browser wizard that installs a private
@@ -80,10 +88,11 @@ tailored to the current self-hosted n8n and Hostinger VPS setup path.
 The hosted site and local wizard keep the original Relmio relay layout while
 adding a compact **System / Light / Dark** appearance control. System follows
 the computer's preference; Light and Dark are remembered on that browser only.
-The local wizard keeps its horizontal five-step Signal Spine at the top of the
-flow, and the hosted site keeps the live GitHub star/version control visible.
-Both surfaces collapse their controls for narrow phone screens without
-turning the setup flow into a side rail or requiring a separate mobile app.
+On desktop, the local wizard keeps progress and sidecar-only safety notes in a
+persistent rail beside the active task; its compact fixed-screen shell avoids
+document scrolling on common laptop screens. On narrow phones, it switches to
+a horizontal progress strip and keeps task scrolling inside the active panel.
+The hosted site keeps the live GitHub star/version control visible.
 
 ## Quick start
 
@@ -184,28 +193,51 @@ it is not currently advertised as supported.
 
 ## Visual walkthrough
 
-All images below are sanitized previews with reserved addresses, fake server
-data, and no real credential or session information.
+These current product screenshots use sanitized sample values wherever a setup
+field might otherwise identify an environment. The VPS identity screen shows a
+reserved sample address and sample SSH fingerprint; none of the images includes
+an OAuth token, password, private key, or live wizard session URL.
+
+### 1. Choose a hosted installation method
+
+<img src="https://cdn.jsdelivr.net/npm/relmio@latest/docs/images/setup/00-install-methods.png" alt="Hosted Relmio installation page with macOS/Linux, Homebrew, PowerShell, Command Prompt, and NPX choices" width="720">
+
+The hosted page starts with the installation-method selector. Run the selected
+command locally, not on the VPS.
 
-### 1. Confirm the local ChatGPT/Codex sign-in
+### 2. Complete the local ChatGPT/Codex sign-in
 
-<img src="https://cdn.jsdelivr.net/npm/relmio@latest/docs/images/setup/01-local-sign-in-ready.png" alt="Sanitized local sign-in ready screen" width="720">
+<img src="https://cdn.jsdelivr.net/npm/relmio@latest/docs/images/setup/01-local-sign-in-ready.png" alt="Sanitized preview-mode sample credential state, not a real saved-login confirmation" width="626">
 
-### 2. Verify the VPS identity
+This image shows a sanitized preview-mode sample credential state; it does not
+confirm that a real local ChatGPT login was saved. During a real fresh login,
+the browser confirmation states that the credentials were saved locally.
 
-<img src="https://cdn.jsdelivr.net/npm/relmio@latest/docs/images/setup/02-vps-identity-confirmed.png" alt="Sanitized VPS fingerprint confirmation screen" width="720">
+### 3. Verify the VPS identity
 
-### 3. Choose the detected n8n container and network
+<img src="https://cdn.jsdelivr.net/npm/relmio@latest/docs/images/setup/02-vps-identity-confirmed.png" alt="VPS identity confirmation with a sanitized sample address and SSH fingerprint" width="720">
 
-<img src="https://cdn.jsdelivr.net/npm/relmio@latest/docs/images/setup/03-n8n-detected.png" alt="Sanitized n8n discovery screen" width="720">
+Confirm the SSH host fingerprint before authentication. The screenshot uses the
+reserved sample host `vps.example.test`, a sample fingerprint, and a blank
+password field.
 
-### 4. Review the exact sidecar-only plan
+### 4. Choose the detected n8n container and network
 
-<img src="https://cdn.jsdelivr.net/npm/relmio@latest/docs/images/setup/04-install-plan.png" alt="Sanitized installation plan screen" width="720">
+<img src="https://cdn.jsdelivr.net/npm/relmio@latest/docs/images/setup/03-n8n-detected.png" alt="Detected n8n container and shared Docker network" width="720">
 
-### 5. Copy the verified n8n settings
+Discovery is read-only; choose the existing n8n container and shared Docker
+network.
 
-<img src="https://cdn.jsdelivr.net/npm/relmio@latest/docs/images/setup/05-bridge-ready.png" alt="Sanitized verified bridge screen" width="720">
+### 5. Review the exact sidecar-only plan
+
+<img src="https://cdn.jsdelivr.net/npm/relmio@latest/docs/images/setup/04-install-plan.png" alt="Exact sidecar-only installation plan, including forbidden actions" width="720">
+
+The plan names the allowed sidecar work and explicitly excludes edits or
+restarts of n8n, a published host port, and a Traefik route.
+
+### 6. Copy the verified n8n settings
+
+<img src="https://cdn.jsdelivr.net/npm/relmio@latest/docs/images/setup/05-bridge-ready.png" alt="Private bridge ready screen with n8n OpenAI credential settings" width="720">
 
 Use these values in an n8n OpenAI credential:
 
@@ -219,6 +251,43 @@ Add Custom Header: Off
 The `local-only` value is a placeholder required by n8n. It is not an OpenAI
 Platform API key.
 
+For an n8n **HTTP Request** node, use **Generic Credential Type** → **Bearer
+Auth**, name the credential `openai-oauth`, and enter `local-only` as the
+bearer token. Enable **Send Headers** with `Content-Type: application/json`,
+then enable **Send Body** → **JSON** → **Using JSON** and paste:
+
+```json
+{
+  "model": "gpt-5.6-sol",
+  "messages": [
+    {
+      "role": "user",
+      "content": "What is a robot?"
+    }
+  ],
+  "response_format": {
+    "type": "json_schema",
+    "json_schema": {
+      "name": "answer",
+      "schema": {
+        "type": "object",
+        "properties": {
+          "content": { "type": "string" }
+        },
+        "required": ["content"],
+        "additionalProperties": false
+      },
+      "strict": true
+    }
+  }
+}
+```
+
+Use `POST http://n8n-openai-oauth:10531/v1/chat/completions` as the URL. The
+local wizard's **Copy HTTP request recipe** action supplies the same fields.
+Replace the model only if the wizard reports a different ID. The full guide
+has the importable cURL version.
+
 ## Important boundaries
 
 - Relmio does not create an OpenAI Platform API key.
@@ -228,7 +297,8 @@ Platform API key.
 - Relmio never edits, rebuilds, recreates, stops, or restarts the existing n8n
   container.
 - This is an unofficial community project, not affiliated with or endorsed by
-  OpenAI, xAI, or n8n. Provider access, models, limits, and policies can change.
+  OpenAI, xAI, n8n, Hostinger, Telegram, or AppBuildersPH. Provider access,
+  models, limits, and policies can change.
 - Use it only where your account, subscription, provider terms, and applicable
   policies allow.
 

package/docs/n8n-configuration.md

@@ -97,8 +97,9 @@ the chain.
 
 ## 3. HTTP Request node
 
-The HTTP Request recipe calls the bridge directly and does not need the n8n
-OpenAI credential.
+The HTTP Request recipe calls the bridge directly with n8n's generic Bearer
+Auth credential. It uses the Chat Completions route because the body below uses
+the `messages` format shown in the n8n node.
 
 ### Copy-paste fields
 
@@ -111,69 +112,120 @@ POST
 URL:
 
 ```text
-http://n8n-openai-oauth:10531/v1/responses
+http://n8n-openai-oauth:10531/v1/chat/completions
 ```
 
 Authentication:
 
 ```text
-None
+Generic Credential Type
 ```
 
-Header 1 name:
+Generic Auth Type:
 
 ```text
-Authorization
+Bearer Auth
 ```
 
-Header 1 value:
+Credential name:
 
 ```text
-Bearer local-only
+openai-oauth
 ```
 
-Header 2 name:
+Bearer token:
+
+```text
+local-only
+```
+
+Enable **Send Headers** and add this header:
+
+Header name:
 
 ```text
 Content-Type
 ```
 
-Header 2 value:
+Header value:
 
 ```text
 application/json
 ```
 
-JSON body:
+Enable **Send Body**, select **JSON** for **Body Content Type**, and choose
+**Using JSON** for **Specify Body**. Paste this body:
 
 ```json
 {
-  "model": "PASTE_ONE_MODEL_ID_FROM_THE_WIZARD",
-  "input": "Reply with exactly: bridge works"
+  "model": "gpt-5.6-sol",
+  "messages": [
+    {
+      "role": "user",
+      "content": "What is a robot?"
+    }
+  ],
+  "response_format": {
+    "type": "json_schema",
+    "json_schema": {
+      "name": "answer",
+      "schema": {
+        "type": "object",
+        "properties": {
+          "content": { "type": "string" }
+        },
+        "required": ["content"],
+        "additionalProperties": false
+      },
+      "strict": true
+    }
+  }
 }
 ```
 
-Enable **Send Headers** and **Send Body**, select a JSON body, and paste the
-object above.
+If the wizard reports a different model ID, replace only `gpt-5.6-sol` with
+that detected ID. The `local-only` bearer value is a harmless n8n placeholder;
+it is not an OpenAI Platform API key.
 
 ### Importable cURL version
 
-The n8n HTTP Request node can import a cURL command. Replace only the model
-placeholder:
+The n8n HTTP Request node can import this cURL command. Replace only the model
+if the wizard reports a different ID:
 
 ```bash
 curl --request POST \
-  --url http://n8n-openai-oauth:10531/v1/responses \
+  --url http://n8n-openai-oauth:10531/v1/chat/completions \
   --header 'Authorization: Bearer local-only' \
   --header 'Content-Type: application/json' \
   --data '{
-    "model": "PASTE_ONE_MODEL_ID_FROM_THE_WIZARD",
-    "input": "Reply with exactly: bridge works"
+    "model": "gpt-5.6-sol",
+    "messages": [
+      {
+        "role": "user",
+        "content": "What is a robot?"
+      }
+    ],
+    "response_format": {
+      "type": "json_schema",
+      "json_schema": {
+        "name": "answer",
+        "schema": {
+          "type": "object",
+          "properties": {
+            "content": { "type": "string" }
+          },
+          "required": ["content"],
+          "additionalProperties": false
+        },
+        "strict": true
+      }
+    }
   }'
 ```
 
-The placeholder header is included because it matches OpenAI-compatible
-client behavior. It is not a real API credential.
+The cURL `Authorization` header is equivalent to the n8n Bearer Auth
+credential. It is included so the command can be imported or run as a direct
+connectivity check.
 
 ### Expression-driven HTTP body
 
@@ -182,8 +234,26 @@ After the fixed test succeeds, switch the entire JSON body field to
 
 ```javascript
 ={{ {
-  model: "PASTE_ONE_MODEL_ID_FROM_THE_WIZARD",
-  input: $json.prompt
+  model: "gpt-5.6-sol",
+  messages: [
+    {
+      role: "user",
+      content: $json.prompt
+    }
+  ],
+  response_format: {
+    type: "json_schema",
+    json_schema: {
+      name: "answer",
+      schema: {
+        type: "object",
+        properties: { content: { type: "string" } },
+        required: ["content"],
+        additionalProperties: false
+      },
+      strict: true
+    }
+  }
 } }}
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "relmio",
-  "version": "0.2.15",
+  "version": "0.3.1",
   "description": "Turn a supported ChatGPT/Codex OAuth sign-in into a private OpenAI-compatible endpoint, starting with self-hosted n8n.",
   "keywords": [
     "relmio",

package/src/ui/app.js

@@ -123,8 +123,28 @@ async function copyText(value) {
 function renderHttpRequestBody(model) {
   element("result-http-body").textContent = JSON.stringify(
     {
-      model,
-      input: "Reply with exactly: bridge works",
+      model: model === "Not detected" ? "gpt-5.6-sol" : model,
+      messages: [
+        {
+          role: "user",
+          content: "What is a robot?",
+        },
+      ],
+      response_format: {
+        type: "json_schema",
+        json_schema: {
+          name: "answer",
+          schema: {
+            type: "object",
+            properties: {
+              content: { type: "string" },
+            },
+            required: ["content"],
+            additionalProperties: false,
+          },
+          strict: true,
+        },
+      },
     },
     null,
     2,
@@ -144,9 +164,16 @@ function copyHttpRecipe() {
   return [
     "Method: POST",
     `URL: ${element("result-http-url").textContent}`,
-    "Authorization: Bearer local-only",
+    "Authentication: Generic Credential Type",
+    "Generic Auth Type: Bearer Auth",
+    "Credential: openai-oauth",
+    `Bearer token: ${element("result-key").textContent}`,
+    `Authorization: ${element("result-http-auth").textContent}`,
     "Content-Type: application/json",
-    "Authentication: None",
+    "Send Headers: On",
+    "Send Body: On",
+    "Body Content Type: JSON",
+    "Specify Body: Using JSON",
     "JSON body:",
     element("result-http-body").textContent,
   ].join("\n");
@@ -598,7 +625,7 @@ element("install-button").addEventListener("click", async (event) => {
     element("result-model").textContent = firstModel;
     element("result-models").textContent = result.models.join(", ");
     element("result-http-url").textContent =
-      `${result.baseUrl.replace(/\/$/u, "")}/responses`;
+      `${result.baseUrl.replace(/\/$/u, "")}/chat/completions`;
     renderHttpRequestBody(firstModel);
     showStep(5);
     setMessage(