diff --git a/.vscode/launch.json b/.vscode/launch.json
index 47a5435c..42e3bc09 100644
--- a/.vscode/launch.json
+++ b/.vscode/launch.json
@@ -44,7 +44,7 @@
         //"AYANOVA_LOG_LEVEL": "Debug",
         "AYANOVA_DEFAULT_TRANSLATION": "en",
         //TRANSLATION MUST BE en for Integration TESTING
-        "AYANOVA_PERMANENTLY_ERASE_DATABASE": "true",
+       // "AYANOVA_PERMANENTLY_ERASE_DATABASE": "true",
         "AYANOVA_DB_CONNECTION": "Server=localhost;Username=postgres;Password=raven;Database=AyaNova;",
         "AYANOVA_USE_URLS": "http://*:7575;",
         "AYANOVA_FOLDER_USER_FILES": "c:\\temp\\RavenTestData\\userfiles",
diff --git a/devdocs/todo.txt b/devdocs/todo.txt
index e4b2bda1..2d1a9d65 100644
--- a/devdocs/todo.txt
+++ b/devdocs/todo.txt
@@ -8,22 +8,6 @@ LICENSE / ONBOARDING
 
 
 
-todo: DBID issue
-	dbid in activekey being shown in ui, but, it should only be used to compare to databases dbid to validate correct license
-	instead, the database dbid should be the only thing shown anywhere unless viewing the key itself directly
-
-
-todo: in paralel on rockfish, add client and server code as per below and trial form to fill out by user
-	Best way to do this is code it through the steps a new user would take starting with a empty db and trial request
-	and work up to a purchase and license
-
-todo: FRESH TRIAL ONBOARD
-	setup dev test so it boots cleanly and creates a db as in a new installation
-	remove magic dbid value so it just has a normal db id as it would in production	
-		Can add back in some kind of automated routine to install license etc when done with onboarding later, for now do it like it will work in practice
-	handle auth and new password as spec'd below
-	add trial view in client as per specs in client todo doc
-	Work it out towards getting a trial key requested, approved, fetched and seeding data
 
 todo: FRESH PURCHASE ONBOARD
 	continue on with the steps required to purchase and use in production
@@ -96,7 +80,7 @@ todo: permanently erase db startup thing, should it really exist?
 todo: could be a presentation issue but erasing the database and "permanently" erasing the db do two different things completely
 	Maybe change the biz object erase to empty or remove all data or something along those lines
 	If it requires too much explanation then it's probably mis-identified as to what it does
-	
+
 todo: docs, change all named references to the Manager / manager / admin / adminstrator account to "SuperUser"
 
 TODO: do I really need to not log IP addresses on login?