Skip to content

Release v8.3.0: Rigorous Euclid#142

Closed
nullhack wants to merge 4 commits intomainfrom
chore/release-v8.3.0
Closed

Release v8.3.0: Rigorous Euclid#142
nullhack wants to merge 4 commits intomainfrom
chore/release-v8.3.0

Conversation

@nullhack
Copy link
Copy Markdown
Owner

@nullhack nullhack commented May 6, 2026

Summary

Merges release/v8.3.0 into main — README rewrite, FAQ section, tagline/branding sync, flowr 1.0.0 upgrade, lint fix.

Added

  • README FAQ section: Five questions covering Kiro, Cursor/Copilot, Claude Code/opencode, tool compatibility, and non-software workflows
  • README "Who is this for" rewrite: Refocused around vibe coding, agentic engineering, and spec-driven development
  • agents-smith quick start: One-command adoption for existing projects
  • Workflow flexibility paragraph: Flows are not hardcoded; any state machine process fits

Changed

  • Tagline: "production-ready Python, without the ceremony" → "Spec-driven agent orchestration. Any workflow. Any LLM. Zero lock-in."
  • Branding sync: docs/branding/branding.md tagline updated
  • flowr 1.0.0: Upgraded from >=0.5 to >=1.0.0, knowledge files synced to v1.0.0 spec
  • ~= operator removed, when forms documented, conformance levels added, validation streamlined

Fixed

  • Line length lint in generate-flowviz-data.py

nullhack added 4 commits May 6, 2026 12:00
…anup

Release v8.2.1 (Rigorous Euclid): AI writing marker taxonomy knowledge file (6-tier, evidence-based), repo-wide em dash cleanup (~930 replacements across ~120 files), Tier 1/2/6 AI marker word fixes (leveraging, ensures, significantly, paramount), flowr 1.0.0 specification adoption (~= operator removed, when forms, conformance levels, reserved keys registry), 5 AI research notes, research file for flowr 1.0.0 spec.
@nullhack
Copy link
Copy Markdown
Owner Author

nullhack commented May 6, 2026

Closing duplicate — PR #141 already covers this release.

@nullhack nullhack closed this May 6, 2026
@nullhack nullhack deleted the chore/release-v8.3.0 branch May 6, 2026 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant