Add contributor docs, GPL license, and UI fixes

Add project governance and onboarding materials (CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md) and add GPL-3.0 LICENSE. Update README with badges, privacy manifesto and developer setup details. Update .gitignore to ignore test results and log files. Fix runtime/test issues by propagating themeManager via .environmentObject to navigation destinations in CalendarView and InsightsView, and harden SettingsUITests by waiting/scrolling for the Accent Color element to reduce flakiness.

Author: VoxDroid

.gitignore

@@ -52,4 +52,8 @@ Pods/
 ## Git stuff
 .git/
 
+## Test results
 TestResults.xcresult/
+
+## Logs
+*.log

CODE_OF_CONDUCT.md

@@ -0,0 +1,45 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team will maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at https://www.contributor-covenant.org/version/2.1/code_of_conduct.html.
+
+[homepage]: https://www.contributor-covenant.org

CONTRIBUTING.md

@@ -0,0 +1,32 @@
+# Contributing to CycleOne
+
+First off, thank you for considering contributing to CycleOne! It's people like you that make CycleOne such a great tool.
+
+## How Can I Contribute?
+
+### Reporting Bugs
+- Use the **GitHub Issue Tracker**.
+- Describe the bug and steps to reproduce.
+- Include your iOS version and device model.
+
+### Suggesting Enhancements
+- Open an issue to discuss the enhancement first.
+- Explain why this feature would be useful to most users.
+
+### Pull Requests
+1. Fork the repo and create your branch from `main`.
+2. If you've added code that should be tested, add tests.
+3. Ensure the test suite passes (`make check`).
+4. Make sure your code lints (`make format`).
+5. Issue that pull request!
+
+## Coding Standard
+- We follow the [Ray Wenderlich Swift Style Guide](https://github.com/raywenderlich/swift-style-guide).
+- Use `make format` before committing.
+
+## Privacy Policy
+- CycleOne is strictly **local-only**.
+- Any contribution that adds networking, cloud sync, or third-party tracking will be rejected unless there is an extremely compelling, privacy-preserving reason.
+
+---
+By contributing, you agree that your contributions will be licensed under its GPL-3.0 License.

CycleOne/Views/Calendar/CalendarView.swift

@@ -59,6 +59,7 @@ struct CalendarView: View {
                 .navigationBarTitleDisplayMode(.inline)
                 .navigationDestination(for: Date.self) { date in
                     LogView(date: date, context: context)
+                        .environmentObject(themeManager)
                 }
 
                 if !hasSeenOnboarding {

CycleOne/Views/Insights/InsightsView.swift

@@ -122,6 +122,7 @@ struct InsightsView: View {
                         destination: CycleHistoryList(
                             cycles: viewModel.recentCycles
                         )
+                        .environmentObject(themeManager)
                     ) {
                         HStack {
                             Image(

CycleOneUITests/Tests/SettingsUITests.swift

@@ -21,9 +21,20 @@ final class SettingsUITests: XCTestCase {
         XCTAssertTrue(settingsTab.waitForExistence(timeout: 5))
         settingsTab.tap()
 
+        // Wait for list to load
+        _ = settingsTab.waitForExistence(timeout: 2)
+
         // Verify Appearance section and Accent Color picker exist
         let accentColor = app.staticTexts["AccentColorTitle"]
-        if !accentColor.waitForExistence(timeout: 5) {
+
+        // Scroll until visible if needed
+        var retryCount = 0
+        while !accentColor.exists, retryCount < 5 {
+            app.swipeUp()
+            retryCount += 1
+        }
+
+        if !accentColor.waitForExistence(timeout: 10) {
             print("UI Hierarchy: \(app.debugDescription)")
             XCTFail("Expected accent color picker in Settings. Title not found.")
         }