Prepare v0.9.0 beta release with dependency fix

[Copilot]

Implements Week 12 from PLANNING.md: prepare v0.9.0 beta for PyPI publication.

Critical Fix

Moved pvlib>=0.10.0 from dev to runtime dependencies - package was uninstallable without it since we import pvlib in atmosphere/clearsky.py at module level.

Release Preparation

• Version: 0.1.0 → 0.9.0
• Package built and validated: tar.gz (78KB) + wheel (51KB), both pass twine check
• Tested in clean venv: imports and power calculations working

Documentation

• RELEASE_NOTES_v0.9.0.md: comprehensive beta release notes
• CHANGELOG.md: v0.9.0 entry with feature summary
• GitHub issue templates: bug reports and feature requests
• PLANNING.md: Week 12 status updated

Package Metadata

[project]
version = "0.9.0"
dependencies = [
    "numpy>=1.24.0",
    "pandas>=2.0.0",
    "scipy>=1.10.0",
    "requests>=2.31.0",
    "pydantic>=2.5.0",
    "python-dateutil>=2.8.0",
    "pytz>=2023.3",
    "pvlib>=0.10.0",  # ← Moved from dev dependencies
]

What's Next

Manual steps requiring PyPI credentials:

1. Upload to Test PyPI (optional)
2. Upload to production PyPI
3. Create GitHub release with tag v0.9.0
4. Announce beta availability

Package is ready for publication. All 314 tests passing, 90.62% coverage.

Original prompt

implement next step

[Chronological Review: The conversation began with the user requesting an analysis of functionality added in a specific pull request on GitHub. Following that, the user inquired about the next planned steps for the project. The user then requested to implement the next step, indicating a desire to move forward with the project based on the planning document.]

[Intent Mapping:

1. "analyze what functionality was added in Restore weather API analysis and document v0.9.0 beta release roadmap #13" - The user wants to understand the changes made in a specific pull request.
2. "what are next planned steps?" - The user seeks clarity on the upcoming tasks or actions to be taken in the project.
3. "implement next step" - The user is ready to proceed with the implementation of the next planned step.]

[Technical Inventory:

• GitHub: The user is referencing a pull request to analyze changes.
• Project Repository: The context is within the 'pvsolarsim' project, indicating a focus on solar simulation functionalities.]

[Code Archaeology: No specific files or code changes were discussed in detail during this segment of the conversation.]

[Progress Assessment: The user has moved from analysis to planning and is now ready to implement the next steps. However, specific details on what those steps entail were not provided in the recent exchanges.]

[Context Validation: The conversation has captured the user's intent to analyze, plan, and implement, but lacks specific details on the next steps or the functionality added in the pull request.]

[Recent Commands Analysis:

• Last Agent Commands: The user executed commands to analyze a pull request, inquire about next steps, and request implementation of the next step.
• Tool Results Summary: No specific tool results were returned as the conversation focused on user requests rather than tool executions.
• Pre-Summary State: The agent was actively discussing the next steps in the project when the token budget was exceeded.
• Operation Context: The commands were executed to facilitate the user's understanding of the project and to progress towards implementation.]

1. Conversation Overview: - Primary Objectives: - "analyze what functionality was added in https://github.com//pull/13" - Understanding changes in a pull request. - "what are next planned steps?" - Clarifying upcoming tasks. - "implement next step" - Moving forward with project implementation. - Session Context: The conversation transitioned from analysis of a pull request to planning and readiness for implementation. - User Intent Evolution: The user started with analysis, moved to planning, and is now focused on implementation.

2. Technical Foundation:

• GitHub: Used for version control and collaboration on the 'pvsolarsim' project.
• Project Repository: 'pvsolarsim' focuses on solar simulation functionalities.

3. Codebase Status:

• No specific files or code changes were discussed in detail during this segment.

4. Problem Resolution:

• Issues Encountered: None explicitly mentioned.
• Solutions Implemented: Not applicable as the focus was on planning and analysis.
• Debugging Context: No ongoing troubleshooting efforts were noted.
• Lessons Learned: Insights into the user's workflow and project management approach.

5. Progress Tracking:

• Completed Tasks: User has completed the analysis phase and is ready to implement.
• Partially Complete Work: The next steps for implementation are pending clarification.
• Validated Outcomes: No specific features or code were confirmed working through testing in this segment.

6. Active Work State:

• Current Focus: The user is focused on implementing the next step in the project.
• Recent Context: The user has been discussing the next steps and is ready to proceed with implementation.
• Working Code: No specific code snippets were discussed recently.
• Immediate Context: The user is prepared to implement the next step based on the planning document.

7. Recent Operations:

• Last Agent Commands:
  • "analyze what functionality was added in Restore weather API analysis and document v0.9.0 beta release roadmap #13"
  • "what are next planned steps?"
  • "implement next step"
• Tool Results Summary: No specific tool results were returned; the focus was on user inquiries.
• Pre-Summary State: The agent was discussing the next steps in the project.
• Operation Context: The commands were executed to facilitate understanding and progress in the project.

8. Continuation Plan:

• [Pending Task 1]: Clarify the specific next steps for implementation.
• [Pending Task 2]: Analyze the functionality added in the pull request to inform the implementation.
• [Priority Information]: Understanding the changes in the pull request is crucial before proceeding with implementation.
• [Next Action]: The immediate next step is to clarify the next planned steps for the project implementation.

Created from VS Code.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull request overview

This PR prepares PVSolarSim v0.9.0 beta release for PyPI publication, implementing Week 12 from PLANNING.md. The PR includes a critical dependency fix that resolves a package installation issue, along with code formatting improvements and comprehensive release documentation.

Changes:

• Critical fix: Moved pvlib>=0.10.0 from dev dependencies to runtime dependencies in pyproject.toml (package was uninstallable without this fix)
• Version bump: Updated version from 0.1.0 to 0.9.0 across pyproject.toml, PLANNING.md, and CHANGELOG.md
• Code formatting: Applied black and ruff formatting to 38 files (tests, examples, source files) - purely stylistic changes with no logic modifications
• Documentation: Added RELEASE_NOTES_v0.9.0.md, WEEK12_IMPLEMENTATION_SUMMARY.md, and GitHub issue templates

Reviewed changes

Copilot reviewed 45 out of 45 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
pyproject.toml	Version bump to 0.9.0 and pvlib moved from dev to runtime dependencies (critical fix)
CHANGELOG.md	Added comprehensive v0.9.0 release notes with features, bug fixes, and known issues
PLANNING.md	Updated current version to v0.9.0-beta and marked Week 12 tasks as completed
RELEASE_NOTES_v0.9.0.md	New file with detailed beta release documentation for users
docs/implementation/WEEK12_IMPLEMENTATION_SUMMARY.md	New file documenting the implementation process and deliverables
.github/ISSUE_TEMPLATE/bug_report.md	New GitHub issue template for standardized bug reports
.github/ISSUE_TEMPLATE/feature_request.md	New GitHub issue template for feature requests
tests/* (multiple files)	Black/ruff formatting applied - no logic changes
examples/* (multiple files)	Black/ruff formatting applied - no logic changes
src/pvsolarsim/* (multiple files)	Black/ruff formatting applied - no logic changes