Exclude tests directory from framework publish

Add 100+ automated unit tests from .expect file specifications
Add session system test
Add rsx:constants:regenerate command test
Add rsx:logrotate command test
Add rsx:clean command test
Add rsx:manifest:stats command test
Add model enum system test
Add model mass assignment prevention test
Add rsx:check command test
Add migrate:status command test

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

app/RSpade/man/expect_files.txt

@@ -138,6 +138,50 @@ Use TODO: prefix for planned functionality that doesn't exist yet:
 TODO expectations document future requirements without implying the feature
 exists. The test runner will skip these until converted to EXPECT blocks.
 
+CHANGE TIMESTAMPS
+
+All additions and modifications to .expect files must include a timestamp
+to track when expectations were documented. This creates a timeline of
+behavioral requirements as the codebase evolves.
+
+Format: # Added: YYYY-MM-DD or # Modified: YYYY-MM-DD
+
+Place timestamp as the last line within an expectation block:
+
+    EXPECT: Parse ISO 8601 with milliseconds
+    GIVEN: String "2024-12-24T15:30:45.123Z"
+    WHEN: Passed to parse()
+    THEN: Returns Carbon instance with millisecond precision
+    # Added: 2024-12-24
+    ---
+
+When modifying an existing expectation, add the modification date:
+
+    EXPECT: Parse ISO 8601 with milliseconds
+    GIVEN: String "2024-12-24T15:30:45.123Z"
+    WHEN: Passed to parse()
+    THEN: Returns Carbon instance with millisecond precision
+    # Added: 2024-12-24
+    # Modified: 2024-12-26 - Changed from DateTime to Carbon
+    ---
+
+For file-level metadata, use a header comment:
+
+    # Rsx_Time.php.expect
+    # Created: 2024-12-24
+    # Last modified: 2024-12-26
+
+    ## Parsing
+
+    EXPECT: Parse ISO 8601 format
+    ...
+
+This timeline helps:
+- Track when specific behaviors were defined
+- Identify recently added/changed expectations during code review
+- Correlate behavioral expectations with git commits
+- Understand the evolution of requirements over time
+
 COMMENTS AND NOTES
 
 Expect files can include freeform comments and explanations. These help