Teknium
ef04d846e9
Cron jobs were constructed with skip_memory=True and a hard 'memory' toolset denial, so MEMORY.md/USER.md never loaded and the memory tool was stripped even from per-job enabled_toolsets. That was inconsistent with kanban/delegate/gateway agents (which all get memory) and forced users into hacky bypasses. - cron/scheduler.py: skip_memory=False on the cron AIAgent; drop 'memory' from _resolve_cron_disabled_toolsets; remove _strip_cron_memory_toolset and its call sites - agent/agent_init.py: update stale comment referencing the cron denylist - tests: flip pinning tests to the new contract (memory enabled, per-job memory toolset kept, user-level denylist still wins) - docs: cron-internals + automate-with-cron no longer claim cron has no persistent memory
Website
This website is built using Docusaurus, a modern static website generator.
Installation
yarn
Local Development
yarn start
This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
Build
yarn build
This command generates static content into the build directory and can be served using any static contents hosting service.
Deployment
Using SSH:
USE_SSH=true yarn deploy
Not using SSH:
GIT_USER=<Your GitHub username> yarn deploy
If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the gh-pages branch.
Diagram Linting
CI runs ascii-guard to lint docs for ASCII box diagrams. Use Mermaid (````mermaid`) or plain lists/tables instead of ASCII boxes to avoid CI failures.