I’ll investigate one issue in a small Python or browser JavaScript example and give you a written account of what I could reproduce, what the evidence shows and what to do next. The scope is up to 10 source files and 2,000 lines, using Python’s standard library or vanilla browser JavaScript, HTML and CSS. It covers one reproduction case and one execution target. The example must run without external services, paid dependencies or production access. You receive reproduction steps, relevant test results, findings and a proposed repair approach. If the cause cannot be established, the report explains the diagnostic limits and missing evidence. A code fix is not included or guaranteed. Repairs, broader debugging and complex applications can be scoped separately. To scope the work, provide the minimal source example and exact run command or browser steps; expected and actual behaviour; one reproduction sequence with test input and sanitized errors; the Python version and operating system or the desktop browser and version; and relevant recent changes or a known working version, if available. Remove credentials and production records. I use OpenAI Codex for AI-assisted development. Before processing your brief or source code with that service, I need confirmation that you have the right to share it and explicit permission covering the supplied code and brief. Code that cannot be shared with that service needs a separately assessed arrangement. Customer records and source documents remain local unless you separately identify and authorize content for external AI review. Leaving that authorization blank grants no permission to review document or record content with AI. Do not provide credentials or production personal data. The proposed delivery period starts on a date agreed in writing after the required inputs, permissions and platform contracting steps are complete, following the platform’s actual rules. The package includes 1 consolidated written revision within this scope. Defects against the agreed acceptance checks are corrections; new features or changed rules need a separate scope. Briefs, progress updates, revisions and handover are handled in writing.