<commit_before>SHORTLIST --
	1) test the ryr controller thoroghly 
	2) 	deploy our sandbox version for dad to break
	3) rider view / allow registered to view status, and update
	4) admin/riders can retrieve and update fields for riders

QUESTIONS 
	- do we need defensive user validation at each step of new rider registration ?
		- this could likely be handled by a 'before_action' block in the controller-- verify that rider is current_user

	- can we valid params not saved to db ? 
		- ala credit card number (feel like we should do this )


<!-- admin register new admin -- password conf field
email conf also --><commit_msg>update todos<commit_after>SHORTLIST --
	1) test the ryr controller thoroghly 
	2) 	deploy our sandbox version for dad to break
	3) rider view / allow registered to view status, and update
	4) admin/riders can retrieve and update fields for riders

QUESTIONS 
	- we need tests for the paypal wrapper method




<!-- admin register new admin -- password conf field
email conf also -->
{'fraction_non_alphanumeric': 0.05434782608695652, 'fraction_numerical': 0.007905138339920948, 'mean_word_length': 3.5223214285714284, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4979971', 'n_tokens_mistral': 293, 'n_tokens_neox': 261, 'n_words': 149}