From 49732cab89f24afd91716a0e6c04d38994efc495 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 2 Sep 2026 17:23:58 +0000 Subject: [PATCH] skills(platform): delete the placeholder eval README and drop its ceiling row MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The file was a stub for evals that were never written: it says the directory is "reserved for future skill evaluation tests", that "When implemented, evals will follow this structure", and that it is "Not yet implemented — This is a placeholder for future development". The tree it prints names ten eval files, none of which exists anywhere in the repository. Nothing read the path. Repo-wide, the single reference to skills/objectstack-platform/evals was its own ceiling row in the token ratchet, so the row goes with the file and the package ceiling steps down by 514 tokens. No other row is touched, no ceiling is raised, and no prose changes. Verified before the deletion (the ruling keeps real fixtures, so the directory had to be proven fixture-free): the evals directory held README.md and nothing else, with zero subdirectories. Reverse verification: with the file deleted and the row still present, check-skills-token-ratchet exits 1 with "cannot read skills/objectstack-platform/evals/README.md — red, not a skip (#4690)"; with the row dropped it exits 0 over 30 authored bundle files; --self-test passes 64 cases. Ruled A for item 2 of the eval-stub decision card (#14296): planned-eval stubs are deleted, their ceilings step down, real fixtures stay, no new eval packages. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_01LraLgQVGq8egUwfYZpbYt1 --- scripts/check-skills-token-ratchet.mjs | 1 - skills/objectstack-platform/evals/README.md | 49 --------------------- 2 files changed, 50 deletions(-) delete mode 100644 skills/objectstack-platform/evals/README.md diff --git a/scripts/check-skills-token-ratchet.mjs b/scripts/check-skills-token-ratchet.mjs index f726a13153..b190ac441b 100644 --- a/scripts/check-skills-token-ratchet.mjs +++ b/scripts/check-skills-token-ratchet.mjs @@ -417,7 +417,6 @@ export const CEILINGS = new Map([ ['skills/objectstack-data/rules/validation.md', 3109], // objectstack-platform - ['skills/objectstack-platform/evals/README.md', 514], ['skills/objectstack-platform/references/plugin-hooks.md', 2628], ['skills/objectstack-platform/rules/plugin-lifecycle.md', 2408], ['skills/objectstack-platform/rules/service-registry.md', 2331], diff --git a/skills/objectstack-platform/evals/README.md b/skills/objectstack-platform/evals/README.md deleted file mode 100644 index d332770abc..0000000000 --- a/skills/objectstack-platform/evals/README.md +++ /dev/null @@ -1,49 +0,0 @@ -# Evaluation Tests (evals/) - -This directory is reserved for future skill evaluation tests. - -## Purpose - -Evaluation tests (evals) validate that AI assistants correctly understand and apply the rules defined in this skill when generating code or providing guidance. - -## Structure - -When implemented, evals will follow this structure: - -``` -evals/ -├── bootstrap/ -│ ├── test-definestack-keys.md # no phantom keys (driver:, workflows:, approvals:) -│ ├── test-manifest-required-fields.md -│ └── test-template-selection.md # blank is the whole catalog; the five remote templates are retired -├── drivers-adapters/ -│ ├── test-driver-selection.md # memory / sql / mongodb / sqlite-wasm; turso = cloud/EE -│ └── test-hono-integration.md # @objectstack/hono vs plugin-hono-server; no adapter-* -├── plugins/ -│ ├── test-lifecycle-phases.md # init/start/destroy, dependency order -│ ├── test-service-registry.md # registerService throws on duplicate; no null placeholders -│ └── test-kernel-events.md # kernel:ready/bootstrapped/listening/shutdown; NO data:* events -└── ops/ - ├── test-cli-commands.md # real command surface (no os studio / os data seed / os meta apply) - └── test-litekernel-testing.md # new LiteKernel().use(...) pattern; kernel.context is protected -``` - -## Format - -Each eval file will contain: -1. **Scenario** — Description of the task -2. **Expected Output** — Correct implementation -3. **Common Mistakes** — Incorrect patterns to avoid -4. **Validation Criteria** — How to score the output - -## Status - -⚠️ **Not yet implemented** — This is a placeholder for future development. - -## Contributing - -When adding evals: -1. Each eval should test a single, specific rule or pattern -2. Include both positive (correct) and negative (incorrect) examples -3. Reference the corresponding rule file in `rules/` -4. Use realistic scenarios from actual ObjectStack projects