@caddis/cli 0.2.6 → 0.4.0

package/bundles/codex/.codex/skills/testing/tdd-workflow/SKILL.md

@@ -0,0 +1,188 @@
+---
+name: tdd-workflow
+description: "Test-Driven Development workflow — red-green-refactor cycle"
+---
+
+# TDD Workflow
+
+Test-Driven Development using the red-green-refactor cycle. Write tests first, implement minimum code to pass, then refactor with confidence.
+
+## When to Use
+
+- Writing new features or functionality
+- Fixing bugs (write a test that reproduces it first)
+- Refactoring existing code
+- Adding API endpoints or service methods
+
+## Phase 1: PLAN Tests
+
+Map test cases before writing code. For each feature, identify:
+
+1. **Happy path** — expected successful behavior
+2. **Edge cases** — empty input, boundary values, None/null
+3. **Error cases** — invalid input, missing resources, timeouts
+
+```
+Feature: Shorten URL
+  - Happy: valid URL returns short code
+  - Happy: same URL returns same code (idempotent)
+  - Edge: very long URL (2048+ chars)
+  - Error: invalid URL format
+  - Error: empty string
+```
+
+## Phase 2: WRITE Failing Test (Red)
+
+Write one test at a time. It must fail — this proves it tests something real.
+
+```python
+import pytest
+from myapp.shortener import shorten_url
+
+class TestShortenURL:
+    def test_returns_short_code_for_valid_url(self):
+        result = shorten_url("https://example.com/long/path")
+        assert result is not None
+        assert len(result) == 8
+
+    def test_same_url_returns_same_code(self):
+        code1 = shorten_url("https://example.com")
+        code2 = shorten_url("https://example.com")
+        assert code1 == code2
+
+    def test_rejects_invalid_url(self):
+        with pytest.raises(ValueError, match="Invalid URL"):
+            shorten_url("not-a-url")
+
+    @pytest.mark.parametrize("bad_input", ["", "ftp://wrong", None])
+    def test_rejects_bad_inputs(self, bad_input):
+        with pytest.raises(ValueError):
+            shorten_url(bad_input)
+```
+
+Run and confirm failure:
+
+```bash
+pytest tests/test_shortener.py -v
+# Expected: FAILED (module or assertions fail)
+```
+
+## Phase 3: IMPLEMENT Minimum Code (Green)
+
+Write the simplest code that makes the failing test pass. No extras, no optimization.
+
+```python
+import hashlib, re
+
+_store: dict[str, str] = {}
+
+def shorten_url(url: str) -> str:
+    if not url or not re.match(r"https?://\S+", url):
+        raise ValueError("Invalid URL")
+    code = hashlib.sha256(url.encode()).hexdigest()[:8]
+    _store[code] = url
+    return code
+```
+
+Run and confirm green:
+
+```bash
+pytest tests/test_shortener.py -v
+# Expected: PASSED
+```
+
+## Phase 4: REFACTOR
+
+Improve code quality while keeping all tests green.
+
+**Production code:** extract helpers, improve naming, add type hints, remove duplication.
+
+**Test code:** extract fixtures, use `conftest.py`:
+
+```python
+# tests/conftest.py
+import pytest
+
+@pytest.fixture(autouse=True)
+def reset_store():
+    from myapp.shortener import _store
+    _store.clear()
+```
+
+Run after refactoring — still green:
+
+```bash
+pytest tests/test_shortener.py -v
+```
+
+## Phase 5: VERIFY Coverage
+
+```bash
+pip install pytest-cov
+pytest --cov=myapp --cov-report=term-missing tests/
+```
+
+Enforce in CI:
+
+```ini
+# pyproject.toml
+[tool.pytest.ini_options]
+addopts = "--cov=myapp --cov-fail-under=80"
+```
+
+Look at the `Missing` column for untested lines. Common gaps: exception handlers, fallback branches, cleanup code.
+
+## Testing Patterns
+
+### Mocking External Dependencies
+
+```python
+from unittest.mock import patch, MagicMock
+
+def test_fetches_remote_data():
+    mock_resp = MagicMock()
+    mock_resp.json.return_value = {"status": "ok"}
+    mock_resp.status_code = 200
+    with patch("myapp.client.requests.get", return_value=mock_resp):
+        result = fetch_data("https://api.example.com/data")
+        assert result == {"status": "ok"}
+```
+
+### Database Tests
+
+```python
+@pytest.fixture
+def db_session():
+    engine = create_engine("sqlite:///:memory:")
+    Base.metadata.create_all(engine)
+    session = Session(engine)
+    yield session
+    session.close()
+
+def test_creates_user(db_session):
+    user = User(name="Alice", email="alice@test.com")
+    db_session.add(user)
+    db_session.commit()
+    assert db_session.query(User).count() == 1
+```
+
+## Common Mistakes
+
+| Mistake | Fix |
+|---------|-----|
+| Testing internal state (`obj._count`) | Test observable behavior (`obj.get_value()`) |
+| Tests depend on each other | Each test sets up its own data |
+| No assertions in test | Every test must assert something |
+| Testing implementation details | Test what users/callers see |
+
+## Quick Reference
+
+```bash
+pytest                                    # Run all tests
+pytest tests/test_x.py -v                 # Run specific file, verbose
+pytest tests/test_x.py::TestClass::test_y # Run single test
+pytest --cov=myapp --cov-report=term-missing  # Coverage
+pytest -x                                 # Stop at first failure
+pytest --lf                               # Re-run last failures
+ptw -- --cov=myapp                        # Watch mode (pytest-watch)
+```

package/bundles/codex/.codex/skills/testing/test-strategy/SKILL.md

@@ -0,0 +1,155 @@
+---
+name: test-strategy
+context: fork
+description: Test planning and strategy for projects of any size. Use when defining what to test, choosing test types, setting coverage goals, building test pyramids, or planning quality gates. Produces TEST-STRATEGY.md with prioritized test plan. Routes to Tester agent for execution.
+---
+
+# Test Strategy Skill
+
+Define what to test, at what level, and why — before writing a single test. Strategy first, implementation second.
+
+## 1. When to Apply This Skill
+
+**Trigger conditions:**
+- "What should we test?"
+- "Create a test plan for this feature"
+- "We need a testing strategy"
+- New project or major feature without existing test coverage
+- Before a Tester agent handoff where scope is unclear
+
+**Do not skip strategy** — writing tests without a plan leads to low-value tests that cover the wrong things.
+
+## 2. The Test Pyramid
+
+Map every test to the right level. Cost increases as you go up.
+
+```
+          ┌──────────┐
+          │   E2E    │  ← Fewest: critical user journeys only
+          │ (Slow)   │     5-10% of total tests
+         ─┼──────────┼─
+         │Integration │  ← Middle: API contracts, DB queries, service boundaries
+         │ (Medium)   │     20-30% of total tests
+        ─┼────────────┼─
+        │    Unit      │  ← Most: pure functions, business logic, edge cases
+        │   (Fast)     │     60-70% of total tests
+        └──────────────┘
+```
+
+### Level Selection Rules
+
+| Level | Test When | Do NOT Test |
+|-------|-----------|-------------|
+| **Unit** | Pure logic, calculations, transformations, validators, parsers | Framework glue, wrappers with no logic |
+| **Integration** | DB queries, API endpoints, service interactions, auth flows | Simple CRUD with no business rules |
+| **E2E** | Critical user journeys (login → action → result), payment flows | Every page variation, admin-only features |
+
+## 3. Strategy Template
+
+Produce this for every feature or project:
+
+```markdown
+# Test Strategy: {Feature Name}
+
+## Risk Assessment
+| Component | Risk Level | Why |
+|-----------|-----------|-----|
+| {component} | High/Med/Low | {data loss, revenue, security, UX} |
+
+## Coverage Plan
+| Layer | Target | What's Covered |
+|-------|--------|----------------|
+| Unit | {n} tests | {list of modules/functions} |
+| Integration | {n} tests | {list of API/DB interactions} |
+| E2E | {n} tests | {list of user journeys} |
+
+## Priority Order (implement in this sequence)
+1. {highest-risk component} — unit tests
+2. {API contracts} — integration tests
+3. {critical journey} — E2E test
+4. ... remaining by descending risk
+
+## Quality Gates
+- [ ] All unit tests pass
+- [ ] Integration tests pass with test DB
+- [ ] E2E critical path passes
+- [ ] Coverage ≥ {target}% on changed files
+```
+
+## 4. Risk-Based Prioritisation
+
+Not all code deserves equal test investment. Prioritise by risk:
+
+### High Risk (test thoroughly)
+- Money/payment logic
+- Authentication and authorisation
+- Data mutations (writes, deletes, migrations)
+- External API integrations
+- Security-sensitive code (input validation, sanitisation)
+
+### Medium Risk (test key paths)
+- Business logic with branching conditions
+- Data transformations and aggregations
+- State management (complex reducers, stores)
+- Error handling and recovery
+
+### Low Risk (test selectively)
+- Display components with no logic
+- Configuration files
+- Static content
+- Simple pass-through functions
+
+## 5. Coverage Goals
+
+Set coverage targets by component risk, not a blanket number.
+
+| Component Type | Minimum Coverage | Rationale |
+|---------------|-----------------|-----------|
+| Business logic / calculations | 90%+ | High cost of bugs |
+| API endpoints / routes | 80%+ | Contract stability |
+| Data access layer | 75%+ | Data integrity |
+| UI components with logic | 70%+ | User-facing bugs |
+| Utility functions | 85%+ | Widely reused |
+| Configuration / glue code | — | Not worth unit testing |
+
+## 6. Test Naming Convention
+
+Every test name answers three questions:
+
+```
+test_{what}_{condition}_{expected_outcome}
+```
+
+Examples:
+```python
+def test_calculate_discount_with_expired_coupon_returns_zero():
+def test_login_with_invalid_password_returns_401():
+def test_export_csv_with_empty_dataset_creates_headers_only():
+```
+
+## 7. When to Update the Strategy
+
+- New risk identified (security audit, incident, production bug)
+- Architecture change (new service, DB migration, API version)
+- Coverage drops below target on consecutive PRs
+- Feature scope expands significantly
+
+## 8. Anti-Patterns to Avoid
+
+| Anti-Pattern | Problem | Fix |
+|---|---|---|
+| Testing implementation details | Brittle, breaks on refactor | Test behaviour and outputs |
+| 100% coverage target | Leads to low-value tests | Risk-based targets per component |
+| Only happy path | Misses edge cases that cause incidents | Add error/boundary tests per risk |
+| Shared mutable state between tests | Flaky, order-dependent | Isolate with setup/teardown |
+| Slow test suite | Developers skip running tests | Keep unit tests under 30s total |
+| Testing mocked-only code | False confidence | Mix unit + integration testing |
+
+## 9. Output Artefact
+
+Produce `TEST-STRATEGY.md` in the project docs or agent-docs directory. Ensure it includes:
+1. Risk assessment table
+2. Coverage plan with test counts per layer
+3. Priority order for implementation
+4. Quality gate checklist
+5. Named test cases for the top 10 highest-risk areas

package/bundles/codex/.codex/skills/testing/webapp-testing/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/bundles/codex/.codex/skills/testing/webapp-testing/SKILL.md

@@ -0,0 +1,97 @@
+---
+name: webapp-testing
+context: fork
+description: Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
+license: Complete terms in LICENSE.txt
+---
+
+# Web Application Testing
+
+To test local web applications, write native Python Playwright scripts.
+
+**Helper Scripts Available**:
+- `scripts/with_server.py` - Manages server lifecycle (supports multiple servers)
+
+**Always run scripts with `--help` first** to see usage. DO NOT read the source until you try running the script first and find that a customized solution is abslutely necessary. These scripts can be very large and thus pollute your context window. They exist to be called directly as black-box scripts rather than ingested into your context window.
+
+## Decision Tree: Choosing Your Approach
+
+```
+User task → Is it static HTML?
+    ├─ Yes → Read HTML file directly to identify selectors
+    │         ├─ Success → Write Playwright script using selectors
+    │         └─ Fails/Incomplete → Treat as dynamic (below)
+    │
+    └─ No (dynamic webapp) → Is the server already running?
+        ├─ No → Run: python scripts/with_server.py --help
+        │        Then use the helper + write simplified Playwright script
+        │
+        └─ Yes → Reconnaissance-then-action:
+            1. Navigate and wait for networkidle
+            2. Take screenshot or inspect DOM
+            3. Identify selectors from rendered state
+            4. Execute actions with discovered selectors
+```
+
+## Example: Using with_server.py
+
+To start a server, run `--help` first, then use the helper:
+
+**Single server:**
+```bash
+python scripts/with_server.py --server "npm run dev" --port 5173 -- python your_automation.py
+```
+
+**Multiple servers (e.g., backend + frontend):**
+```bash
+python scripts/with_server.py \
+  --server "cd backend && python server.py" --port 3000 \
+  --server "cd frontend && npm run dev" --port 5173 \
+  -- python your_automation.py
+```
+
+To create an automation script, include only Playwright logic (servers are managed automatically):
+```python
+from playwright.sync_api import sync_playwright
+
+with sync_playwright() as p:
+    browser = p.chromium.launch(headless=True) # Always launch chromium in headless mode
+    page = browser.new_page()
+    page.goto('http://localhost:5173') # Server already running and ready
+    page.wait_for_load_state('networkidle') # CRITICAL: Wait for JS to execute
+    # ... your automation logic
+    browser.close()
+```
+
+## Reconnaissance-Then-Action Pattern
+
+1. **Inspect rendered DOM**:
+   ```python
+   page.screenshot(path='/tmp/inspect.png', full_page=True)
+   content = page.content()
+   page.locator('button').all()
+   ```
+
+2. **Identify selectors** from inspection results
+
+3. **Execute actions** using discovered selectors
+
+## Common Pitfall
+
+❌ **Don't** inspect the DOM before waiting for `networkidle` on dynamic apps
+✅ **Do** wait for `page.wait_for_load_state('networkidle')` before inspection
+
+## Best Practices
+
+- **Use bundled scripts as black boxes** - To accomplish a task, consider whether one of the scripts available in `scripts/` can help. These scripts handle common, complex workflows reliably without cluttering the context window. Use `--help` to see usage, then invoke directly. 
+- Use `sync_playwright()` for synchronous scripts
+- Always close the browser when done
+- Use descriptive selectors: `text=`, `role=`, CSS selectors, or IDs
+- Add appropriate waits: `page.wait_for_selector()` or `page.wait_for_timeout()`
+
+## Reference Files
+
+- **examples/** - Examples showing common patterns:
+  - `element_discovery.py` - Discovering buttons, links, and inputs on a page
+  - `static_html_automation.py` - Using file:// URLs for local HTML
+  - `console_logging.py` - Capturing console logs during automation

package/bundles/codex/.codex/skills/testing/webapp-testing/examples/console_logging.py

@@ -0,0 +1,35 @@
+from playwright.sync_api import sync_playwright
+
+# Example: Capturing console logs during browser automation
+
+url = 'http://localhost:5173'  # Replace with your URL
+
+console_logs = []
+
+with sync_playwright() as p:
+    browser = p.chromium.launch(headless=True)
+    page = browser.new_page(viewport={'width': 1920, 'height': 1080})
+
+    # Set up console log capture
+    def handle_console_message(msg):
+        console_logs.append(f"[{msg.type}] {msg.text}")
+        print(f"Console: [{msg.type}] {msg.text}")
+
+    page.on("console", handle_console_message)
+
+    # Navigate to page
+    page.goto(url)
+    page.wait_for_load_state('networkidle')
+
+    # Interact with the page (triggers console logs)
+    page.click('text=Dashboard')
+    page.wait_for_timeout(1000)
+
+    browser.close()
+
+# Save console logs to file
+with open('/mnt/user-data/outputs/console.log', 'w') as f:
+    f.write('\n'.join(console_logs))
+
+print(f"\nCaptured {len(console_logs)} console messages")
+print(f"Logs saved to: /mnt/user-data/outputs/console.log")