Hermes Agent
ed23524817
Preserve source locations, validate malformed JSON, and add opt-in resource limits. Include executable error-guide coverage, learner pilot materials, native Windows acceptance helpers, and updated CI/documentation.
3.7 KiB
Claro current status
Development version: v2026.10.25.014405
Claro is a learning tool first. The development timestamp identifies source; it does not mean that a release was published or every platform was tested. See release status for dated, artifact-specific evidence.
Beginner core — tested learning path
- Input/output, variables, arithmetic, decisions, loops, lists, simple functions, and text-file save/load have executable lesson/example coverage.
- Teach short
ASKandSET,TEACHwithDO, andENDfor introductory blocks. Older forms remain supported, outside the first lessons. - The first hour, ten lessons, generated starter and introductory examples are checked for behavior, not just syntax.
- The runtime remains one C89 file: src/claro.c.
This is a foundation for learner trials, not proof of accessibility or classroom readiness. Intended learners have not yet validated accessibility; use the classroom pilot checklist to gather that evidence.
Reliability and trust boundary
Maintained checks cover ownership cleanup, malformed expressions, nested blocks, call depth and the learning path under leak-enabled sanitizers. See reliability for scope and testing to reproduce it. Earlier failure logs are history, not current unresolved findings.
Claro runs trusted scripts with the user's permissions. It is not a sandbox. Loops can run indefinitely by default. Opt-in step and READ FILE budgets are available; parsed JSON nesting is capped. Global file/output/memory and CPU-time budgets are not provided. See actual runtime guards.
Platforms — do not confuse compilation with OS acceptance
- Strict GCC C89 and extracted source validation have passed on Linux.
- Linux x86-64 static-musl downloads have been tested on the build host.
- MinGW x64 and MSVC600 x86 executables have been built and tested under Wine.
- The dedicated Windows 98 SE build uses
build98.bat. - Native modern Windows and Windows 98 SE execution remain unverified.
- macOS, ARM, DOS and other untested targets are not implied by C89 compliance.
Exact versions and tested environments are in the release ledger. The portability guide explains the standard archive targets.
Existing optional features versus plans
Types, objects, local projects/packages, HTTP and editor helpers remain available in their reference guides; beginners do not need them. Existing deterministic task helpers are not a claim of native parallel execution or a full scheduler.
Graphics/SDL, a web server, remote registry, richer concurrency and a full editor integration are plans or experiments, not beginner-ready platform promises. They are not active expansion priorities without a separate request.
What is next
- Use the learner pilot kit with a willing person; code checks are not human feedback. Source-located expression diagnostics now have regressions.
- Use the native Windows kit on an authorized target. Wine is explicitly rejected by its OS evidence helper.
- Hosted CI/release delivery needs authenticated Gitea access and enabled Actions. See the six-track status for current blockers.
Follow the small active roadmap. The previous detailed status and hardening log preserve older claims, implementation notes and investigations; they are not current acceptance criteria.