Skip to content

Release V0.20.0

Choose a tag to compare

@Sistema2D Sistema2D released this 28 Sep 13:29
46256d7

FrameCode VibeWork V0.20.0

Compatibility: minor, migration_required. Content baseline 438c477bf3ee88c4330520f18b82926ba27e5031; ready revision 46256d71d3c5dbd94a5f139cb3bf71292ec1419f.

Summary

V0.20.0 delivers phases 1 to 3 of the maintainer backlog. It absorbs V0.19.1, which was prepared but never published.

  • Integrity:
    • The upgrade never overwrites unverifiable local edits.
    • Validator loopholes are closed.
    • Project-profile edits no longer load the framework policy route.
  • Reduction:
    • The installed payload goes from 273 to 103 files and from 1,457 to 1,019 KB.
    • One PROJECT.md replaces seven profiles.
    • Overlapping policies, templates and skills are merged.
    • The plan queue and document reachability are derived, not versioned.
    • The inactive adaptive and loop experiment layer is removed.
    • Framework history no longer ships in the package.
  • Triggers:
    • A file path only implies facts, such as file operations and framework surfaces.
    • Application changes declare their semantic events, and routing warns when they don't.
    • Discovery uses exact matches.
    • ADRs are validated.
    • Each skill states "use when / do not use when" in its description.

Added

  • upgrade_fcvw.py --prune for unmodified files dropped upstream.
  • Routes-only mode in retrieve_context.py.
  • The adr-schema, clean-scaffold-directory, profile-legacy and plan-queue-legacy rules.
  • A frozen rule inventory, a surface budget and a template-envelope uniqueness test.
  • ADR-0010, ADR-0011 and ADR-0012.

Changed

  • Consolidated policies: AUTOMATION.md, RELEASE.md, INSTANTIATION.md, AI.md, OWNERSHIP.md, PLANNING.md and wiki/README.md.
  • Merged skills: governance-validator 2.0.0 and wiki-curator 2.0.0.
  • SCHEMAS.md now lists versioned artifacts only.
  • A trivial prose fix no longer needs a plan.

Removed

  • The legacy project profiles, DOCUMENT_GRAPH.md, QUEUE.md/queue.d, README-only directories, wiki/templates/, refactoring-guide/, examples/ and the retired CI contract.
  • The adaptive/loop tools and their flags.

Migration

Follow the "V0.19.0 to V0.20.0" section of FCVW/MIGRATIONS.md.

  1. Run the new release's upgrade_fcvw.py as a dry run first, then with --apply --prune.
  2. Merge the legacy profiles into PROJECT.md by hand.
  3. Update the links in wiki/index.md.
  4. Move the queue fields into the plans' frontmatter.

A rehearsal on a V0.19.0 installation kept every project-owned file byte-identical.

Validation

  • check_fcvw.py passes on Linux with Python 3.10 to 3.13: tests, governance, benchmark and installed smoke.
  • locale_fcvw.py --require-complete finds 0 findings across the four variants.
  • Each ZIP passes installed-payload verification with 280 tests.
  • A second build reproduced identical checksums.

Known gaps

  • Windows and macOS were not exercised.
  • Language variants have AI-assisted review only; no native-speaker review is claimed.
  • In-page link anchors keep source identifiers.
  • Translation aliases still live in the validator.

Rollback

Reinstall the V0.19.0 assets. Project profiles and records are preserved by the upgrade.

Assets

FrameCode-VibeWork-V0.20.0-pt-BR.zip, -en-US.zip, -es.zip, -de.zip and SHA256SUMS.txt.