We don't believe in "Ask ASM to deploy the stack." Ambiguity is the enemy of automation. Scripts are code. Code is precise. We won't paper over that with a chat bot.
This is forensic-grade automation debugging. No more "it worked on my machine." You can reproduce the exact execution context from three months ago, down to the pip package versions. I won't lie to you. Upgrading from 6.x to 7.0 is not a apt-get upgrade .
This eliminates the "runaway script" problem. No more accidental rm -rf on production because of a stale environment variable. The script must declare its intent. ASM 7.0 enforces it. We heard your frustration. "Why do I need a separate FastAPI app to trigger my maintenance script?" Anu Script Manager 7.0
Anu Script Manager 7.0 is our statement that automation should be seen, not hidden. docker pull anuscript/manager:7.0-beta
The problem wasn't concurrency. It wasn't the UI. It was context . We don't believe in "Ask ASM to deploy the stack
The internal database schema changed. The plugin API is deprecated (replaced by the contract system). And the scheduler state is not backward-compatible.
But once you're on 7.0, you'll wonder how you tolerated the amnesia of 6.x. We deliberately excluded two "obvious" features: We won't paper over that with a chat bot
— The Anu Core Team We open-sourced the Stateful Execution Graph prototype. [Link to GitHub.]. Contribute, critique, or just stare at the complexity. All feedback welcome.