feat: improve create-project flow with clear project type split

[CHY9213]

Summary

Improves the project creation flow by replacing the 6-category project type selector with two clear, visually distinct options: New Project and Bug Fix.

Changes

Template (App.vue)

• Replaced 6 project type options (Web Development, Repo Issue Fix, Mobile, AI/ML, Smart Contract, Other) with 2 clear categories: New Project and Bug Fix
• Larger, two-column tile layout with bigger icons and improved typography
• Dynamic placeholders: title, description, and tech stack fields change placeholder text based on selected project type
• Conditional form fields:
  • \Bug Fix\ selected → shows attach-repo section (now required) for loading GitHub issues
  • \New Project\ selected → shows helpful guidance hint

Styles (styles.css)

• Added .project-type-split 2-column grid layout
• Added .select-tile-big larger tiles
• Added .new-project-hint styled hint section

Testing

• npm run build:local ✅
• npm test ✅ (8/8 tests pass)

Wallet

HUFz3mnXkSDzfxfRgiKsZ6w5zgfcwShigHrYGxvgrjAF

Closes #12

[CHY9213]

Build & Test Verification ✅

\
npm run build:local → ✅ Build passes
npm test → ✅ 8/8 tests pass
\\

Changes Summary

• Replaced 6-category project type selector with New Project / Bug Fix split
• Large two-column tiles with clear visual distinction
• Dynamic placeholders adapt to selected project type
• Attach-repo section shows only for Bug Fix (now marked required)
• New Project shows helpful guidance hint
• Selected type stays visible throughout the flow

Wallet

HUFz3mnXkSDzfxfRgiKsZ6w5zgfcwShigHrYGxvgrjAF

Closes #12

[TUPM96]

Thanks for the PR. For bounty review, please add verification evidence in this PR before final review:

• screenshot, GIF, or video showing the changed flow/UI
• the test/build command(s) you ran and the result
• any relevant edge cases or viewport sizes checked

Evidence can be attached in a PR comment; images in comments count. If this PR has the star: missing label, please also star this repository so bounty eligibility can be verified.

[xingxi0614-cpu]

QA verification for PR #109

Target PR: #109
Head commit checked: 8fff2952885a35c8e4728c78cc357093605ebbd6
Author: CHY9213
Linked bounty: #12, improve create-project flow for new projects and existing bug fixes

GitHub Actions

All visible PR checks are green at the time of review:

• Secret scan: success
• Backend build and test: success
• Web build and test (frontend): success
• Web build and test (admin): success
• Web build and test (scan): success

Merge state is clean.

Local checks

I checked out the PR head and ran the relevant frontend commands:

npm test
# 8/8 tests passed

npm run build:local
# client build passed
# SSR build passed

What the PR changes

The PR replaces the previous six project-type tiles with two clearer choices:

• New Project
• Bug Fix

It also:

• makes placeholders depend on whether the selected type is Bug Fix,
• shows the attach-repository section only for Bug Fix,
• marks the attach-repository section as required for Bug Fix,
• adds a small New Project guidance hint.

The direction matches the bounty, and the diff is small and focused.

Blocking finding

The existing repository-import flow still writes the old project type value Repo Issue Fix.

Evidence:

frontend/src/App.vue

const projectTypeOptions = [
  { label: 'New Project', ... },
  { label: 'Bug Fix', ... },
];

async function loadRepoIssues() {
  ...
  if (repoImportedIssues.value.length) {
    projectSetupForm.projectType = 'Repo Issue Fix';
    ...
  }
}

Why this matters:

• Repo Issue Fix is no longer one of the selectable project type options.
• After a successful repo import, neither New Project nor Bug Fix is selected.
• The attach-repository section is rendered only when projectSetupForm.projectType === 'Bug Fix', so it disappears after import even though the user is in the existing-repo bug-fix flow.
• The dynamic placeholders and final project_type payload also receive the stale value instead of the new two-choice taxonomy.

This undercuts the main bounty goal: the flow should clearly split brand-new projects from existing bug fixes, but the existing repo-import path can still fall back to the removed legacy type.

Suggested fix:

• Change the repo-import success path from Repo Issue Fix to Bug Fix.
• Add a regression check around loadRepoIssues() or the project setup state so future changes cannot reintroduce removed project-type labels.
• Attach screenshots/GIF/video for the two normal paths after the fix: New Project and Bug Fix with successful repo import.

Evidence status

Evidence is incomplete. The author included build/test text, but I do not see attached screenshots, GIF, or video showing the changed project-type flow or the Bug Fix repo-import path. The maintainer already requested runtime evidence in the PR.

Recommendation

Request changes / not ready for bounty acceptance.

The PR is close and has green CI/local checks, but it should not be accepted until the stale Repo Issue Fix assignment is updated and visual evidence is attached for the fixed flows.

[TUPM96]

Not ready for bounty acceptance yet.

The direction matches #12, but the existing repo-import path still needs to be fixed end-to-end. In this head, the old project type value can still leak through the flow after repo import instead of consistently using the new Bug Fix / new-project taxonomy. Please make sure loadRepoIssues() and the final submitted/evaluation payload use the new type consistently.

Also, runtime evidence is still missing. Please attach screenshots/GIF/video for both paths: New Project, and Bug Fix with a successful repo import. The build/test text is useful, but visual evidence is required for this UI bounty.

[TUPM96]

Reviewed diff and added a maintainer follow-up so repo issue import now uses the new Bug Fix project type. Local npm test and build:local pass; GitHub checks are green. Selecting this implementation for #12.

[TUPM96]

MergeOS approved and merged this PR.

• Merge URL: 78522a7
• MRG credit URL: https://scan.mergeos.shop/address/0xf703cb8a82457b4090f4fc61f95cd3521102b339
• Credited worker: github:CHY9213
• Bounty type: Future bounty - small
• MRG credited: 25 MRG
• Proof hash: d7bffc01a48fdb47ef8cf2645c97bfe2cbaec477627885682a6f657458006803

[kejuunuy]

✅ Verification Report — PR #109

PR: #109 — feat: improve create-project flow with clear project type split
Author: @CHY9213
Status: Merged ✅

Verification Summary

1. Code Review: ✅ PR improves the create-project flow by splitting project types into clear categories. Changes are well-structured frontend modifications.

2. Scope: Focused on the project creation UI — adding clear type selection, improving form layout, and enhancing user guidance during project setup.

3. Evidence: PR body includes description of changes and the improvements made to the create-project flow.

4. Regression Risk: Low — changes are additive to the existing project creation flow without breaking existing functionality.

Recommendation

✅ Approve — Clean feature enhancement with focused scope.

---

Verification by @kejuunuy | Wallet: 0x96e04aC80b9b18ddbfB7e921800feF673BC1CA26

[CHY9213]

I noticed the MRG credit for this PR was sent to 0xf703cb8a82457b4090f4fc61f95cd3521102b339, but that is not my wallet address. My wallet address was included in the PR description.