ai-dev-requirements 0.3.1 → 0.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -106,6 +106,10 @@ Create `.requirements-mcp.json` in your project root:
106
106
  "type": "ones-pkce",
107
107
  "emailEnv": "ONES_ACCOUNT",
108
108
  "passwordEnv": "ONES_PASSWORD"
109
+ },
110
+ "openApiAuth": {
111
+ "type": "token",
112
+ "tokenEnv": "ONES_OPENAPI_TOKEN"
109
113
  }
110
114
  }
111
115
  },
@@ -123,13 +127,19 @@ Add to your `.mcp.json`:
123
127
  "args": ["ai-dev-requirements"],
124
128
  "env": {
125
129
  "ONES_ACCOUNT": "${ONES_ACCOUNT}",
126
- "ONES_PASSWORD": "${ONES_PASSWORD}"
130
+ "ONES_PASSWORD": "${ONES_PASSWORD}",
131
+ "ONES_OPENAPI_TOKEN": "${ONES_OPENAPI_TOKEN}"
127
132
  }
128
133
  }
129
134
  }
130
135
  }
131
136
  ```
132
137
 
138
+ `openApiAuth` is optional and independent from the internal `ones-pkce` product
139
+ session. It is used for documented Wiki metadata and search requests when
140
+ available. Wiki creates and updates always use the product session plus the live
141
+ JSONv1 collaboration protocol, so they do not require a Personal API Key.
142
+
133
143
  #### MCP security boundaries
134
144
 
135
145
  - ONES titles, descriptions, test cases, and attachment metadata are marked as untrusted data. Instructions embedded in them must never drive tool calls.