AIWF v1.7.8.post1
AIWF v1.7.8.post1
Release Type
Public repository baseline and release identity patch.
Summary
AIWF v1.7.8.post1 prepares the public source tree for external validation and adoption.
The release keeps workflow protocol semantics at 1.7.8 while updating tool provenance and public documentation to 1.7.8.post1.
Included
- Added Apache License 2.0 text in root
LICENSE. - Added public license wording in
README.md. - Documented
./aiwfas the stable supported repository-local entrypoint. - Documented
.aiwf/bin/ai_workflow.pyas the canonical runtime. - Clarified that AIWF owns only the root
./aiwfentrypoint and the.aiwf/namespace. - Clarified that project-level
docs/,tools/, andscripts/are project-owned and are not required, copied, moved, deleted, or rewritten during normal public AIWF installation and upgrade. - Legacy root
docs/migration remains available only through explicit opt-in after the user reviews path ownership. - Clarified that legacy project-level
tools/ai_workflow.py, when present in older repositories, is preserved unchanged and may be removed manually after confirming no external caller depends on it. - Added
LICENSEto the deterministic public tree exporter allowlist. - Included
.github/workflows/in the public tree so GitHub-hosted CI validates the clean public source tree. - Bumped
AIWF_TOOL_VERSIONto1.7.8.post1. - Kept
WORKFLOW_PROTOCOL_VERSIONat1.7.8.
Public Validation Baseline
The public tree is allowlist-based and excludes private workflow records, global events, knowledge analysis, datasets, private CI metadata, package metadata, internal review helpers, and private Git history.
GitHub Actions validates the clean public tree with:
- Python
3.10 - Python
3.11 - Python
3.12 - runtime compile
- full unit tests
- tracked-files-only fresh public copy
- public boundary checks
- fresh-tree AIWF smoke commands
Compatibility
- No workflow protocol semantic change.
- No task front matter schema change.
- No event schema change.
- No finalize semantic change.
- No automatic migration of project-level
docs/,tools/, orscripts/. - Existing legacy
tools/ai_workflow.pyfiles remain project-owned and are preserved.
Upgrade Notes
Use ./aiwf as the supported entrypoint.
The canonical runtime is .aiwf/bin/ai_workflow.py.
For older repositories that still contain a project-level tools/ai_workflow.py, do not treat that file as the public entrypoint.
Keep it if external callers still depend on it, or remove it manually after confirming it is unused.
Boundary
This is a public release identity and documentation patch in the v1.7.8 protocol family.
It does not introduce v1.8 workflow semantics.