fix: reconcile final context evidence and literal BOM fixture

This commit is contained in:
haelyra committed 2026-11-16 13:40:22 -05:00
1 parent bde6925bd3
commit 7da9b1d29c
3 files changed
+4 -3

No files matched your search

@@ -10,7 +10,7 @@
"id": "hand-seeded",
"source": "manual-curation-pending-regeneration"
},
"registryDigest": "f91abbb7c9368eb1e8f1a8bf7e0058502781da36abb072682b7f8f16f540568b",
"registryDigest": "23bd986cff96ea33424b1a461461a70e3194582ce01927145fd3f956daeebf7f",
"schemaVersion": 1,
"triggers": {
"skill:agent-runtime-gateway-smoke-test": [
+2 -1
View File
@@ -1,7 +1,8 @@
'use strict';
// Neighbor skills: skills the host has installed from somewhere other than ECC.
// ECC never loads them and never reads their bodies. Their names and
// ECC never loads their bodies as context or interprets their instructions.
// Discovery reads bounded files to extract frontmatter. Their names and
// descriptions are matched against the task so the ones that also fit can be
// listed as companions next to ECC's own selection, which they never change.
// The host can then use ECC's skill and the user's other skills together. The
+1 -1
View File
@@ -301,7 +301,7 @@ test('discovery tolerates BOMs and skips oversized headers, relative install pat
const home = fs.mkdtempSync(path.join(os.tmpdir(), 'ecc-neighbors-edges-'));
try {
const config = path.join(home, '.claude');
write(config, 'skills/bom/SKILL.md', '---\nname: bom-skill\ndescription: Starts with a byte order mark.\n---\n');
write(config, 'skills/bom/SKILL.md', '\uFEFF---\nname: bom-skill\ndescription: Starts with a byte order mark.\n---\n');
write(config, 'skills/huge/SKILL.md', `---\nname: huge\ndescription: ${'x'.repeat(17 * 1024)}\n---\n`);
const relative = path.join(home, 'cache', 'relative');
const badKey = path.join(home, 'cache', 'bad');