MOBILE-5004 ai: Rewrite negative sentences

Author: crazyserver

.github/copilot-instructions.md

@@ -12,7 +12,7 @@ Services are NOT Angular-managed singletons. Use the `makeSingleton` pattern:
 export class MyService { }
 export const My = makeSingleton(MyService);
 ```
-Import from `@singletons` for platform APIs, never directly from `@angular/core` or Ionic.
+Import from `@singletons` for platform APIs, only import directly from `@angular/core` or Ionic when necessary.
 
 ### Delegate Pattern for Extensibility
 The codebase uses delegates extensively to allow addons to register handlers:
@@ -154,10 +154,10 @@ Define tables with columns, indexes in site schemas. Version increments trigger
 
 ## Common Pitfalls
 
-1. **Don't** inject Angular services directly - use singletons via `@singletons`
-2. **Don't** use `@NgModule({ declarations: [] })` for new modules - use standalone components
-3. **Don't** forget to register handlers in `provideAppInitializer`
-4. **Don't** import from barrel files that aren't configured in `tsconfig.json` paths
+1. Always use singletons via `@singletons` instead of injecting Angular services directly
+2. Use standalone components for new modules instead of `@NgModule({ declarations: [] })`
+3. Always register handlers in `provideAppInitializer`
+4. Import only from barrel files that are configured in `tsconfig.json` paths
 5. **Do** run `gulp` before testing to ensure lang files are built
 6. **Do** use `CoreSitesReadingStrategy` when fetching data to control cache vs network behavior
 

.github/instructions/angular.instructions.md

@@ -48,7 +48,7 @@ Instructions for generating high-quality Angular applications with TypeScript, u
 ### State Management
 - Use Angular Signals for reactive state management in components and services
 - Leverage `signal()`, `computed()`, and `effect()` for reactive state updates
-- We won't use any experimental features of Angular Signals such as `resource()`
+- Use only stable features of Angular Signals and exclude experimental features such as `resource()`
 - Use writable signals for mutable state and computed signals for derived state
 - Handle loading and error states with signals and proper UI feedback
 - Use Angular's `AsyncPipe` to handle observables in templates when combining signals with RxJS
@@ -64,7 +64,7 @@ Instructions for generating high-quality Angular applications with TypeScript, u
 - Sanitise user inputs using Angular's built-in sanitisation
 - Implement route guards for authentication and authorisation
 - Validate form inputs with Angular's reactive forms and custom validators
-- Follow Angular's security best practices (e.g., avoid direct DOM manipulation)
+- Follow Angular's security best practices by using Angular APIs instead of direct DOM manipulation
 
 ### Performance
 - Enable production builds with `npm run build:prod` for optimisation

.github/instructions/nodejs-ts-jest.instructions.md

@@ -7,20 +7,20 @@ applyTo: '**/*.test.ts'
 
 ## Coding standards
 - Use TypeScript with ES2022 features and Node.js (version defined in .nvmrc) ESM modules
-- Use Node.js built-in modules and avoid external dependencies where possible
-- Ask the user if you require any additional dependencies before adding them
+- Use Node.js built-in modules and minimise external dependencies where possible
+- Ask the user before adding any additional dependencies
 - Always use async/await for asynchronous code, and use 'node:util' promisify function to avoid callbacks
 - Keep the code simple and maintainable
 - Use descriptive variable and function names
-- Do not add comments unless absolutely necessary, the code should be self-explanatory
-- Never use `null`, always use `undefined` for optional values
+- Write code that is self-explanatory, so comments are only needed when absolutely necessary
+- Use `undefined` for optional values instead of `null`
 - Prefer functions over classes
 
 ## Testing
 - Use Jest for testing
 - It's recommended to write tests for all new features and bug fixes
 - Ensure tests cover edge cases and error handling
-- NEVER change the original code to make it easier to test, instead, write tests that cover the original code as it is
+- Always write tests that cover the original code as it is, without changing the original code for testability
 
 ## User interactions
 - Ask questions if you are unsure about the implementation details, design choices, or need clarification on the requirements

.github/instructions/typescript-5-es2021.instructions.md

@@ -15,7 +15,7 @@ applyTo: '**/*.ts'
 ## General Guardrails
 
 - Target TypeScript 5.x / ES2021 and prefer native features over polyfills.
-- Use pure ES modules; never emit `require`, `module.exports`, or CommonJS helpers.
+- Use pure ES modules; always emit only ES module syntax, not `require`, `module.exports`, or CommonJS helpers.
 - Rely on the project's build, lint, and test scripts unless asked otherwise.
 - Note design trade-offs when intent is not obvious.
 
@@ -25,7 +25,7 @@ applyTo: '**/*.ts'
 - Use kebab-case filenames (e.g., `user-session.ts`, `data-service.ts`) unless told otherwise.
 - Keep tests, types, and helpers near their implementation when it aids discovery.
 - Reuse or extend shared utilities when it reduces duplication and keeps responsibilities focused.
-- Create new utilities when they serve a distinct purpose; avoid bloated "Utils" classes that mix unrelated concerns.
+- Create new utilities when they serve a distinct purpose; keep "Utils" classes focused on related concerns only.
 
 ## Naming & Style
 
@@ -46,7 +46,7 @@ applyTo: '**/*.ts'
 - Use discriminated unions for real-time events and state machines.
 - Centralise shared contracts instead of duplicating shapes.
 - Express intent with TypeScript utility types (e.g., `Readonly`, `Partial`, `Record`).
-- Prefer `type` over `interface` for defining shapes; use `interface` only when a class must implement it.
+- Prefer `type` over `interface` for defining shapes; use `interface` when a class must implement it.
 
 ## Async, Events & Error Handling
 
@@ -68,13 +68,13 @@ applyTo: '**/*.ts'
 ## External Integrations
 
 - Instantiate clients outside hot paths and inject them for testability.
-- Never hardcode secrets; load them from secure sources.
+- Always load secrets from secure sources instead of hardcoding them.
 - Normalise external responses and map errors to domain shapes.
 
 ## Security Practices
 
 - Validate and sanitise external input with schema validators or type guards.
-- Avoid dynamic code execution and untrusted template rendering except on plugins.
+- Permit dynamic code execution and untrusted template rendering only on plugins.
 - Encode untrusted content before rendering HTML; use framework escaping or trusted types.
 - Use parameterised queries or prepared statements to block injection.
 - Favor immutable flows and defensive copies for sensitive data.
@@ -96,7 +96,7 @@ applyTo: '**/*.ts'
 
 - Add or update unit tests with the project's framework and naming style.
 - Expand integration or end-to-end suites when behavior crosses modules or platform APIs.
-- Avoid brittle timing assertions; prefer fake timers or injected clocks.
+- Use fake timers or injected clocks instead of brittle timing assertions.
 
 ## Performance & Reliability