AIWF v1.7.13.post1

AIWF v1.7.13.post1

AIWF v1.7.13.post1 fixes the fresh-install payload boundary without changing
the public repository layout or workflow protocol.

Fixed

• Install payload selection is now an explicit AIWF-owned allowlist.
• Public repository contents are not treated as the install payload.
• Repository-level development assets, including tests/, .github/, root
  docs/, knowledge/, release files, CI assets, and review artifacts, are
  excluded from installation.
• Existing target tests/, .github/, and docs/ directories are preserved
  byte-for-byte.
• Install rollback and post-install validation remain enabled.

Compatibility boundary

• AIWF Tool Version: 1.7.13.post1
• Workflow Protocol Version: 1.7.8 (unchanged)
• Public export behavior and public repository layout are unchanged.
• Closure Summary and finalize semantics are unchanged.

Known History

v1.7.13 introduced source-driven installation.
v1.7.13.post1 refines the installation payload boundary to ensure
repository-level development assets are never installed into target
repositories.

AIWF v1.7.13

AIWF v1.7.13

AIWF v1.7.13 improves first-use adoption and closure clarity while preserving
workflow protocol semantics.

Highlights

• Added the source-driven one-step fresh install command:
  /path/to/aiwf-package/aiwf install --target . --yes.
• Added preflight, fail-closed layout detection, package filtering, rollback,
  and post-install validation for fresh installs.
• Added the human-authored Closure Summary to newly generated review_final.md
  artifacts.
• Refreshed the public README, workflow overview, documentation navigation, and
  design-principles language.

Compatibility boundary

• AIWF Tool Version: 1.7.13
• Workflow Protocol Version: 1.7.8 (unchanged)
• Closure Summary is documentation guidance and is not a finalize blocker.
• Finalize semantics, phase transitions, metadata schema, event schema, review
  fix loop, diagnostic semantics, and historical records are unchanged.

AIWF v1.7.12

AIWF v1.7.12

Summary

AIWF v1.7.12 strengthens runtime safety, repository boundaries, read-only
command behavior, migration integrity, backfill idempotency, selector
validation, and diagnostic consistency.

Highlights

• Agents path repository-boundary hardening.
• Relocate and upgrade conflicts fail closed before mutation.
• Read-only task-ID allocation and new-task zero side effects for invalid
  deterministic metadata.
• Backfill source identity, idempotency, and historical-evidence preservation.
• Dataset output repository-boundary enforcement.
• Read-only dry-run and finalize-ready behavior.
• Exact selector and date-range validation.
• Field-specific diagnostics and deterministic input exit-code alignment.

Validation

• 53/53 CLI semantic regression cases passed.
• 463 private-source unit tests passed.
• Formal public export: 74 files, 0 built-in scan findings.

Compatibility

• AIWF Tool Version: 1.7.12
• Workflow Protocol Version: 1.7.8
• No event schema change.
• No manifest schema change.
• No workflow phase semantic change.

AIWF v1.7.11

AIWF v1.7.11

Release Type

Fail-closed task creation identity safety correction.

Fixed

• Made new-task create-only; --update-existing now fails before writing files.
• Rejected same-date duplicate normalized task names before task ID allocation.
• Added AIWF-TASK-NAME-001 diagnostics with exact existing task paths.
• Made check, doctor, and finalize block on pre-existing same-date duplicate names.
• Added focused regression coverage for zero-side-effect failure, cross-date compatibility, and diagnostics.

Compatibility

• Workflow protocol remains 1.7.8.
• Backfill and knowledge-template --update-existing behavior is unchanged.
• No event schema, finalize semantics, phase state machine, locking, repair, or historical-record migration was added.

AIWF v1.7.10.post2

AIWF v1.7.10.post2

Release Type

Packaging / upgrade reliability patch.

Fixed

• Fixed upgrade --apply to install the full .aiwf/bin/** runtime dependency set instead of only .aiwf/bin/ai_workflow.py.
• Fixed upgrade --apply to install .aiwf/templates/**, including AGENTS.block.md.
• Added source package completeness checks for runtime dependencies and managed templates.
• Tightened runtime dependency completeness checks to require .aiwf/bin/lib/package_core.py, not only the .aiwf/bin/lib/ directory.
• Added target dependency completeness checks so same-version but incomplete installations are repaired instead of reported as complete.
• Improved upgrade --dry-run and upgrade --check output so Will update reflects the actual update or repair scope.

Compatibility

• No workflow protocol version change.
• No event schema change.
• No finalize gate change.
• No phase state machine change.
• No records migration.
• Existing .aiwf/records/**, .aiwf/events/**, .aiwf/migrations/**, and .aiwf/config.yaml remain preserved.

Background

This patch was triggered by a ZIP-source upgrade from v1.7.7 to v1.7.10 where the target repository received .aiwf/bin/ai_workflow.py but not its runtime dependencies, causing ModuleNotFoundError: No module named 'safe_paths'.

A second issue showed .aiwf/templates/AGENTS.block.md was also not installed, causing agents check to fail with missing AIWF managed block template.

AIWF v1.7.10

AIWF v1.7.10

Changed

• Added v1.7.10 runtime security hardening release identity.
• Improved README first-time-reader overview.
• Added AIWF overview SVG under .aiwf/docs/images/.
• Repaired README image path to avoid creating or depending on root docs/.
• Clarified AIWF Tool Version vs Workflow Protocol Version.
• Included README images in public export.
• Excluded internal review bundle tests from public export.

Compatibility

• Workflow Protocol Version remains 1.7.8.
• No workflow protocol semantic change.
• No event schema change.
• No finalize semantics change.
• No runtime workflow boundary change from the README update.

Version Boundary

• AIWF Release Version: 1.7.10
• AIWF Tool Version: 1.7.10
• Workflow Protocol Version: 1.7.8

AIWF v1.7.9.post2

Public export hotfix for the v1.7.9 release line.

• Includes .aiwf/bin/lib/package_core.py and .aiwf/bin/lib/init.py in the public release tree so the AIWF runtime can import package records helpers.
• Includes the package records manifest schema required by public CI and runtime validation.
• Keeps private AIWF records, events, knowledge, internal review helpers, and local artifacts out of the public tree.
• No workflow protocol semantics, task state semantics, event schema, finalize behavior, or phase-state-machine behavior changed.
• Existing v1.7.9-post1 tag was not moved.

AIWF v1.7.9.post1

AIWF v1.7.9

Release Type

Package Records evidence portability release.

Added

• Added ./aiwf package records as an optional workflow evidence portability command.
• Supports ZIP and directory package output.
• Includes manifest, inventories, package summary, and integrity metadata.
• Includes selected AIWF workflow records and related workflow evidence.
• Includes task-local and associated global events.
• Integrates dataset export into package records.
• Supports redaction profiles: safe, internal, and none.
• Fails closed on high-confidence secret findings.
• Clarifies package validation semantics:
  • Package Generation
  • Manifest Schema
  • Package Integrity
  • Privacy/Security
  • Workflow Evidence Findings
• Introduces review_agent.md as the canonical agent review artifact for new records.
• Keeps review_codex.md as a backward-compatible legacy alias.

Changed

• Package Records documentation added to README and reporting documentation.
• Upgrade documentation clarifies that Package Records is optional and requires no migration.
• Package Records release preparation documentation records v1.7.9 as the human release decision.

Fixed

• Failed or interrupted task creation now rolls back task directories created by
  the failed command before a valid task exists, preventing empty orphan task
  directories from becoming repository hygiene failures.

Compatibility

This release does not change:

• workflow protocol semantics
• task state semantics
• event schema
• finalize behavior
• phase-state-machine behavior
• historical workflow records

Existing repositories continue to work unchanged.

Notes

package records is not a repository backup, source archive, public release export, or tamper-proof audit ledger.

It is intended for workflow evidence analysis, engineering handoff, review, dogfooding, and post-hoc workflow record inspection.

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 ./aiwf as the stable supported repository-local entrypoint.
• Documented .aiwf/bin/ai_workflow.py as the canonical runtime.
• Clarified that AIWF owns only the root ./aiwf entrypoint and the .aiwf/ namespace.
• Clarified that project-level docs/, tools/, and scripts/ 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 LICENSE to 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_VERSION to 1.7.8.post1.
• Kept WORKFLOW_PROTOCOL_VERSION at 1.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/, or scripts/.
• Existing legacy tools/ai_workflow.py files 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.