← CompText ContextCONTENT HISTORY

Update to CompText Context

Snapshot Sep 30, 2026 · 23:14 UTC · version 0.1.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "compile-context",
  "description": "Use when the user asks to build, validate, or minimize operational context from explicit required fields, constraints, dependencies, blockers, or recovery paths.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 287
    }
  ],
  "skill_md_contents": "---\nname: compile-context\ndescription: Use when the user asks to build, validate, or minimize operational context from explicit required fields, constraints, dependencies, blockers, or recovery paths.\n---\n\n# Compile operational context\n\nBuild context before loading more source material. Create two bounded JSON files: a source summary with `source_digest` and available `field_paths`, and a contract with the explicit required fields and operational rules.\n\nRun:\n`node \"${CODEX_HOME:-$HOME/.codex}/plugins/cache/comptext-marketplace/comptext-context/0.1.0/scripts/build-context.mjs\" <source-summary.json> <contract.json>`\n\nTreat the single JSON line as the primary context receipt. Do not include raw prompts, source text, secrets, command output, or unrelated repository content in either input.\n\nPreserve semantic `required_order`; sort only set-like fields. If `validation.valid` is false, report the missing required fields instead of pretending the context is sufficient.\n\nReturn `context_id`, strategy, required/satisfied/missing fields, constraints, blockers, recovery paths, validation, and non-claims."
}

SHA-256: 83d4182ee480f0b3d66847b73bb4518ec165f240765e4623d800cc82e7a0601b