@gspothq/cli 0.1.1 → 0.2.0

package/dist/{linkinator-program.js → linkinator-process.js}

@@ -1,10 +1,10 @@
-// packages/cli/src/checks/framework/site/linkinator-program.ts
+// src/checks/framework/site/linkinator-process.ts
 import { z } from "zod";
 import { pathToFileURL } from "node:url";
 import { createRequire } from "node:module";
 import { text } from "node:stream/consumers";
 
-// packages/cli/src/config/checks/framework/site.ts
+// src/config/checks/framework/site.ts
 var TEXT_SUFFIXES = new Set([
   ".htm",
   ".html",
@@ -28,15 +28,13 @@ var TEXT_SUFFIXES = new Set([
   ".yaml"
 ]);
 var LINKINATOR = "linkinator";
-var LOCAL_HOSTS = ["localhost", "127.0.0.1"];
+var LOCAL_HOSTS = new Set(["localhost", "127.0.0.1"]);
 var PURGECSS = "purgecss";
-var PURGECSS_CONTENT = ["**/*.html", "**/*.js"];
 
-// packages/cli/src/checks/framework/site/linkinator-program.ts
+// src/checks/framework/site/linkinator-process.ts
 var linkinatorRequestSchema = z.strictObject({
   paths: z.array(z.string().min(1)),
   origin: z.url().optional(),
-  external: z.boolean(),
   skipped: z.array(z.string())
 });
 var executable = z.string().parse(process.argv[2]);
@@ -57,7 +55,7 @@ var result = await checker.check({
   urlRewriteExpressions: rewrites,
   linksToSkip: (href) => {
     const url = new URL(href);
-    return Promise.resolve(!request.external && url.origin !== request.origin && !new Set(LOCAL_HOSTS).has(url.hostname) || skipped.some((pattern) => pattern.test(href)));
+    return Promise.resolve(url.origin !== request.origin && !LOCAL_HOSTS.has(url.hostname) || skipped.some((pattern) => pattern.test(href)));
   }
 });
 process.stdout.write(`${JSON.stringify(result)}

package/dist/{purgecss-program.js → purgecss-process.js}

@@ -1,10 +1,10 @@
-// packages/cli/src/checks/framework/site/purgecss-program.ts
+// src/checks/framework/site/purgecss-process.ts
 import { z } from "zod";
 import { pathToFileURL } from "node:url";
 import { createRequire } from "node:module";
 import { text } from "node:stream/consumers";
 
-// packages/cli/src/config/checks/framework/site.ts
+// src/config/checks/framework/site.ts
 var TEXT_SUFFIXES = new Set([
   ".htm",
   ".html",
@@ -28,24 +28,24 @@ var TEXT_SUFFIXES = new Set([
   ".yaml"
 ]);
 var LINKINATOR = "linkinator";
-var LOCAL_HOSTS = ["localhost", "127.0.0.1"];
+var LOCAL_HOSTS = new Set(["localhost", "127.0.0.1"]);
 var PURGECSS = "purgecss";
-var PURGECSS_CONTENT = ["**/*.html", "**/*.js"];
 
-// packages/cli/src/checks/framework/site/purgecss-program.ts
+// src/checks/framework/site/purgecss-process.ts
 var purgecssRequestSchema = z.strictObject({
-  configuration: z.string().min(1),
-  css: z.array(z.string().min(1)).min(1)
+  toolFile: z.string().min(1),
+  css: z.array(z.string().min(1)),
+  content: z.array(z.string().min(1))
 });
 var executable = z.string().parse(process.argv[2]);
 var api = await import(pathToFileURL(createRequire(executable).resolve(PURGECSS)).href);
 var request = purgecssRequestSchema.parse(JSON.parse(await text(process.stdin)));
-var configuration = await import(pathToFileURL(request.configuration).href);
-var report = await new api.PurgeCSS().purge({
-  ...configuration,
+var options = await import(pathToFileURL(request.toolFile).href);
+var results = await new api.PurgeCSS().purge({
+  ...options,
   css: request.css,
-  content: PURGECSS_CONTENT,
+  content: request.content,
   rejected: true
 });
-process.stdout.write(`${JSON.stringify(report)}
+process.stdout.write(`${JSON.stringify(results)}
 `);

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@gspothq/cli",
-    "version": "0.1.1",
+    "version": "0.2.0",
     "publishConfig": {
         "access": "public"
     },
@@ -30,14 +30,15 @@
         "./package.json": "./package.json"
     },
     "files": [
-        "dist",
+        "dist/gspot.js",
+        "dist/linkinator-process.js",
+        "dist/purgecss-process.js",
         "configurations",
-        "grammars",
-        "gspot.schema.json"
+        "grammars"
     ],
     "engines": {
         "bun": ">=1.4.2",
-        "node": ">=24.2.0"
+        "node": ">=24.15.0"
     },
     "dependencies": {
         "@clack/prompts": "1.8.0",
@@ -57,7 +58,6 @@
         "jsonc-parser": "3.3.1",
         "libpg-query": "18.1.4",
         "mdast-util-from-markdown": "2.0.3",
-        "mdast-util-to-string": "4.0.0",
         "nypm": "0.6.10",
         "p-limit": "7.3.2",
         "picocolors": "1.1.1",
@@ -65,7 +65,6 @@
         "scule": "1.3.0",
         "semver": "7.8.5",
         "signal-exit": "4.1.0",
-        "smol-toml": "1.9.0",
         "spdx-expression-parse": "5.0.0",
         "spdx-satisfies": "6.0.0",
         "std-env": "4.2.0",
@@ -77,12 +76,11 @@
         "zod": "4.6.2"
     },
     "devDependencies": {
-        "@bacons/xcode": "1.0.0-alpha.33",
         "@pgsql/types": "18.0.0",
-        "@types/mdast": "4.0.4",
         "@types/npmcli__config": "6.0.4",
         "@types/picomatch": "4.0.2",
         "@types/semver": "7.7.1",
+        "@types/which": "3.0.4",
         "tree-sitter-bash": "0.25.1",
         "tree-sitter-css": "0.25.0",
         "tree-sitter-html": "0.23.2",

package/configurations/infrastructure/github-actions/zizmor.yml

@@ -1,3 +0,0 @@
-rules:
-    unpinned-uses:
-        disable: true

package/configurations/language/bash/rules/NAMING.md

@@ -1,62 +0,0 @@
-# Bash Naming
-
-Bash naming follows Google shell guidance, with the overrides below for file stems.
-
-## Bash case rules
-
-<!-- level: all -->
-
-- Executable scripts use `.sh` when invoked through a task runner or build
-  rules.
-- Omit the extension on an executable script only when users invoke it
-  as a command on `PATH`.
-- Give sourced libraries the `.sh` extension and no executable permission.
-- Numbered pipeline steps use `NN-description.sh`, such as `01-install.sh`; the numeric prefix defines a
-  structural prefix the naming check strips before it matches the stem.
-- Functions and mutable variables use `lower_snake_case`.
-- Package-like function prefixes may use `::` only when a script family already
-  uses that convention.
-
-| Avoid              | Prefer                     | Meaning              |
-| ------------------ | -------------------------- | -------------------- |
-| `DeployScript.sh`  | `deploy-api.sh`            | API deployment.      |
-| `deploy_script.sh` | `upload-storage-assets.sh` | Storage upload.      |
-| `helpers.sh`       | `archive-reports`          | A command on `PATH`. |
-
-Name a deployment function `deploy_api` and its local target
-`target_environment`.
-
-## Bash variables
-
-<!-- level: all -->
-
-- Loop variables name each item in the loop.
-- Name a temporary path after what it holds, such as `download_file` or `work_dir`; `tmp` and
-  `temp` say nothing.
-- Avoid vague names when the domain provides a name.
-- Avoid shell-reserved and shell-special names for unrelated values.
-
-Use `migration_file` when iterating migration paths and `report_output` for
-captured report text. Check the report command's exit status before printing
-the captured output. A loop variable such as `i` does not describe a file.
-
-## Bash functions
-
-<!-- level: all -->
-
-- Function names use verb phrases when the function has side effects.
-- Name a function that prints to `stdout` for the data it prints.
-- Do not name scripts or functions after shell builtins or common commands.
-- Do not make function names so generic that logs and stack traces lose context.
-
-Name a port validator `validate_port`. Avoid `test`, which shadows a shell builtin, and
-generic names such as `run` or `process`.
-
-## Files
-
-<!-- level: all -->
-
-- Put a related script family in an owning subdirectory and give the contained
-  files role names such as `main.sh`, `state.sh`, `query.sh`, or `report.sh`.
-- External hook families may use a dynamic shared prefix when the external
-  interface owns those filenames.

package/configurations/language/css/rules/NAMING.md

@@ -1,17 +0,0 @@
-# CSS Naming
-
-## Selector and file names
-
-<!-- level: all -->
-
-- Name classes for the component or state, such as `order-card`, `order-card-title`, `is-active`, or `has-error`.
-- A state class starts with `is-` or `has-`. A script toggles it. Never style it alone.
-- Custom properties name the role of the value, not its appearance:
-  `--color-surface`, `--space-2`, `--font-size-body`, never `--blue` or `--big-margin`.
-- Theme overrides reuse the same property names under a theme selector; they never introduce
-  theme-specific property names.
-- Keyframe names describe the motion, such as `fade-in` or `slide-from-start`.
-- Name stylesheet files for what they hold such as `order-card.css`,
-  `tokens.css`, `layout.css`.
-- Utility classes, when the project uses a utility system, keep that system's names; hand-written
-  do not add utilities beside it.

package/configurations/language/html/rules/NAMING.md

@@ -1,16 +0,0 @@
-# HTML Naming
-
-## Route and attribute names
-
-<!-- level: all -->
-
-- Use kebab-case file names that match the public route: `about-us.html`, `pricing/index.html`.
-  Directory routes end in `index.html` in generated output.
-- Name public route segments in lowercase kebab-case with no trailing slash ambiguity: one
-  canonical form, with the other redirected.
-- Use `id` attributes for anchors, labels, and descriptions, not for styling.
-- Name `data-*` attributes in kebab-case for their value, such as `data-device-class`.
-- Placeholders follow the engine's convention and name the value.
-- Name content files for the route or content they serve, such as `content/legal/privacy.md`.
-- Name asset files in kebab-case for their subject and role, such as `hero-phone-dark.webp`. Never use
-  `image1.png` or `final-v2.svg`. Generate hashed names rather than writing them by hand.

package/configurations/language/javascript/rules/NAMING.md

@@ -1,31 +0,0 @@
-# JavaScript Naming
-
-JavaScript naming follows the same role, responsibility, and boundary principles
-as TypeScript. Use the JavaScript rules when editing `.js`, `.mjs`, `.cjs`, and
-plain JavaScript tooling files.
-
-## JavaScript imports and exports
-
-<!-- level: all -->
-
-- Namespace import aliases derive from the imported filename or
-  clear package name.
-- Named imports keep their exported name unless a collision forces an alias.
-- If the module requires a named import alias, use a domain or path component that
-  explains the collision.
-- Default import names follow the imported identifier type, but use default
-  imports only for ecosystem modules that require them.
-
-Use `fileOne` for a namespace import from `file-one.js`. If two modules export
-`Cat`, use an alias such as `DomesticatedCat` that identifies the owning domain.
-
-## JavaScript and TypeScript files
-
-<!-- level: all -->
-
-| Avoid            | Prefer                        | Meaning                        |
-| ---------------- | ----------------------------- | ------------------------------ |
-| `Helpers.js`     | `session-token-verifier.js`   | Session token verification.    |
-| `UserService.ts` | `user-repository.ts`          | User persistence.              |
-| `sharedUtils.ts` | `email-template-formatter.ts` | Email template formatting.     |
-| `data.cjs`       | `database-connection.cjs`     | Database connection lifecycle. |

package/configurations/language/markdown/markdownlint-cli2.mjs

@@ -1,19 +0,0 @@
-import { fileURLToPath } from 'node:url';
-
-export default {
-    config: { extends: fileURLToPath(new URL('markdownlint.jsonc', import.meta.url)) },
-    noBanner: true,
-    noProgress: true,
-    outputFormatters: [
-        [
-            /**
-             * Write the findings as JSON.
-             * @param {object} output the formatter input.
-             * @param {unknown} output.results the findings.
-             * @param {(message: string) => void} output.logMessage the report writer.
-             * @returns {void} nothing.
-             */
-            ({ results, logMessage }) => logMessage(JSON.stringify(results)),
-        ],
-    ],
-};

package/configurations/language/python/rules/NAMING.md

@@ -1,53 +0,0 @@
-# Python Naming
-
-Python naming follows Python Enhancement Proposal (PEP) 8, with the rules below.
-
-## Command inputs and external names
-
-<!-- level: all -->
-
-- CLI flags use lowercase kebab case, such as `--account-name` and
-  `--output-dir`.
-- Avoid single-letter names except loop counters and math notation.
-- Preserve provider capitalization in external names such as `AWS_REGION` and
-  provider resource IDs.
-
-## Python modules and imports
-
-<!-- level: all -->
-
-- Do not create package-level re-export layers only to preserve old names.
-- Keep `__all__` names accurate and ordered according to local lint rules.
-
-Import `AccountSettings` under its declared name. An alias such as `Thing`
-hides the contract and provides no collision information.
-
-## Python types and dataclasses
-
-<!-- level: all -->
-
-- Dataclass names describe the domain value they represent.
-- Field names describe the value inside the owning type without repeating the
-  type name.
-- Use `Path` variables with names that reveal whether they point to a directory,
-  file, report, output, or repository root.
-- Use `*_path` for filesystem paths and `*_dir` only for directories.
-- Use `*_id` only for real identifiers, not arbitrary names, or labels.
-- Use `*_name` for display or provider names.
-- Use `*_key` for dictionary keys and supported variant keys.
-
-| Avoid                    | Prefer           | Meaning             |
-| ------------------------ | ---------------- | ------------------- |
-| `Invoice.invoice_number` | `Invoice.number` | The invoice number. |
-| `Shipment.shipment_date` | `Shipment.date`  | The shipment date.  |
-
-## Python boundary names
-
-<!-- level: all -->
-
-- Keep raw provider or CLI names at the boundary.
-- Translate external names into domain names before passing values inward when
-  the external name differs from the domain concept.
-- Keep path construction with the code that owns the resource instead of repeating it in
-  unrelated operations.
-- Name functions that cross boundaries for the operation they perform.

package/configurations/language/sql/rules/NAMING.md

@@ -1,90 +0,0 @@
-# SQL Naming
-
-SQL names define durable infrastructure interfaces. Rename them only
-through migrations and contract-aware code changes.
-
-## SQL case rules
-
-<!-- level: all -->
-
-- SQL schemas, tables, columns, functions, function parameters, indexes,
-  triggers, constraints, and policies use `lower_snake_case`.
-- Fully qualify grants and function signatures when names have more than one possible meaning.
-- Do not use quoted sentence-style identifiers for local policy names.
-- Do not use pluralization or prefixes inconsistently inside one schema.
-
-| Avoid                        | Prefer                           | Meaning                            |
-| ---------------------------- | -------------------------------- | ---------------------------------- |
-| `public.OrderItems`          | `public.order_items`             | An order-item table.               |
-| `users_can_view_order_items` | `users_can_view_own_order_items` | A policy restricted to owned rows. |
-
-The policy name must describe its actual predicate. A name that says "own"
-does not establish ownership checks or enable Row Level Security.
-
-## Migration filenames
-
-<!-- level: all -->
-
-Follow the migration tool's file names. Name each migration for its durable database change.
-
-## SQL tables and columns
-
-<!-- level: all -->
-
-- Table names identify the domain set stored by the relation.
-- Column names identify the value, not the application layer that reads it.
-- Foreign-key columns use the referenced concept plus `_id`.
-- Timestamp columns use stable event names such as `created_at`,
-  `updated_at`, `deleted_at`, or a concrete domain event time.
-- Boolean columns use concise positive assertion names without an `is_`
-  prefix.
-- Avoid generic columns that hide meaning.
-
-| Avoid     | Prefer                      | Meaning                   |
-| --------- | --------------------------- | ------------------------- |
-| `data`    | `message_delivery_attempts` | Delivery attempt table.   |
-| `payload` | `provider_response`         | Response payload column.  |
-| `flag`    | `retryable`                 | Retry eligibility column. |
-| `date`    | `attempted_at`              | Attempt timestamp column. |
-
-## SQL functions and parameters
-
-<!-- level: all -->
-
-- SQL function names use verb phrases or domain operation names. These verbs govern function
-  names, not migration filenames.
-
-- Retrieval functions use `get_` regardless of whether they return one row,
-  an optional row, a collection, or a paginated collection. Do not use
-  `read_`, `find_`, `fetch_`, `load_`, or `list_` as retrieval synonyms.
-- Data-access mutation functions use `set_`, `insert_`, `update_`, or
-  `delete_` according to the operation they perform. Do not use `create_`,
-  `add_`, `save_`, `write_`, `put_`, `upsert_`, or `remove_` as synonyms.
-- Function parameters use `lower_snake_case`.
-- Parameter names never collide with table column names.
-- `SECURITY DEFINER` functions must have names that make the privileged action
-  clear.
-- Do not name functions like arbitrary script tasks.
-
-Use `archive_expired_orders` for a transactional operation that archives
-expired orders. Name its user argument `target_user_id` when `user_id` already names
-already a column in the affected tables. A generic `run` name hides the
-operation, and an unqualified `id` can obscure column ownership.
-
-## Indexes, constraints, triggers, and policies
-
-<!-- level: all -->
-
-- Name constraints and scope them to their table or concept.
-- Name indexes by table plus indexed columns or purpose.
-- Name triggers by event and action.
-- Name policies by actor plus allowed action.
-- Keep names stable because they appear in migrations, errors, grants, and
-  database inspection output.
-
-| Avoid           | Prefer                            | Meaning                              |
-| --------------- | --------------------------------- | ------------------------------------ |
-| `idx1`          | `messages_user_id_created_at_idx` | Index on user and creation time.     |
-| `check_status`  | `messages_status_not_empty_check` | Nonempty status constraint.          |
-| `trigger1`      | `messages_set_updated_at`         | Update timestamp trigger.            |
-| `select_policy` | `users_can_view_own_messages`     | Policy restricted to owned messages. |

package/configurations/language/swift/rules/NAMING.md

@@ -1,88 +0,0 @@
-# Swift Naming
-
-Swift naming follows the Apple API Design Guidelines and optimizes for call-site clarity.
-
-## Case, scope, and files
-
-<!-- level: all -->
-
-Preserve external names and domain notation that the team uses. Express privacy through access
-modifiers, not an underscore.
-
-Express a structural relationship through nesting rather than a longer
-top-level name: `Parser.Error`, not `ParseError`. A static property does not repeat its
-declaring type: `UIColor.primary`, not `UIColor.primaryColor`. Use `shared` and `default`
-only when they describe the role. Use an empty enum as a namespace only for tightly related
-constants or functions never instantiated.
-
-## Roles
-
-<!-- level: all -->
-
-A suffix says what a type owns and means one thing across the whole codebase. If `Repository`
-owns domain-facing data access in one feature, it does not own HTTP mechanics in another.
-Which suffixes a project uses depends on the pattern it picked, but these framework words have
-one meaning:
-
-| Role word        | Use when                                                                               |
-| ---------------- | -------------------------------------------------------------------------------------- |
-| `View`           | SwiftUI view or UIKit view type that presents UI.                                      |
-| `ViewController` | UIKit screen controller.                                                               |
-| `ViewModel`      | Presentation state and user intent owner for one screen, flow, or cohesive surface.    |
-| `ViewState`      | Value describing screen presentation state.                                            |
-| `ViewAction`     | Typed user or lifecycle intent emitted by a view.                                      |
-| `Coordinator`    | Navigation or flow state owner.                                                        |
-| `Router`         | Route mutation or destination-selection boundary, narrower than a coordinator.         |
-| `DataSource`     | UIKit list adapter that feeds rows and sections.                                       |
-| `CellModel`      | Values a reusable cell renders: strings, image references, state, and lightweight IDs. |
-
-Repository protocols speak domain language and return domain results through domain
-operations such as `TemplateRepository.getTemplate`; an implementation may name its technology
-such as `HTTPTemplateRepository` when that distinguishes real implementations. Client types own
-external API or SDK mechanics such as `TemplateAPIClient`. Coordinators own route state, destination
-construction, stack mutations, and presentation flow such as `TemplateCoordinator.showEditTemplate`.
-Keep route enums within their feature and name them for the flow. Give them stable domain identifiers
-such as `TemplateDestination.editTemplate`. Never give them view models, views, repository implementations, SDK
-clients, database records, or DTOs.
-
-## Methods, labels, and delegates
-
-<!-- level: all -->
-
-When the project uses view models, name a direct UI event for the event
-such as `submitButtonTapped()`, `cameraPermissionDenied()`, `selectedItemChanged(to:)`. Name domain work
-with a domain verb such as `enqueueFileUpload(_:)`, `refreshOrderHistory(for:)`,
-`validateEmailAddress(_:)`; `handle`, `process`, and `didTap` name neither. Reserve `handle...` for
-reserved for literal UIKit target-action and notification handlers marked `@objc`.
-
-Names form grammatical English at the call site: omit the first label when the base
-name and argument form a phrase and included when it clarifies a weak type. Initializer
-arguments that set stored properties use the property names with explicit `self.`, and
-factories use `make...` such as `makeTemplateView(for:)`. Nonmutating methods without side effects
-read as noun phrases, and mutating methods read as imperatives. Pairs follow `sort`/`sorted`,
-`append`/`appending`, `formUnion`/`union`.
-
-A delegate method passes the source object first and unlabeled, and never trims its signature because
-one caller currently owns it. Name a source-only `Void` event with the source type plus a tense
-phrase: `draftStore(_:didDeleteDraft:)`. A source-only `Bool` answer uses `can`, `is`, or
-another predicate, never `should` or `may`: `draftStoreCanDeleteDraft`. Name a source-only value with a
-noun phrase with a natural preposition: `numberOfSections(in:)`. Extra arguments make the
-second label describe the event or requested value:
-`messageListDataSource(_:heightForMessageAt:)`.
-
-## Protocols and identifiers
-
-<!-- level: all -->
-
-A protocol carries no `I` prefix and no `Protocol` suffix. Name a domain role with a noun such as `TemplateRepository`. Name a capability for its behavior, often with `-ing`,
-such as `ProgressReporting`, `ThemeColorProviding`, or `LoginCoordinating`. Avoid an automatic `-able`
-name that describes no clear capability. `Provider`, `Repository`, `Client`, and
-`Coordinating` appear only when the protocol serves that role, and no protocol exists per ViewModel or use
-case merely to enable mocks.
-
-Presentation identifiers provide stable interfaces for UI identity, diffable data sources,
-navigation, persistence, and tests, named for what they identify rather than the framework
-that consumes them. Snapshot items use stable presentation or domain IDs, never DTO identity,
-array offsets, or index paths. `id` suffices when the enclosing type supplies the context
-such as `MessageRow.id`; a role-qualified name such as `selectedMessageID` or `conversationID`
-serves a scope with several identifiers.

package/configurations/language/typescript/rules/NAMING.md

@@ -1,73 +0,0 @@
-# TypeScript Naming
-
-TypeScript naming follows the project rules here. Use Google TypeScript guidance as
-a strong default for many language choices. The rules below deliberately override some of it, and
-say so where they do.
-
-## TypeScript files and modules
-
-<!-- level: all -->
-
-- File names describe the primary exported type, function, route, or cohesive
-  capability.
-- Do not use namespaces, `module`, triple-slash references, or
-  `import x = require(...)` to simulate ownership.
-- Do not create files named only for generic reuse.
-- Keep generated file names only when generator-owned.
-
-## TypeScript variables
-
-<!-- level: all -->
-
-- Use meaningful, pronounceable names.
-- Use the same vocabulary for the same concept.
-- Use explanatory destructuring names.
-- Avoid mental mapping with single-letter names except tiny local scopes.
-- Use named constants for meaningful repeated numbers or strings.
-- Do not add context already present in the type or owner.
-
-For a range comparison, name the value `value` and the bounds `minimum` and
-`maximum`. Use a type that supports the comparison, such as `number`; an
-unconstrained generic does not establish ordering semantics.
-
-When iterating a map of users, destructure its entries as `[userId, user]`
-instead of naming each pair `keyValue`.
-
-Name a reused daily timer duration `MILLISECONDS_PER_DAY` and define it as
-`86_400_000`. The name explains both the interval and its unit.
-
-## TypeScript functions
-
-<!-- level: all -->
-
-- Function names say what they do.
-- Prefer two or fewer parameters.
-- Use an options object for many arguments, multiple same-type arguments,
-  optional groups, or boolean flags.
-- Do not use boolean flags to choose separate behaviors.
-- Prefer a positive predicate name plus `!` at the call site over a negative
-  predicate function.
-- Use async/await in names only to distinguish from a blocking counterpart. Normally the return type communicates async.
-- Name functions by domain work, not implementation mechanics.
-
-## TypeScript types
-
-<!-- level: all -->
-
-- Use unions and discriminated unions for alternatives.
-- Use interfaces only when a framework contract, declaration merging, or
-  `implements` relationship makes an interface the clearest tool.
-- Do not encode optionality in an alias name.
-- Use optional fields and parameters for values callers can omit.
-- Avoid return-type-only generics. When using an existing return-type-only
-  generic API, specify the generic explicitly.
-- Name index keys meaningfully when the type needs an index signature.
-- Prefer `Map` for key/value operations.
-
-Name a coffee response union `CoffeeResponse`; put `| undefined` on an
-operation that can return no response. Name a user index `UsersById` and its
-index key `userId`.
-
-A function that selects a collection element ties its generic to the input
-collection. Its return contract must account for an empty collection unless
-the input type or validation proves that an element exists.

package/configurations/library/swift-snapshot-testing/manifest.toml

@@ -1,32 +0,0 @@
-[configuration]
-title = "Swift Snapshot Testing"
-requires = ["swift"]
-description = "SnapshotTesting comparisons keep recording disabled and retain references only while their test source exists."
-
-[detect]
-dependencies = ["swift-snapshot-testing"]
-
-[files]
-paths = ["**/*.swift", "**/__Snapshots__/**"]
-kinds = ["source", "binary"]
-
-[[check]]
-name = "recording"
-example = "A snapshot test left in recording mode reports a recording finding. Inspect and retain the intended reference images, remove the recording flag, and rerun in comparison mode."
-level = "recommended"
-stage = "commit"
-files = { tags = ["swift-test"] }
-summary = "Refuses a snapshot test left in a recording mode."
-why = "A recording test writes a new reference and passes, so it approves whatever the screen shows."
-help = "Take the recording flag out, and commit the references it wrote after looking at them."
-
-[[check]]
-name = "references"
-example = "A snapshot reference folder whose corresponding test file no longer exists reports unused references. Delete the unused references, or rename the folder to match the renamed test file."
-level = "all"
-stage = "commit"
-runs = "scope"
-files = { paths = ["**/*"], kinds = ["source", "binary"] }
-summary = "Checks that __Snapshots__ reference folders name a sibling Swift test file."
-why = "References of a deleted test stay in the repository, and every clone pays for them."
-help = "Delete the references of the test that is gone, or rename the folder after the test file."