diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index 72cbddee..04c3d042 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -2,73 +2,6 @@
 @@@@@@@@@@@@@@@ ROADMAP STAGE 4 - REPORTING / DASHBOARD / KPI
 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
 
-bugbug: menu won't drop down top right when running ayanova from a local win64 server build
-	started happening in build alpha 25, didn't happen before that so not related to the .net update, more likely something to do with the pwa changes made recently
-	I've actually seen this briefly multiple times during development and it goes away with a refresh IIRC
-	
-	TRY:
-		first TRY does it happen when I run it from localhost development server with remote client or just the windows build server?
-			YES!!!!
-		
-		Try the "whitelisted modules" fix: https://github.com/vuetifyjs/vuetify/issues/5518
-			nope
-		try updating all client bits again
-		something around this? https://vuetifyjs.com/en/features/treeshaking/#vuetify-loader
-		Put a dummy dropdown menu in the toolbar beside the notification icon to rule out my complex menu building code in app.vue
-		Try vue devtools to inspect it from here on Joyce's server to see if anything is visibly related
-		
-		Try putting a development build of client on local server then load and see if it still an issue
-		TRY Can use v7 laptop to use dev tools to investigate on my own computer or vice-versa
-		TRY revert all recent changes one by one until hit on the culprit
-		fuck it would have been nice to have an old w64 build around to test directly, maybe keep them in sequnce for a while
-	NOT 
-		a manifest pwa related issue because I'm seeing it direct browsing from desktop browser, not app version
-			holup, not sure what this means, it seems to be not true
-
-	ISSUE
-		Turns out it's because it's not https secure connection
-		browsers will trust localhost but not aything else
-		serviceworkers will not work on a non secure, non localhost connection
-			HOWEVER, it appears now that sw has nothing to do with this at all and it's something else
-
-	NO RESOLUTION YET
-		Some kind of certificate faking locally on private network server 
-		adapt the client to not use a service worker on a private network (bypass pwa stuff)
-		
-		OUTDATED (doesn't appear it's a pwa issue at all):
-			Don't use pwa at all or have an optional build of it:
-			https://github.com/vuejs/vue-cli/issues/3830
-			https://stackoverflow.com/questions/52800904/disable-pwa-plugin-in-vue-cli-3
-	
-	#### CHANGES BETWEEN WORKING (commit 5712 Raven alpha-21 (you sent me link Sept 24 10:10am)) AND FAIL (commit 5739 last) Raven alpha-25 (you sent me link Sept 29 11:11am)
-		manifest starturl changed from  "start_url": "./index.html", to   "start_url": "/",
-		added logo adn footer move code
-		remove wipe data on change of client version in app.vue code (commented out)
-		set build to report
-		5725 added service worker stuff, modified original sw stuff in registerServiceWorker
-			app.vue added listener for swUpdated event, could be something there
-			commented out original wipe data on client update code here
-			added pwa block to vue.config.js under transpiledependencies
-			added sw.jw
-		TRY: reversing 5725 by commenting out
-		
-		TRIED build 33: app.vue comment out "swUpdated" event listener in created
-			FIXED!!!!! WTF? Actually I commented out two lines and it wasn't the swUpdated one at all it was the next one...
-
-		Tried build 38: comment out navigator.serviceWorker.addEventListener("controllerchange", () => { line in app.vue
-			FIXED, did not comment ou the other line
-			This is an alternative to the controllerchange in the app.vue approach:
-				https://levelup.gitconnected.com/vue-pwa-example-298a8ea953c9
-
-		TRIED build 31: manifest starturl reversal
-			Revert starturl back in manifest.json build 31
-			did not fix, reverted back
-		TRIED build 32: updateexists is still set to true in app.vue by default when it was set that way for testing only!
-			set to false build 32
-			NOT fixed, not reverting back since it's supposed to be that way
-		TRY: made showrefreshui async in 5727
-	
-
 
 
 BUGBUG: decimal control displays blank even when value comes from server.  It's ok when you manually enter but reverts to blank even though the value is there on open