Revert main to 2026-03-14 state

[Copilot]

Four commits merged on 2026-03-15 need to be undone to restore main to its end-of-day 2026-03-14 state (f036f1b).

Reverted (newest → oldest)

• 75d9b45 — Copilot/review feedback report (Copilot/review feedback report #3): CI workflow, ARCHITECTURE.md, pyproject.toml, mpf/fullstack.py, backend_controller.py, interpreter.py
• 9dfe387 — Fix Python 3.10 UTC → timezone.utc in engine_core.py
• de3f9a4 — "Initial plan ([WIP] Fix Python 3.10 failure in CI #4)" — empty commit, no file changes
• ea06776 — Fix 9 failing tests: confirmation gating, shell routing, headless config (interpreter.py, shell.py, JLframe_Engine_Framework.headless.json, test_shell_tool.py)

Verification

git diff f036f1b HEAD is empty — tree exactly matches the 2026-03-14 target.

Note on history clearing

Erasing git history requires a force-push directly to main and cannot be done via PR. After merge, if desired:

git checkout --orphan clean-main
git add -A
git commit -m "Clean slate"
git push --force origin clean-main:main

Original prompt

Revert the repository jaden688/JL_Engine-local main branch back to the state it was yesterday (relative to current date 2026-03-15, so target date is 2026-03-14). Determine the appropriate commit on main representing the desired repository state from 2026-03-14 and create a pull request that restores the repository to that state. Prefer a safe approach that preserves history (for example, by reverting commits made after the target point) rather than rewriting branch history. Validate the target commit carefully so the resulting PR makes the repository contents match the state as of yesterday. Include a concise summary of the chosen target commit and what was reverted in the PR description.

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: I would like to revert the main repository back to the state it was yesterday

Assistant: I can help, but I need the exact repository owner/name first.

Please provide:

• Repository: owner/repo

Optional but helpful:

• Which branch counts as “main” if it’s not literally main
• Whether by “yesterday” you mean March 14, 2026 and whether you want:
  1. the branch reset to the latest commit from that date, or
  2. specific commits reverted with new revert commits

Important: rewriting a main branch can be destructive, so I won’t do it without that confirmation.

User: There you go does that help back to yesterday

Assistant: We’re waiting for your response to the GitHub tool authorization dialog so I can continue creating the PR to restore jaden688/JL_Engine-local to yesterday’s state.

This pull request was created from Copilot chat.

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

[deepsource-io]

DeepSource Code Review

We reviewed changes in 75d9b45...81fc09e on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade

Security   Reliability   Complexity   Hygiene

Code Review Summary

Analyzer	Status	Updated (UTC)	Details
Java		Mar 15, 2026 12:06p.m.	Review ↗
Shell		Mar 15, 2026 12:06p.m.	Review ↗
Python		Mar 15, 2026 12:06p.m.	Review ↗
Secrets		Mar 15, 2026 12:06p.m.	Review ↗

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 81fc09ef50

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Replace datetime.UTC with timezone.utc for Python 3.10

Importing UTC from datetime only works on newer Python versions, but this project still declares support for Python 3.10; with this change, importing jl_engine_core.engine_core now raises ImportError on 3.10 and prevents CLI/API startup (this is currently reproducible during pytest collection in this environment). Please switch back to a 3.10-compatible UTC timezone constant.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Re-enable confirmation for destructive local actions

Setting requires_confirmation to False for bridge_local file writes/creates (and similarly for run_shell) bypasses the pending-action approval path, because run() only gates when this flag is true before executing _call_tool. That means filesystem and shell mutations now run immediately instead of returning confirmation_required, reintroducing unsafe auto-execution and breaking confirmation-based runtime flows.

Useful? React with 👍 / 👎.