OWNER 009 flatten workspace artifacts

Author: ToolboxAid

.gitignore

@@ -17,12 +17,16 @@ NEXT_COMMAND.txt
 node_modules/
 tests/results/
 tests/results/**
-dev/workspace/artifacts/tmp/
-dev/workspace/artifacts/tmp/**
-dev/workspace/artifacts/test-results/
-dev/workspace/artifacts/test-results/**
-dev/workspace/artifacts/zips/
-dev/workspace/artifacts/zips/**
+dev/workspace/tmp/
+dev/workspace/tmp/**
+dev/workspace/test-results/
+dev/workspace/test-results/**
+dev/workspace/zips/
+dev/workspace/zips/**
+dev/workspace/logs/
+dev/workspace/logs/**
+dev/workspace/generated/
+dev/workspace/generated/**
 tmp/
 dev/scripts/untracked/
 dev/scripts/untracked/**

README.md

@@ -33,7 +33,7 @@ This repository follows a docs-first game/runtime model, combining a stable engi
 3. Browse archived reference samples from [dev/archive/v1-v2/samples/index.html](dev/archive/v1-v2/samples/index.html)
 4. Explore tools under [toolbox/](toolbox/)
 5. Review engine and architecture boundaries in [docs/architecture/](docs/architecture/)
-6. Follow the workflow in [dev/build/dev/](dev/build/dev/) and [dev/build/pr/](dev/build/pr/)
+6. Follow the workflow in [dev/build/ProjectInstructions/](dev/build/ProjectInstructions/) and [dev/build/pr/](dev/build/pr/)
 
 ---
 
@@ -107,7 +107,7 @@ PLAN_PR → BUILD_PR → APPLY_PR
 - One PR per purpose
 - Small, surgical changes
 - Docs-first implementation planning
-- Delta ZIP outputs stored under `<project folder>/dev/workspace/artifacts/zips/`
+- Delta ZIP outputs stored under `<project folder>/dev/workspace/zips/`
 
 ---
 
@@ -116,7 +116,7 @@ PLAN_PR → BUILD_PR → APPLY_PR
 - [docs/README.md](docs/README.md) → top-level documentation index
 - [docs/architecture/](docs/architecture/) → durable architecture and boundary contracts
 - [dev/build/pr/](dev/build/pr/) → preserved PR history and architecture evolution
-- [dev/build/dev/](dev/build/dev/) → active workflow controls and implementation planning
+- [dev/build/ProjectInstructions/](dev/build/ProjectInstructions/) → active governance and workflow controls
 - [dev/reports/](dev/reports/) → active report artifacts
 - [dev/archive/](dev/archive/) → archived dev-ops notes and generated reports
 

dev/README.md

@@ -15,12 +15,12 @@ This folder is the destination shell for non-deployable development workspace ma
 
 - `dev/build/` owns active development governance and PR workflow material.
 - `dev/reports/` owns generated reports.
-- `dev/workspace/artifacts/` owns generated non-report artifacts and local temporary workspace output.
+- `dev/workspace/` owns generated non-report artifacts and local temporary workspace output.
 - `dev/tests/` owns non-deployable tests.
 - `dev/scripts/` owns development-only scripts and runners.
 - `dev/config/` owns development-only runner and tooling configuration.
 - `dev/archive/` owns historical development reference material.
-- `dev/project-instructions/` is deprecated reference only; active Project Instructions live under `dev/build/ProjectInstructions/`.
+- `dev/build/ProjectInstructions/` is the only active Project Instructions source.
 
 ## Data Boundary
 

dev/build/ProjectInstructions/PROJECT_INSTRUCTIONS.md

@@ -53,7 +53,7 @@ Existing Project Instructions outside `dev/build/ProjectInstructions/` remain pr
 - `dev/build/ProjectInstructions/` owns governance, team instructions, standards, and addendums.
 - `dev/build/pr/` owns PR workflow documents, templates, and examples.
 - `dev/reports/` owns generated reports and audits.
-- `dev/workspace/artifacts/` owns generated non-report artifacts, repo-structured ZIPs, and local temporary workspace output.
+- `dev/workspace/` owns generated non-report artifacts, repo-structured ZIPs, and local temporary workspace output.
 - root `dev/archive/` owns historical reference material only.
 
 ## Team Backlog, SOD, And EOD Governance

dev/build/ProjectInstructions/README.txt

@@ -4,7 +4,7 @@ Folder purpose:
 This folder is the only active Project Instructions source for Game Foundry Studio. It organizes active governance, backlog, team assignment, standards, deprecation, and history material under `dev/build/ProjectInstructions/`.
 
 Preservation rules:
-Preserve historical Project Instructions material as deprecated reference only. Do not treat root-level copies in `dev/build/dev/`, `dev/project-instructions/`, `dev/archive/`, or archived snapshots as active instruction sources. When a conflict appears, `dev/build/ProjectInstructions/` wins unless OWNER explicitly approves a newer governance change.
+Preserve historical Project Instructions material as deprecated reference only. Do not treat root-level copies in `dev/build/dev/`, `dev/archive/`, or archived snapshots as active instruction sources. When a conflict appears, `dev/build/ProjectInstructions/` wins unless OWNER explicitly approves a newer governance change.
 
 Backlog workflow:
 Backlog work is tracked under backlog/. BACKLOG_MASTER.md is the planned source for backlog item status, notes, and references. Backlog item text is treated as immutable once created; status and notes may change under the governance addendums.

dev/build/ProjectInstructions/addendums/canonical_repository_structure.md

@@ -27,7 +27,7 @@ Development workspace:
 - dev/scripts/
 - dev/config/
 - dev/archive/
-- dev/workspace/artifacts/
+- dev/workspace/
 
 Tools:
 - toolbox/{tool-name}/index.html
@@ -64,4 +64,4 @@ These legacy transition buckets may remain until explicit migration PRs move the
 - New deployable `src/` work follows `src/web/`, `src/api-runtime/`, or `src/runtime/`.
 - New non-deployable work belongs under `dev/`.
 - Required reports belong under flat `dev/reports/`.
-- Required ZIPs belong under `dev/workspace/artifacts/zips/`; generated temporary artifacts belong under `dev/workspace/artifacts/tmp/`.
+- Required ZIPs belong under `dev/workspace/zips/`; generated temporary artifacts belong under `dev/workspace/tmp/`.

dev/build/ProjectInstructions/addendums/codex_artifact_and_reporting_standard.md

@@ -31,7 +31,7 @@ Minimum ZIP contents:
 ZIP artifacts must be written under:
 
 ```text
-dev/workspace/artifacts/zips/
+dev/workspace/zips/
 ```
 
 Reports must remain flat under `dev/reports/`. Use descriptive filenames that include the PR, team, runner, or lane context instead of nested team or runner report folders.
@@ -44,7 +44,7 @@ Optional:
 - validation.txt
 - generated artifacts
 
-Generated non-report artifacts must live under `dev/workspace/artifacts/`.
+Generated non-report artifacts must live under `dev/workspace/`.
 
 ## Completion Reporting
 

dev/build/ProjectInstructions/addendums/documentation_ownership.md

@@ -5,7 +5,7 @@ Owner: OWNER
 
 ## Purpose
 
-Define the ownership model for documentation under `dev/build/dev/` after Project Instructions consolidation.
+Define the ownership model for documentation under `dev/` after Project Instructions consolidation.
 
 ## Canonical Ownership
 
@@ -24,7 +24,7 @@ Define the ownership model for documentation under `dev/build/dev/` after Projec
 - generated reports
 - audits
 
-`dev/workspace/artifacts/` owns:
+`dev/workspace/` owns:
 - generated non-report artifacts
 - generated ZIP files
 - local temporary workspace output
@@ -37,19 +37,19 @@ The repository root `dev/archive/` owns:
 - No active governance may exist outside `dev/build/ProjectInstructions/`.
 - No reusable PR template may exist outside `dev/build/pr/templates/`.
 - No generated report may exist outside `dev/reports/`.
-- No generated non-report artifact may exist outside `dev/workspace/artifacts/`.
+- No generated non-report artifact may exist outside `dev/workspace/`.
 - No active document may exist outside its owning area.
 - Historical reference material must not be treated as active governance.
-- `dev/build/dev/start_of_day/` is a protected legacy handoff area and must not become an active Project Instructions source.
+- Legacy `start_of_day/` folders are retired and must not become an active Project Instructions source.
 
 ## Folder Rules
 
 - `dev/build/ProjectInstructions/standards/` contains active contract, model, and platform standards.
 - `dev/build/pr/templates/` contains reusable PR templates.
 - `dev/build/pr/reference/` contains historical or reference PR documents.
 - `dev/reports/` contains flat generated report outputs. Use team, runner, lane, or PR naming in filenames instead of nested report folders.
-- `dev/workspace/artifacts/zips/` contains repo-structured ZIP outputs.
-- `dev/workspace/artifacts/tmp/` contains temporary generated files.
+- `dev/workspace/zips/` contains repo-structured ZIP outputs.
+- `dev/workspace/tmp/` contains temporary generated files.
 
 ## Validation
 
@@ -58,5 +58,5 @@ Documentation ownership cleanup PRs must verify:
 - no active Project Instructions outside `dev/build/ProjectInstructions/`
 - no reusable PR templates outside `dev/build/pr/templates/`
 - no generated reports outside `dev/reports/`
-- no generated non-report artifacts outside `dev/workspace/artifacts/`
+- no generated non-report artifacts outside `dev/workspace/`
 - no runtime/product/API/database files changed unless explicitly scoped

dev/build/ProjectInstructions/addendums/koti_layout_contract.md

@@ -6,8 +6,8 @@ Define the minimal, explicit data contract for a King of the Iceberg (KOTI) base
 
 ## 2. Source Artifacts Used
 
-- `dev/workspace/artifacts/tmp/uat_exports/king_of_the_iceberg_layout_snapshot.json`
-- `dev/workspace/artifacts/tmp/uat_tool_layout_workflow_results.json`
+- `dev/workspace/tmp/uat_exports/king_of_the_iceberg_layout_snapshot.json`
+- `dev/workspace/tmp/uat_tool_layout_workflow_results.json`
 - `dev/reports/PR_tool_layout_workflow_baseline_report.md`
 
 Observed baseline facts from these artifacts:

dev/build/ProjectInstructions/addendums/multi_team.md

@@ -129,7 +129,7 @@ Required gate:
    - blocked PRs with blockers
    - next review queue
    - final branch/worktree/local-origin sync
-   - repo-structured ZIP path under `dev/workspace/artifacts/zips/`
+   - repo-structured ZIP path under `dev/workspace/zips/`
    - final repository state block
 
 OWNER_049 lesson:
@@ -158,7 +158,7 @@ Required steps:
    - local/origin sync = 0 0
 5. Record final main commit.
 6. Report final repository state.
-7. Produce a repo-structured ZIP under `dev/workspace/artifacts/zips/` that includes the EOD report and all changed or preserved repo files from the closeout.
+7. Produce a repo-structured ZIP under `dev/workspace/zips/` that includes the EOD report and all changed or preserved repo files from the closeout.
 8. Record source branch disposition as `retained`.
 9. Mark the PR Closed only when every Closed gate passes.
 
@@ -180,7 +180,7 @@ Rules:
 - Do not leave Codex on a feature, team, workstream, recovery, governance, or owner branch after successful merge.
 - Plan, Build, validation, reports, ZIP packaging, and closeout stay tied to the same PR identity and source branch.
 - Source branches are retained by default after merge and closeout.
-- A PR is not Closed until the PR merged, changes are pushed, the repository is on `main`, `main` includes the merge or final commit, the worktree is clean, local/origin sync is `0/0`, no untracked files exist, branch disposition is recorded as `retained`, required reports exist, the required repo-structured ZIP exists under `dev/workspace/artifacts/zips/`, backlog is updated, and tool state is updated when applicable.
+- A PR is not Closed until the PR merged, changes are pushed, the repository is on `main`, `main` includes the merge or final commit, the worktree is clean, local/origin sync is `0/0`, no untracked files exist, branch disposition is recorded as `retained`, required reports exist, the required repo-structured ZIP exists under `dev/workspace/zips/`, backlog is updated, and tool state is updated when applicable.
 - A completed EOD closeout must produce the required ZIP even when the closeout changed no repo files; in that case, the ZIP must contain the EOD report proving the no-change result.
 - The EOD ZIP does not replace the EOD report or other required reports under `dev/reports/`.
 - If merge succeeds but repository is not returned to main: