@tityra/cli 1.1.0 → 1.1.1

package/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## 1.1.1
+
+- Update customer-facing audit terminology to describe website content audits.
+- Clarify the content delivery, structure and context covered by the service.
+
 ## 1.1.0
 
 - Clarify that audit requests use explicit authorisation and validated scope without a second manual staff authority confirmation, while retaining report quality and commercial checks.

package/README.md

@@ -2,11 +2,11 @@
 
 Your Tityra workspace, from the terminal. Explore projects, read audit reports and work through findings from the command line, scripts or an AI agent.
 
-The CLI is an API client for the Tityra service. It uses the same account permissions, selected projects and customer workflows as the application.
+Tityra's website content audits review content delivery, structure and available context within an agreed website scope. Reports document findings and supporting evidence. The CLI is an API client for the Tityra service and uses the same account permissions, selected projects and customer workflows as the application.
 
 ## Project status
 
-Version `1.1.0` adds project monitoring commands and included-audit pricing status. Stable releases use npm's `latest` tag; check the [npm package page](https://www.npmjs.com/package/@tityra/cli) for the currently published version. CI targets Node.js 22 and 24 on Linux, macOS and Windows; local regression tests use isolated fixtures rather than live customer accounts.
+Version `1.1.1` updates the terminology used for Tityra's website content audit service. Version `1.1.0` added project monitoring commands and included-audit pricing status. Stable releases use npm's `latest` tag; check the [npm package page](https://www.npmjs.com/package/@tityra/cli) for the currently published version. CI targets Node.js 22 and 24 on Linux, macOS and Windows; local regression tests use isolated fixtures rather than live customer accounts.
 
 ## Basic functionality
 
@@ -24,7 +24,7 @@ The interactive workspace offers read-only navigation. Account changes use the e
 
 ## Prerequisites and installation
 
-You need **Node.js 22.14 or later**, a Tityra customer account and permission to access the projects you select. Staff and partner operations are not delegated through this connection. Browser login requires the browser to reach the temporary loopback callback on the computer running the CLI.
+You need **Node.js 22.14 or later**, a Tityra customer account and permission to access the projects you select. Staff operations are not delegated through this connection. Browser login requires the browser to reach the temporary loopback callback on the computer running the CLI.
 
 Install the stable release:
 
@@ -75,13 +75,13 @@ Audit options describe the existing eligibility and review rules. A submitted re
 
 ### Workspace plans and weekly monitoring
 
-Scale and Enterprise support unlimited organisations, projects and members. Enterprise offers monthly billing at £3,600 or annual billing at £36,000, excluding VAT, with one scheduled AX Audit per week for each enabled project and up to 500 pages per project. Check [current plans and prices](https://app.tityra.com/customer) in your account before subscribing.
+Scale and Enterprise support unlimited organisations, projects and members. Enterprise offers monthly billing at £3,600 or annual billing at £36,000, excluding VAT, with one scheduled In-Depth Audit per week for each enabled project and up to 500 pages per project. Check [current plans and prices](https://app.tityra.com/customer) in your account before subscribing.
 
 Enable **Monitor this project** in the Tityra application, or use the monitoring commands below with an explicitly granted `monitoring:write` permission and current project management access. Confirm that you are authorised to scan the website and selected pages. Eligibility comes from the project's organisation and its explicitly assigned Billing Profile, with an active subscription or explicit complimentary assignment that includes weekly monitoring. Your personal plan or membership in another paying organisation does not supply it. Your confirmed project consent enables monitoring without a separate administrator approval. Reports are delivered automatically after the required checks. You can pause and resume each project separately; existing reports remain available.
 
-The first included AX Audit is due seven days after the project's first production audit request for its current website, whether that request was Free Audit, AX Audit or Expert Review. If no request exists, confirmed monitoring consent starts that interval. Enabling or resuming an eligible project whose audit is already due automatically queues one included AX Audit. Later included audits remain at least seven days apart; missed slots do not accumulate. Read the server's `nextScheduledAt` and `history` rather than calculating a new start date locally.
+The first included website content audit is due seven days after the project's first production audit request for its current website, whether that request was Initial Audit, In-Depth Audit or Expert Review. If no request exists, confirmed monitoring consent starts that interval. Enabling or resuming an eligible project whose audit is already due automatically queues one included audit. Later included audits remain at least seven days apart; missed slots do not accumulate. Read the server's `nextScheduledAt` and `history` rather than calculating a new start date locally.
 
-Use `audits list` and `reports get` to read released weekly AX Audit reports within the projects and permissions you approved. An AX Audit submitted through `audits create` is an additional request, charged separately; it does not replace the included weekly AX Audit slot. Expert Review is never included in weekly monitoring and always follows the normal separately paid request and checkout process. Free Audit requests retain their normal eligibility limits. The CLI cannot choose a payer or change a subscription.
+Use `audits list` and `reports get` to read released weekly website content audit reports within the projects and permissions you approved. A paid In-Depth Audit submitted through `audits create` is an additional request, charged separately; it does not replace the included weekly audit slot. Expert Review is never included in weekly monitoring and always follows the normal separately paid request and checkout process. Initial Audit requests retain their normal eligibility limits. The CLI cannot choose a payer or change a subscription.
 
 Audit lists show the server's pricing status when your connection has `billing:read`; genuine included monitoring requests use `included`. A missing pricing status does not mean a payment is due. Use `audits payment AUDIT_ID` for current payment requirements. Normal report publication and payment checks remain in force.
 

package/dist/commands/audits.js

@@ -37,7 +37,7 @@ export function registerAuditsCommands(program, context) {
     writeOptions(audits
         .command('create')
         .description('Request an additional audit with explicit authorisation for its website scope')
-        .addHelpText('after', '\nYour authorisation: true declaration and the validated website scope provide the required request authorisation. No second manual staff confirmation of website authority is required.\nEligibility, scope and commercial checks still apply. Individually requested reports retain staff quality review.\nWeekly monitoring includes AX Audit only. Additional AX Audits and Expert Review require a separate request and payment through the normal checkout.\nUse projects monitoring get/update for an explicitly authorised project, or manage monitoring in the Tityra application.\n')).action(async (_options, command) => {
+        .addHelpText('after', '\nYour authorisation: true declaration and the validated website scope provide the required request authorisation. No second manual staff confirmation of website authority is required.\nEligibility, scope and commercial checks still apply. Individually requested reports retain staff quality review.\nWeekly monitoring includes the In-Depth Audit only. Additional In-Depth Audits and Expert Review require a separate request and payment through the normal checkout.\nUse projects monitoring get/update for an explicitly authorised project, or manage monitoring in the Tityra application.\n')).action(async (_options, command) => {
         await write(command, context, 'audit', '/api/agent/audits');
     });
 }

package/dist/commands/projects.js

@@ -12,7 +12,7 @@ export function registerProjectsCommands(program, context) {
     });
     const monitoring = projects
         .command('monitoring')
-        .description('Read or change weekly AX Audit monitoring for a selected project');
+        .description('Read or change weekly website content audit monitoring for a selected project');
     monitoring
         .command('get <project-id>')
         .description('Read current monitoring settings, scope, revision and report history')
@@ -21,8 +21,8 @@ export function registerProjectsCommands(program, context) {
     });
     writeOptions(monitoring
         .command('update <project-id>')
-        .description('Enable, pause, resume or update the scope of weekly AX Audit monitoring')
-        .addHelpText('after', '\nRequires an explicitly granted monitoring:write permission and current project management access.\nRead settings first; include the current expectedRevision and keep the same input and idempotencyKey when retrying an uncertain write.\nUse action enable with authorisation: true and the returned website as expectedWebsite. Use action disable to pause.\nEnabling monitoring records your website and scope authorisation without a separate administrator approval. Confirm that authorisation again after changing the website or scope.\nThe first included audit is due seven days after the first audit request for this project website, or after consent if none exists. Enabling or resuming an overdue eligible project queues its due AX Audit automatically. Read nextScheduledAt and history for the current server state.\nThe CLI cannot select a payer or change a subscription.\n')).action(async (id, _options, command) => {
+        .description('Enable, pause, resume or update the scope of weekly website content audits')
+        .addHelpText('after', '\nRequires an explicitly granted monitoring:write permission and current project management access.\nRead settings first; include the current expectedRevision and keep the same input and idempotencyKey when retrying an uncertain write.\nUse action enable with authorisation: true and the returned website as expectedWebsite. Use action disable to pause.\nEnabling monitoring records your website and scope authorisation without a separate administrator approval. Confirm that authorisation again after changing the website or scope.\nThe first included audit is due seven days after the first audit request for this project website, or after consent if none exists. Enabling or resuming an overdue eligible project queues its due website content audit automatically. Read nextScheduledAt and history for the current server state.\nThe CLI cannot select a payer or change a subscription.\n')).action(async (id, _options, command) => {
         await write(command, context, 'monitoring', `/api/agent/projects/${identifier(id)}/monitoring`, 'PATCH');
     });
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tityra/cli",
-  "version": "1.1.0",
+  "version": "1.1.1",
   "description": "Official Tityra CLI for projects, audits, reports and findings. Built for developers, AI agents and automated workflows.",
   "type": "module",
   "bin": {