Add consolidated design-change report and expanded PR body draft

[Copilot]

This change turns the previously discussed design-change summary into a repository document and expands it into a PR-ready body. It gives one place to review the current architecture shift, validation framing, and admin UI direction without reconstructing context from multiple docs.

• What this adds

  • New document: docs/overall-design-change-pr-report-2026-05-08.md
  • Consolidated summary of the repository-wide design changes
  • Expanded PR body draft that can be pasted into GitHub as-is
  • Short-form PR body variant for lighter reviews

• How the document is structured

  • Korean summary for the repository’s working context
  • English PR body for direct use in GitHub
  • Clear source references to the existing readiness, orchestrator, and admin UI documents

• Content alignment

  • Uses repository-relative paths instead of runner-specific absolute paths
  • Calls out the bilingual structure at the top so the split format is immediately understandable
  • Keeps the narrative centered on:
    • generator contract unification
    • hard-gate/readiness evidence
    • operational verification framing
    • admin dashboard orchestration-hub redesign

• Why this is useful

  • Reduces duplication across status, readiness, and reporting threads
  • Makes the current design baseline easy to scan during review
  • Provides a reusable PR/reporting artifact instead of ad hoc summary text

Example excerpt from the added document:

## 3. 실제 PR 본문 초안

## Summary

This PR consolidates the repository-wide design changes into a single operational baseline. It aligns the public/admin runtime structure, unifies the generator contract around the `app/services/` package layout, strengthens post-generation hard-gate validation, and reorganizes the admin dashboard into an operator-centric orchestration hub.

Summary by Sourcery

Add a bilingual repository-wide design-change report documenting the consolidated architecture, validation, and admin UI baseline, including a ready-to-use pull request body and short-form variant.

Documentation:

• Document the current platform/runtime structure, generator contract unification, hard-gate validation flow, capability evidence model, and admin dashboard UX redesign in a single bilingual design-change report.
• Provide both full-length and short-form PR body drafts that can be pasted directly into GitHub, with clear references to related readiness and orchestrator documents.

[sourcery-ai]

Reviewer's Guide

Adds a new bilingual documentation file that consolidates repository-wide architecture, validation, and admin UI design changes into a single design-change report, and embeds both full-length and short-form PR body drafts for reuse.

Sequence diagram for post-generation hard-gate validation flow

sequenceDiagram
  participant Orchestrator
  participant MultiGenerator
  participant ServicePackage
  participant HardGate
  participant SemanticGate
  participant CompletionGate
  participant PackagingAudit
  participant OutputAudit
  participant ReadinessChecklist
  participant SelfRunRecords
  participant AdminDashboard

  Orchestrator->>MultiGenerator: Trigger generation
  MultiGenerator->>ServicePackage: Create app/services/ layout
  ServicePackage-->>MultiGenerator: Service package ready

  MultiGenerator->>HardGate: Start post-generation validation
  HardGate->>HardGate: Install dependencies
  HardGate->>HardGate: Start standalone boot
  HardGate->>HardGate: Run core API smoke checks
  HardGate->>HardGate: Execute tests
  HardGate->>HardGate: Verify ZIP reproduction

  HardGate->>SemanticGate: Provide generation semantics
  SemanticGate-->>HardGate: Semantic gate result

  HardGate->>CompletionGate: Provide execution results
  CompletionGate-->>HardGate: Completion gate result

  HardGate->>PackagingAudit: Provide build artifacts
  PackagingAudit-->>HardGate: Packaging audit result

  HardGate->>OutputAudit: Provide output snapshot
  OutputAudit-->>HardGate: Output audit result

  HardGate->>ReadinessChecklist: Update final_readiness_checklist.md
  ReadinessChecklist-->>HardGate: Readiness status

  HardGate->>SelfRunRecords: Record self_run_status and evidence_digest
  SelfRunRecords-->>HardGate: Stored trace

  SelfRunRecords->>AdminDashboard: Expose completion_gate_ok, failure_tags, target_file_ids
  ReadinessChecklist->>AdminDashboard: Expose readiness evidence
  AdminDashboard-->>AdminDashboard: Render operator view for closure decision

Loading

File-Level Changes

Change	Details	Files
Introduce a consolidated bilingual design-change report with reusable PR body drafts.	Add a Korean-language repository-wide design-change summary that captures runtime structure, generator contract unification, validation and readiness framing, and admin UI redesign. Embed an English, GitHub-ready PR body draft describing the architecture baseline, validation standards, capability evidence, risks, rollback, and reviewer focus. Provide a short-form PR body variant emphasizing service-package contract alignment, hard-gate/readiness evidence flow, and admin hub UI direction. Document explicit references to existing readiness, orchestrator, and admin dashboard documents as the validation and design basis.	docs/overall-design-change-pr-report-2026-05-08.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[parkcheolhong]

설계도와 보고서는 중분이 검토했습니다,

[sourcery-ai]

Hey - I've found 1 issue, and left some high level feedback:

• Consider making the filename and top-level title less date-specific (or clearly marking it as a snapshot) so it’s easier to reuse or discover as a long-lived baseline rather than a one-off report for 2026-05-08.
• In the English PR body section, multiple ## Summary headings at different places could make navigation and linking harder; using more specific headings (e.g., ## Full PR Summary, ## Short PR Summary) would improve readability and clarity in GitHub’s TOC.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider making the filename and top-level title less date-specific (or clearly marking it as a snapshot) so it’s easier to reuse or discover as a long-lived baseline rather than a one-off report for 2026-05-08.
- In the English PR body section, multiple `## Summary` headings at different places could make navigation and linking harder; using more specific headings (e.g., `## Full PR Summary`, `## Short PR Summary`) would improve readability and clarity in GitHub’s TOC.

## Individual Comments

### Comment 1
<location path="docs/overall-design-change-pr-report-2026-05-08.md" line_range="118" />
<code_context>
+- Connected self-run terminal status and `applied_to_source` evidence to the admin-facing review flow.
+
+### 5. Operational Verification Standards
+- Kept operational verification centered on real production paths, including admin, marketplace, websocket, system-settings, and workspace self-run record flows.
+- Kept local verification baselines on `127.0.0.1:8000` or the production domain rather than `localhost`.
+- Maintained the rule that completion status requires operational evidence, not just code presence.
</code_context>
<issue_to_address>
**suggestion (typo):** Align the spelling of 'system-settings' with earlier 'system settings' for consistency.

Here you use `system-settings` (hyphenated), while earlier in the Korean section it’s `system settings` (with a space). Please standardize on one form (e.g., `system settings`) so it’s clear they refer to the same concept.

```suggestion
- Kept operational verification centered on real production paths, including admin, marketplace, websocket, system settings, and workspace self-run record flows.
```
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[parkcheolhong]

보고서 잘 확인했습니다

[Copilot]

Pull request overview

Adds a single repository document that consolidates the current repo-wide design/architecture shift and provides ready-to-paste PR body drafts (full + short), with source references to existing readiness/orchestrator/admin-UI documentation.

Changes:

• Add docs/overall-design-change-pr-report-2026-05-08.md as a bilingual (KR design summary + EN PR body) consolidated report.
• Include a full PR-body draft covering generator contract unification, hard-gate/readiness evidence framing, operational verification, and admin dashboard direction.
• Include a short-form PR-body variant for lighter reviews.

[parkcheolhong]

@copilot apply changes based on the comments in this thread

[parkcheolhong]

@copilot apply changes based on the comments in this thread