@abgov/nx-adsp 13.13.0 → 13.14.0

package/README.md

@@ -251,9 +251,13 @@ npx @abgov/adsp-cli login --env <dev|test|prod> --tenant "<Your Tenant>" --scope
 When you run a generator:
 
 - if a valid cached token exists, generation proceeds with no prompt;
-- if not, an **interactive** run launches `adsp login` for you (browser); a
-  **non-interactive** run (`--no-interactive` / CI) fails with the exact
-  `adsp login` command to run first.
+- if `ADSP_CLIENT_ID`/`ADSP_CLIENT_SECRET` are set (a CI service account — requires
+  `@abgov/adsp-cli` ^1.7.0+ and the tenant's `adsp-cli-ci` Keycloak client enabled with credentials
+  generated), a fresh token is acquired non-interactively via that account, no browser and no prior
+  `adsp login` needed;
+- otherwise, an **interactive** run launches `adsp login` for you (browser); a **non-interactive**
+  run (`--no-interactive` / CI) fails with the exact `adsp login` command to run first, or the two
+  env vars above to set instead.
 
 Generator flags that steer which tenant/token is used:
 
@@ -269,7 +273,7 @@ have a tenant yet? That picker also offers a **+ Create a new tenant** choice
 `tenant-service-admin`, and (unless `tenant-service-admin`) that doesn't already own a tenant (one
 per admin email). Picking it prompts for a name and waits for the new realm to finish provisioning
 before continuing the login as that tenant. Requires `@abgov/adsp-cli` ^1.4.0+ (this plugin pins
-^1.6.0 or later).
+^1.7.0 or later).
 
 ## Agent consultation
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@abgov/nx-adsp",
-  "version": "13.13.0",
+  "version": "13.14.0",
   "license": "Apache-2.0",
   "main": "src/index.js",
   "description": "Government of Alberta - Nx plugin for ADSP apps.",

package/src/generators/express-service/express-service.spec.ts

@@ -96,6 +96,7 @@ describe('Express Service Generator', () => {
     const agents = host.read('apps/test/AGENTS.md').toString();
     expect(agents).toContain('@abgov/adsp-sdk-mcp-server');
     expect(agents).toContain('get_platform_quickstart');
+    expect(agents).toContain('get_service_configuration_schema');
     expect(agents).toContain('search_sdk_reference');
   }, 60000);
 

package/src/generators/express-service/files/AGENTS.md__tmpl__

@@ -26,6 +26,13 @@ APIs from memory** when integrating ADSP capabilities:
 
 - `get_platform_quickstart` — the canonical `initializePlatform` usage pattern and
   a capabilities summary. Start here for "how do I use ADSP from this service?".
+  Covers `serviceConfigurations` too — registration creates resources, not just
+  declares a dependency, and there's both a `NamedConfiguration` and a
+  plain-object variant.
+- `get_service_configuration_schema` — fetches the live configuration schema for
+  a platform service from configuration-service. Use this before writing a
+  `serviceConfigurations` entry in `initializeService()` so its shape matches
+  what that service actually expects, instead of guessing.
 - `search_sdk_reference` — look up `@abgov/adsp-service-sdk` by symbol, module, or
   keyword; returns kind, description, option/return shape, example, deprecation.
 - `search_adsp_docs` — keyword search across ADSP platform docs (getting started,