Name: [DOC] roadmap + migration: reconcile with the relocated code

State: Killed

PR State: merged

PR Author: David Tran

PR Author Email:

PR: #109

Committer: David Tran

Committer Email: davidtran.hp@gmail.com

Commit: b20fe85599a22860071ba14549b0897fec9a2785

Description:

                                            [DOC] roadmap + migration: reconcile with the relocated code

The 50 AI/Brain modules now live in Viindoo/tvtmaaddons (47) and
Viindoo/erponline-enterprise (3). Reading both repos back against this
roadmap turned up two claims that were not true of the code, plus six
counts or references that had drifted.

Corrected, each on the evidence it rests on:

- M7-4 goes back to [ ]. The ADR-029 decision stands, but the execution
  never landed: viin_ai_chatbot on odoo-tvtma17's 17.0 HEAD is still
  version 1.0.1, carries only migrations/16.0.1.0.1/, and holds zero
  references to viin_ai_livechat. The planned 1.0.2 bump and
  migrations/17.0.1.0.2/ do not exist. migration.md described the same
  work as already done and now reads as the design it is.
- M7-5 claimed the asset gate asserts an AI bundle under 500KB gzip. No
  such assertion exists in that test or anywhere else; only the
  viin_brain 450KB budget is real, so the AI-side bundle is ungated.
- be53a191 is not a commit in any repo. The fix it credits is cdfd038519.
- The skill catalogue splits 72 kw-* / 41 viin-*, not 62 / 51. The
  totals 113/13 and 115/14 were right.
- SQL templates total 35 today; 23 was the last figure ever recorded.
- Eight work routines ship, not seven. routine_dunning_weekly is named
  elsewhere in the doc but was never added to the tally.
- Four line references in 2A W3.2 had slid 1-3 lines; symbols unchanged.
- Wave 4 covers 46 icon files of which only 39 are byte-distinct - five
  viin_brain_* modules share one identical file.

Add 9.1, which records a rule that fell on the floor during the move.
Commit 4bbdabb6bc dropped every migration script and pinned each module
to 1.0.0 because the ai17 repo had no deployment to protect, and made
its own removal conditional on that changing. The rule lived in
ai17/AGENTS.md 0.1, and merge 8d238c74 states plainly that repo-level
files stayed behind. Neither destination repo carries it; neither has an
AGENTS.md at all.

Bare 1.0.0 turns out to be the house style there - 126 sibling modules
use bare manifest versions with series-prefixed migration dirs - so
nothing needs renumbering. What is missing is the migrations. No
back-migration is owed either: no tag, no customer repo and no SaaS
config shows any of these modules installed anywhere. That is absence of
evidence rather than proof, and 9.1 says so. The invariant bites at the
next schema change, and ADR-031's translate=True is the first one due.
Where to write the rule down in a shared repo is left to the owner.

Also flag the audio capability as declared but dead: provider_google_gemini
and vendor_google both seed it while call_transcription is a bare
NotImplementedError, so the UI advertises what a call would fail on.
                                            

Branch: 17.0

Instance ID: 0

Age:

Up-time: Not finished