Emi Matchu e3d196fe87 Revert modeling refactors to the old modeling that worked! ... Because we ended up with such a big error, and it doesn't have an easy fix, I'm wrapping up today by reverting the entire set of refactors we've done lately, so modeling in production can continue while we improve this code further over time. I generated this commit by hand-picking the refactor-y commits recently, running `git revert --no-commit <hash>` in reverse order, then manually updating `pet_spec.rb` to reflect the state of the code: passing the most important behavioral tests, but no longer passing one of the kinds of annoyances I *did* fix in the new code. ```shell git revert --no-commit 48c1a58df9 git revert --no-commit 42e7eabdd8 git revert --no-commit d82c7f817a git revert --no-commit 5264947608 git revert --no-commit 90407403ba git revert --no-commit 242b85470d git revert --no-commit 9eaee4a2d4 git revert --no-commit 52ca41dbff git revert --no-commit c03e7446e3 git revert --no-commit f81415d327 git revert --no-commit 13ceec8fcc ```		2024-11-06 14:31:16 -08:00
..
development.rb	Revert modeling refactors to the old modeling that worked!	2024-11-06 14:31:16 -08:00
production.rb	Revert modeling refactors to the old modeling that worked!	2024-11-06 14:31:16 -08:00
remote_development.rb	handle contribution for now-unused swf	2010-11-15 16:44:57 -05:00
test.rb	Revert modeling refactors to the old modeling that worked!	2024-11-06 14:31:16 -08:00