@fulmenhq/tsfulmen 0.1.6

package/schemas/crucible-ts/ascii/v1.0.0/box-chars.schema.json

@@ -0,0 +1,60 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://schemas.fulmenhq.dev/crucible/ascii/box-chars-v1.0.0.json",
+  "title": "BoxChars",
+  "description": "Characters used for drawing ASCII boxes and borders",
+  "type": "object",
+  "properties": {
+    "topLeft": {
+      "type": "string",
+      "description": "Top-left corner character",
+      "minLength": 1,
+      "maxLength": 1
+    },
+    "topRight": {
+      "type": "string",
+      "description": "Top-right corner character",
+      "minLength": 1,
+      "maxLength": 1
+    },
+    "bottomLeft": {
+      "type": "string",
+      "description": "Bottom-left corner character",
+      "minLength": 1,
+      "maxLength": 1
+    },
+    "bottomRight": {
+      "type": "string",
+      "description": "Bottom-right corner character",
+      "minLength": 1,
+      "maxLength": 1
+    },
+    "horizontal": {
+      "type": "string",
+      "description": "Horizontal line character",
+      "minLength": 1,
+      "maxLength": 1
+    },
+    "vertical": {
+      "type": "string",
+      "description": "Vertical line character",
+      "minLength": 1,
+      "maxLength": 1
+    },
+    "cross": {
+      "type": "string",
+      "description": "Cross/intersection character",
+      "minLength": 1,
+      "maxLength": 1
+    }
+  },
+  "required": [
+    "topLeft",
+    "topRight",
+    "bottomLeft",
+    "bottomRight",
+    "horizontal",
+    "vertical",
+    "cross"
+  ]
+}

package/schemas/crucible-ts/ascii/v1.0.0/string-analysis.schema.json

@@ -0,0 +1,45 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://schemas.fulmenhq.dev/crucible/ascii/string-analysis-v1.0.0.json",
+  "title": "StringAnalysis",
+  "description": "Analysis results for string properties including Unicode-aware width calculation",
+  "type": "object",
+  "properties": {
+    "length": {
+      "type": "integer",
+      "minimum": 0,
+      "description": "Total character length of the string"
+    },
+    "width": {
+      "type": "integer",
+      "minimum": 0,
+      "description": "Display width accounting for Unicode characters"
+    },
+    "hasUnicode": {
+      "type": "boolean",
+      "description": "Whether the string contains Unicode characters"
+    },
+    "lineCount": {
+      "type": "integer",
+      "minimum": 0,
+      "description": "Number of lines in the string"
+    },
+    "wordCount": {
+      "type": "integer",
+      "minimum": 0,
+      "description": "Number of words in the string"
+    },
+    "isMultiline": {
+      "type": "boolean",
+      "description": "Whether the string contains multiple lines"
+    }
+  },
+  "required": [
+    "length",
+    "width",
+    "hasUnicode",
+    "lineCount",
+    "wordCount",
+    "isMultiline"
+  ]
+}

package/schemas/crucible-ts/assessment/README.md

@@ -0,0 +1,25 @@
+# Assessment Schemas
+
+This directory contains shared schema definitions for assessment- and analysis-related
+artifacts that span multiple Fulmen tools.
+
+## Files
+
+| Schema                                    | Purpose                                                       |
+| ----------------------------------------- | ------------------------------------------------------------- |
+| `v1.0.0/severity-definitions.schema.json` | Canonical severity name/level mapping for assessment tooling. |
+
+### Severity Definitions
+
+`severity-definitions.schema.json` provides `$defs` that map assessment severity names
+(`info`, `low`, `medium`, `high`, `critical`) to sortable numeric levels (`0-4`).
+Consumers should reference these definitions via `$ref`, for example:
+
+```yaml
+fail_on:
+  $ref: ../../assessment/v1.0.0/severity-definitions.schema.json#/$defs/severityName
+  default: high
+```
+
+When comparing severities, always convert names to `severityLevel` using the canonical
+mapping (`severityMapping`) rather than relying on lexical ordering.

package/schemas/crucible-ts/assessment/v1.0.0/severity-definitions.schema.json

@@ -0,0 +1,60 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://schemas.fulmenhq.dev/assessment/severity-definitions-v1.0.0.json",
+  "title": "Assessment Severity Definitions",
+  "description": "Shared severity definitions for assessment and analysis tooling.",
+  "$comment": "Implementations MUST compare severities using severityLevel, not lexical ordering of severityName.",
+  "$defs": {
+    "severityName": {
+      "type": "string",
+      "enum": [
+        "info",
+        "low",
+        "medium",
+        "high",
+        "critical"
+      ],
+      "description": "Assessment severity name from lowest (info) to highest (critical)."
+    },
+    "severityLevel": {
+      "type": "integer",
+      "enum": [
+        0,
+        1,
+        2,
+        3,
+        4
+      ],
+      "description": "Numeric severity level for sorting and comparison (info=0, critical=4)."
+    },
+    "severityMapping": {
+      "type": "object",
+      "description": "Canonical mapping of severity names to numeric levels.",
+      "additionalProperties": false,
+      "properties": {
+        "info": {
+          "const": 0
+        },
+        "low": {
+          "const": 1
+        },
+        "medium": {
+          "const": 2
+        },
+        "high": {
+          "const": 3
+        },
+        "critical": {
+          "const": 4
+        }
+      },
+      "required": [
+        "info",
+        "low",
+        "medium",
+        "high",
+        "critical"
+      ]
+    }
+  }
+}

package/schemas/crucible-ts/config/fulmen-ecosystem/v1.0.0/README.md

@@ -0,0 +1,11 @@
+---
+title: "Fulmen Config Paths Schema"
+description: "JSON schema describing default config/data/cache locations for Fulmen ecosystem"
+author: "Schema Cartographer"
+date: "2025-10-02"
+last_updated: "2025-10-02"
+status: "draft"
+tags: ["config", "schema", "xdg"]
+---
+
+Use `fulmen-config-paths.schema.json` to validate documents that capture per-platform configuration directories. This schema complements the Fulmen Config Path Standard.

package/schemas/crucible-ts/config/fulmen-ecosystem/v1.0.0/fulmen-config-paths.schema.json

@@ -0,0 +1,61 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://schemas.fulmenhq.dev/config/fulmen-ecosystem/fulmen-config-paths-v1.0.0.json",
+  "title": "Fulmen Config Paths",
+  "description": "Describes shared configuration directories for Fulmen tools",
+  "type": "object",
+  "required": [
+    "platforms"
+  ],
+  "properties": {
+    "version": {
+      "type": "string",
+      "description": "Schema version or manifest revision"
+    },
+    "platforms": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": [
+        "linux",
+        "macos",
+        "windows"
+      ],
+      "properties": {
+        "linux": {
+          "$ref": "#/definitions/platformPaths"
+        },
+        "macos": {
+          "$ref": "#/definitions/platformPaths"
+        },
+        "windows": {
+          "$ref": "#/definitions/platformPaths"
+        }
+      }
+    }
+  },
+  "definitions": {
+    "platformPaths": {
+      "type": "object",
+      "required": [
+        "config",
+        "data",
+        "cache"
+      ],
+      "properties": {
+        "config": {
+          "type": "string",
+          "description": "Default configuration directory"
+        },
+        "data": {
+          "type": "string",
+          "description": "Default data directory"
+        },
+        "cache": {
+          "type": "string",
+          "description": "Default cache directory"
+        }
+      },
+      "additionalProperties": false
+    }
+  }
+}

package/schemas/crucible-ts/config/goneat/README.md

@@ -0,0 +1,60 @@
+# Goneat Configuration Schemas
+
+This directory contains JSON Schema definitions that codify configuration and policy
+files consumed by the goneat toolchain. Each schema is published at
+`https://schemas.fulmenhq.dev/config/goneat/<name>-<version>.schema.json` and should
+be referenced from the corresponding YAML/JSON policy files via the `$schema` field
+whenever possible.
+
+## Available Schemas
+
+| Schema                                        | Purpose                                                          |
+| --------------------------------------------- | ---------------------------------------------------------------- |
+| `goneat-config.yaml`                          | Core goneat CLI configuration (toolchain sources, telemetry opt) |
+| `dates.yaml`                                  | Date formatting conventions for release automation               |
+| `security-policy.yaml`                        | Security scanning and suppression policy                         |
+| `lifecycle-phase.json` / `release-phase.json` | Lifecycle metadata used by release automation                    |
+| `version-policy.schema.yaml`                  | Version SSOT propagation policy (new in v0.3.0)                  |
+
+## Version Policy (`version-policy.schema.yaml`)
+
+The version policy schema enables repositories to describe how the authoritative
+`VERSION` file propagates into downstream package manifests using goneat’s
+`version propagate` command. Policies live at `.goneat/version-policy.yaml` in consumer
+repositories and should reference the schema via:
+
+```yaml
+$schema: https://schemas.fulmenhq.dev/config/goneat/version-policy-v1.0.0.schema.json
+```
+
+Key capabilities:
+
+- **Schemes & Channels**: declare whether the repo uses SemVer or CalVer and optionally
+  constrain prerelease channels.
+- **Propagation Rules**: control default include/exclude patterns, handler-specific
+  overrides, workspace behaviour, and backup retention.
+- **Content Rules vs Guards**: `rules` describes version content constraints (channels,
+  tags, prerelease allowances) while `guards` enforce execution preconditions (branch
+  allow-lists, dirty worktree checks). Both sections are optional—planned for Phase 3a of
+  goneat’s roadmap.
+- **Extensibility**: `metadata` allows teams to attach internal annotations that goneat
+  will ignore while keeping the schema forward-compatible.
+
+The schema keys align with manifest filenames (e.g., `package.json`, `pyproject.toml`,
+`go.mod`). The workspace strategy supports three patterns:
+
+- `single-version`: all manifests inherit the root VERSION.
+- `opt-in`: only globs listed in `allowlist` receive independent version control.
+- `opt-out`: everything propagates except paths explicitly listed in `blocklist`.
+
+See the schema `examples` block for a reference configuration that covers common
+use cases (JS + Python monorepo with Go validation only). Additional cookbook
+samples will ship with goneat v0.3.0 documentation.
+
+## Contributing
+
+- Update the `$id` to point at the published schema URL when introducing new versions.
+- Keep the schema version number in lock-step with goneat releases that introduce
+  breaking changes to the configuration surface.
+- Whenever a schema is added or updated, ensure `make check-all` passes so that
+  downstream language wrappers receive the new definition during sync.

package/schemas/crucible-ts/config/goneat/v1.0.0/dates.yaml

@@ -0,0 +1,234 @@
+$schema: https://json-schema.org/draft/2020-12/schema
+$id: https://schemas.goneat.dev/config/dates/v1.0.0
+$version: 1.0.0
+title: Goneat Dates Configuration Schema
+description: Configuration schema for Goneat dates validation and fixes
+type: object
+properties:
+  enabled:
+    type: boolean
+    description: Enable dates validation
+    default: true
+    examples:
+      - true
+      - false
+  rules:
+    type: object
+    description: Rule-specific configurations
+    properties:
+      future_dates:
+        type: object
+        description: Detect dates in future (e.g., hallucinations)
+        properties:
+          enabled:
+            type: boolean
+            description: Enable future dates detection
+            default: true
+          max_skew:
+            type: string
+            description: Max future allowance (Go duration format)
+            default: "24h"
+            pattern: "^\\d+[dhms]$"
+            examples:
+              - "24h"
+              - "1h"
+              - "30m"
+              - "5d"
+          severity:
+            type: string
+            description: Severity level for future dates
+            enum: ["critical", "high", "medium", "low", "info", "error"]
+            default: "error"
+          auto_fix:
+            type: boolean
+            description: Auto-replace with today (warn on ambiguity)
+            default: true
+        additionalProperties: false
+      stale_entries:
+        type: object
+        description: Warn on outdated entries (e.g., old changelogs)
+        properties:
+          enabled:
+            type: boolean
+            description: Enable stale entries detection
+            default: true
+          warn_days:
+            type: integer
+            description: Days before warning
+            minimum: 0
+            maximum: 3650
+            default: 180
+          severity:
+            type: string
+            description: Severity level for stale entries
+            enum: ["critical", "high", "medium", "low", "info", "warning"]
+            default: "warning"
+        additionalProperties: false
+      monotonic_order:
+        type: object
+        description: Ensure chronological order (e.g., changelog descending)
+        properties:
+          enabled:
+            type: boolean
+            description: Enable monotonic order checking
+            default: true
+          files:
+            type: array
+            description: Glob patterns for ordering checks
+            items:
+              type: string
+            default: ["CHANGELOG.md"]
+            examples:
+              - ["CHANGELOG.md", "**/HISTORY.md"]
+          severity:
+            type: string
+            description: Severity level for order violations
+            enum: ["critical", "high", "medium", "low", "info", "warning", "error"]
+            default: "warning"
+          check_top_n:
+            type: integer
+            description: Check only the top N entries (0 = check all)
+            minimum: 0
+            default: 0
+          ignore_files:
+            type: array
+            description: Files to ignore for monotonic checks
+            items:
+              type: string
+            default: []
+        additionalProperties: false
+      cross_file_consistency:
+        type: object
+        description: Coherence across files (e.g., dates match versions)
+        properties:
+          enabled:
+            type: boolean
+            description: Enable cross-file consistency checking
+            default: false
+          groups:
+            type: array
+            description: Arrays of files to cross-check
+            items:
+              type: array
+              items:
+                type: string
+            examples:
+              - [["CHANGELOG.md", "package.json"], ["VERSION", "Cargo.toml"]]
+          severity:
+            type: string
+            description: Severity level for consistency violations
+            enum: ["critical", "high", "medium", "low", "info", "error"]
+            default: "error"
+        additionalProperties: false
+    additionalProperties: false
+    required: []
+  files:
+    type: object
+    description: File selection and guards
+    properties:
+      include:
+        type: array
+        description: Globs to include (supports ** via doublestar). Opt-in approach - only specified files are checked.
+        items:
+          type: string
+        default: ["CHANGELOG.md", "**/CHANGELOG*.md", "**/HISTORY.md", "RELEASE_NOTES.md", "**/RELEASE*.md", "**/VERSION"]
+      exclude:
+        type: array
+        description: Globs to exclude (supports **)
+        items:
+          type: string
+        default: ["**/node_modules/**", "**/.git/**", "**/dist/**", "**/build/**"]
+      text_extensions:
+        type: array
+        description: Advisory extensions (binary sniff overrides)
+        items:
+          type: string
+        default: [".md", ".txt", ".yaml", ".yml", ".json", ".toml"]
+      max_file_size_bytes:
+        type: integer
+        description: Skip larger files (prevent OOM)
+        minimum: 0
+        default: 4194304
+    additionalProperties: false
+    required: []
+  date_patterns:
+    type: array
+    description: Order-aware patterns to avoid MM/DD vs DD/MM ambiguity
+    items:
+      type: object
+      properties:
+        regex:
+          type: string
+          description: Regex with 3 capture groups (year, month, day)
+        order:
+          type: string
+          description: Parse order specification
+          enum: ["YMD", "MDY", "DMY"]
+        description:
+          type: string
+          description: Human-readable description of the pattern
+      required: ["regex", "order"]
+      additionalProperties: false
+    default:
+      - regex: "(\\d{4})-(\\d{2})-(\\d{2})"
+        order: "YMD"
+        description: "ISO 8601 Standard"
+      - regex: "(\\d{1,2})/(\\d{1,2})/(\\d{4})"
+        order: "MDY"
+        description: "US Format"
+      - regex: "(\\d{1,2})\\.(\\d{1,2})\\.(\\d{4})"
+        order: "DMY"
+        description: "European Format"
+  timezone:
+    type: string
+    description: IANA TZ for parsing/comparison
+    default: "UTC"
+    examples:
+      - "UTC"
+      - "America/New_York"
+  now:
+    type: ["string", "null"]
+    description: RFC3339 string to override time.Now() (tests only)
+    format: date-time
+    default: null
+  ai_safety:
+    type: object
+    description: AI-specific checks (e.g., hallucinations, placeholders)
+    properties:
+      enabled:
+        type: boolean
+        description: Enable AI safety checks
+        default: true
+      detect_placeholders:
+        type: boolean
+        description: Detect placeholder dates like [DATE], YYYY-MM-DD
+        default: true
+      detect_impossible:
+        type: boolean
+        description: Detect impossible dates like Feb 30, invalid months
+        default: true
+      severity:
+        type: string
+        description: Severity level for AI safety violations
+        enum: ["critical", "high", "medium", "low", "info", "warning"]
+        default: "warning"
+    additionalProperties: false
+    required: []
+  output:
+    type: object
+    description: CLI output control
+    properties:
+      format:
+        type: string
+        description: Output format
+        enum: ["text", "json", "sarif", "markdown"]
+        default: "text"
+      fail_on:
+        type: string
+        description: Exit 1 on severity level
+        enum: ["error", "warning", "any"]
+        default: "error"
+    additionalProperties: false
+    required: []
+additionalProperties: false
+required: []