refactor: move world concepts into engine

.agents/rules/forge-sync.md

@@ -1,29 +0,0 @@
----
-description: Local vs sync mode rules for git and Forgejo — commit, push, and PR policy per workflow.
----
-
-# Forge Sync Rules
-
-When a workflow uses explicit mode:
-
-- `Mode: sync` or `--sync` means sync mode.
-- no sync marker means local mode.
-- Do not ask whether git workflow should be agent-managed.
-
-Local mode:
-- No push.
-- No forge write tools.
-- No PR create/update/comment.
-
-Sync mode:
-- Commit completed workflow units.
-- Push after each unit commit.
-- Create PR after first push if missing.
-- Reuse existing PR on later pushes.
-- Comment/update PR only when workflow asks for it.
-
-Forbidden always:
-- No force push.
-- No branch deletion.
-- No hard reset.
-- No amending unless explicitly requested.

.agents/rules/openspec.md

@@ -1,19 +0,0 @@
----
-description: Rules for OpenSpec propose and archive workflows.
----
-
-# OpenSpec Instructions
-
-## OpenSpec Propose Workflow
-
-When proposing changes via `/opsx-propose`:
-
-- If the change introduces or modifies user-facing behavior (API changes, conventions), include a task section for updating `README.md` in the proposal's impact assessment.
-
-## OpenSpec Archive Workflow
-
-When archiving tasks via `/opsx-archive`:
-
-1. Automatically sync specs, do not ask the user.
-2. If mode is explicit, use `forge-sync` for archive commit, push, PR, and Forgejo behavior.
-3. If no mode is explicit, default to local mode.