KeiSeiKit-1.0

keisei/KeiSeiKit-1.0

Fork 0

Commit graph

Author	SHA1	Message	Date
Parfii-bot	59fd1a0362	test(substrate): integration now asserts real atom execution via Stream E Previously expected NotImplemented stub (exit 64). Stream E wired real subprocess exec to kei-task, so invoke now actually creates tasks. Updated test: - Builds kei-task in release + passes KEI_RUNTIME_BIN_DIR + KEI_TASK_DB - Asserts exit 0 + stdout has 'id' field - NEW assertion: invoke with empty KEI_RUNTIME_BIN_DIR → exit 127 (BinaryNotFound) - Bad-input assertion stays (InputInvalid → exit 2) 4 end-to-end assertions now cover the full §Runtime contract. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-23 01:23:05 +08:00
Parfii-bot	f7e4725573	fix(substrate): amendment A-1 (input/output required all kinds) + integration test + jsonschema 0.18 relative-$id bug Three post-E1/E2/E3-merge items: 1. Schema amendment A-1 (architect P0-a, non-breaking clarification): input.schema and output.schema are REQUIRED for all atom kinds. The shared kei-atom-discovery parses them as Option<PathBuf> only to allow tolerant skip-on-missing (stderr warn), not to permit absent schemas. Resolves Stream C / Stream D enforcement asymmetry documented in critic finding #6. 2. Cross-stream integration test (architect P0-b): tests/substrate_integration.sh builds release binaries, scaffolds a test atom corpus, runs schema-lint + list-atoms + atoms-discover + invoke; asserts all four streams agree on the same atom corpus and exit codes honour the locked §Runtime contract. Previously missing — only manual smoke checks existed. 3. Fix regression introduced by E1's jsonschema 0.18 upgrade: "relative URL without a base" on compile when schema declared a relative $id like "kei-task/atoms/schemas/create-input.json". validate.rs now synthesises an absolute file:// $id from the canonicalised schema path before compile. Internal $refs still resolve relative to the schema file; LocalFileResolver still confines to the schema's parent dir. Integration test catches this. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-23 00:56:27 +08:00

Author

SHA1

Message

Date

Parfii-bot

59fd1a0362

test(substrate): integration now asserts real atom execution via Stream E

Previously expected NotImplemented stub (exit 64). Stream E wired real
subprocess exec to kei-task, so invoke now actually creates tasks.
Updated test:
- Builds kei-task in release + passes KEI_RUNTIME_BIN_DIR + KEI_TASK_DB
- Asserts exit 0 + stdout has 'id' field
- NEW assertion: invoke with empty KEI_RUNTIME_BIN_DIR → exit 127 (BinaryNotFound)
- Bad-input assertion stays (InputInvalid → exit 2)

4 end-to-end assertions now cover the full §Runtime contract.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-23 01:23:05 +08:00

Parfii-bot

f7e4725573

fix(substrate): amendment A-1 (input/output required all kinds) + integration test + jsonschema 0.18 relative-$id bug

Three post-E1/E2/E3-merge items:

1. Schema amendment A-1 (architect P0-a, non-breaking clarification):
   input.schema and output.schema are REQUIRED for all atom kinds. The
   shared kei-atom-discovery parses them as Option<PathBuf> only to allow
   tolerant skip-on-missing (stderr warn), not to permit absent schemas.
   Resolves Stream C / Stream D enforcement asymmetry documented in
   critic finding #6.

2. Cross-stream integration test (architect P0-b): tests/substrate_integration.sh
   builds release binaries, scaffolds a test atom corpus, runs
   schema-lint + list-atoms + atoms-discover + invoke; asserts all four
   streams agree on the same atom corpus and exit codes honour the
   locked §Runtime contract. Previously missing — only manual smoke
   checks existed.

3. Fix regression introduced by E1's jsonschema 0.18 upgrade:
   "relative URL without a base" on compile when schema declared a
   relative $id like "kei-task/atoms/schemas/create-input.json".
   validate.rs now synthesises an absolute file:// $id from the
   canonicalised schema path before compile. Internal $refs still
   resolve relative to the schema file; LocalFileResolver still confines
   to the schema's parent dir. Integration test catches this.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-23 00:56:27 +08:00

2 commits