Unify estimate intake with Dev+1 rebrand, account auto-provisioning, and email verification gating#60
Merged
Conversation
Copilot created this pull request from a session on behalf of
iaretechnician
May 31, 2026 13:39
View session
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR updates the website and unified dashboard flow to align with the Dev+1 naming change and fixes estimate intake so requests always carry a visible
Estimate IDand are linked to client accounts. It also introduces verification-gated client activation so new estimate-driven accounts cannot log in until email verification is completed.Branding + public label migration (Dev Partner → Dev+1)
Dev Partnerreferences withDev+1across primary navigation, footer, service page metadata/content, dashboard copy, and related product messaging./design-debug-deploy.php) while updating visible page title and content language.Estimate request lifecycle hardening
/estimate.phpto enforce required inputs (name,email,project_type,description; plusdesired_usernamewhen anonymous).estimate_idin estimate records.Estimate ID, account context, and game/server Discord guidance when applicable.Anonymous submitter → client account auto-creation
role=clientstatus=pending_verificationEmail verification flow + resend
includes/email.phpwithsend_email(...)wrapper and explicit SMTP hardening TODOs./verify-email.phptoken activation endpoint and/resend-verification.phpfor renewal of verification tokens.Login + redirect safety + status gating
/login.phpto:active,pending_verification,disabled)return/redirectto local relative paths only.includes/portal-helpers.php.Unified dashboard + staff visibility updates
/dashboard.phpmodel with role-based rendering.Estimate ID,Project Type,Status,Submitted Date).discord_username,client_username, and estimate fallback labelLegacy Requestfor historical entries without IDs).