Product updates, without internal noise.

The modal now separates today's manual composer from the future paid API flow, avoiding any autopost promise without cost controls.

The PRD/SDD now requires an X credit budget, spending limit, usage alert and canary account before enabling real posting.

The new block guides users to lock the best version, run one edit at a time and save the winner before testing another variation.

The copy reinforces 1 credit per confirmed edit, with no automatic batch spend, hidden autopost or loss of the original scene.

The billing card separates referral credits, future affiliates and optional Hotmart use while the commercial rules stay under manual validation.

The signed-in CTA opens authenticated support with the partner subject and starter message prefilled before any payout flow exists.

The signed-in area gained a compact account strip below the mobile shortcuts, with email and plan in user-facing language.

The change preserves the modern menu plus New, search and current-section shortcuts while meeting the rule that users see who is signed in.

The roadmap shows live examples, next routes and the ideal input before the CTA, helping visitors choose a small proof instead of starting a batch too early.

Facade, bathroom, commercial, night, clay and social now explain queue status and the safest material to validate fidelity.

The copy separates customers who want to earn credits from partners who may earn commission on qualified paid subscriptions.

The block captures interest through support and a partner list while margin, terms, attribution and misuse checks stay under validation.

The Account screen shows Now, Canary and Later stages so the manual kit is not confused with autoposting.

The card keeps image upload, made_with_ai, quota, logs and spend-limit requirements visible before any API publishing.

The projects list uses a softer fallback for work without a linked client, avoiding an error-like label on accounts with real renders.

The project footer now has a guided block with scene, comparison and curation steps that lead directly to a first test.

Visitors who are not ready to create an account can still open the examples library and compare routes first.

The /perfis page now lets visitors start a first portfolio render or review before/after examples before creating an account.

The path explains that Starter helps create publishable material while the public profile remains a Studio+ feature.

Visitors can choose a test route before scrolling through the full library, reducing friction on smaller screens.

Each shortcut opens signup while keeping the selected route for the first project workflow.

When a feature requires any paid plan, the subscription path now points to the under-$10 Starter entry plan.

Accounts that already satisfy the requested plan no longer see an alert asking for a lower subscription.

When preparing a public project, users can copy everything needed for safer manual publishing.

The flow still has no autopost, but organizes text, link, media and AI disclosure in the shape a future API integration must respect.

Each example now shows estimated cost and fidelity risk alongside the before/after, helping architects choose the first test.

The page reinforces 1 credit to validate a similar image and keeps edits, variations or video as separate confirmed steps.

Portfolio polish, client presentation and social crop now appear as ready workflows for turning an approved render into a deliverable.

Choosing a workflow opens the description mode so users can review intensity and confirm credits before generating.

Instead of a row of partially hidden chips, navigation now shows New, the current area and a stable Menu button.

The menu groups Main, Tools, System and Account, making it easier to move around without dragging a mobile bar.

The billing screen now repeats the commercial anchor for Starter, reducing doubt for users who want a small paid routine.

This is a clarity improvement: price, credits, upgrade or downgrade actions and billing portal behavior continue to follow the existing rules.

The projects guide now frames a small pilot project, one clear image and a first render as the initial proof.

Project creation keeps the controlled-scene context and reinforces that comparison comes before spending credits on a batch.

The first-render step now checks real completed renders, so users are not tied to the SketchUp milestone to prove the first scene.

The path now prioritizes account, email, first render and first edit before suggesting the connector as an accelerator.

Open steps show Open instead of Ready, avoiding the visual contradiction between pending status and action copy.

The coverage roadmap is no longer just a queue. It explains the safe loop for generating more examples without scaling a batch too early.

Visitors understand the sequence of choosing a scene, validating fidelity, editing with control and keeping the winning version.

After confirming an edit, switching from 1 to 2 or 3 options clears the confirmation so a higher spend is reviewed again.

The variation picker shows the cost for each option and explains how many credits are missing when the balance cannot cover that exploration.

The modal explains that a future integration should still keep human review, authorize the X account and upload the image before creating the post.

The kit reinforces that the render should be marked as AI-generated media when the social network offers that option.

When the cycle date has already passed, ArchScene shows the last recorded cycle instead of calling it the next billing date.

The logged-in comparison still keeps Starter as the under-$10 entry option without implying a stale future charge.

Users with one project and no renders see the main path to upload images, without a comparison action that cannot create a useful link yet.

The comparison link remains available once two public projects exist, matching the client portfolio workflow.

Alongside approval, before/after and portfolio, users can prepare a prospecting message before opening X.

The improvement stays in the safe human-review flow, without new OAuth, X tokens or automatic publishing.

The new section translates modern AI rendering product patterns into a practical decision: what to test first, what proof to watch and what next step to take.

Each route has its own CTA to start the first test without turning the public page into technical documentation.

Users review text, download the render image and confirm the AI disclosure before publishing manually.

The copy makes it clear that future autoposting needs X account authorization, media upload and AI-generated media disclosure.

A copy do Starter reforca US$7.99/R$39, 30 creditos mensais e uso em um projeto pequeno de cliente.

A comparacao logada explica que Starter e a entrada de baixo risco, enquanto Solo, Plus e Pro escalam com volume.

Portfolio previews no longer show an icon that could look like a broken image while renders are still loading.

Even when a public render takes a few seconds, the profiles page keeps an intentional look aligned with the premium visual system.

When the render is ready to attach, the modal reminds users to mark it as AI-generated media if the social network asks for that confirmation.

The flow still uses a manual composer, public link, downloadable image and human review, with no new OAuth or automatic publishing.

The active portfolios panel now has an editorial placeholder and higher loading priority for the first visible renders.

Even when the image proxy takes a few seconds, the public showcase no longer looks like an empty dark block.

Metric cards are no longer squeezed into four columns inside the main dashboard area, preventing labels from breaking mid-word.

The progress area stays compact, but numbers and descriptions are easier to scan on the first visit.

Before the first upload, the Generate first render button stays unavailable and explains that a renderable image is required.

The explanation is associated with the blocked button, helping screen readers and reducing uncertainty during the first test.

The Starter block now has a direct call to view the entry plan before the full pricing cards.

The copy reinforces that visitors can start small, cancel anytime and upgrade only when volume requires it.

The project link no longer gets mixed into the X text body, reducing duplication and making the public card more predictable.

Manual posts now include ArchScene and RenderArquitetonico hashtags without autoposting, new tokens or publishing before human review.

Shortcut cards no longer squeeze four actions into the same row on medium screens and keep the supporting copy visible.

The home screen still prioritizes the next step, now with steadier cards for choosing project, gallery, example or audit.

The page lists facades, bathrooms, small commercial spaces, night lighting, raw models and social candidates as test routes.

Each route explains what to upload and what signal to judge before turning a room into a batch or post.

Visitors see Starter from $7.99 or R$39 per month before reaching the full plan cards.

The hero reinforces 5 free credits with no card and shows the low-risk paid next step.

When the social kit offers the render image, it also shows a short alt text users can copy into the social network.

The social kit modal now scrolls internally, keeping caption, image and accessibility fields reachable.

Example buttons now open the project workbench with the selected test context instead of losing the intent at login.

The projects page shows a short three-step block to create a small project, compare fidelity and only then expand the batch.

Visitors can choose between fast confidence, geometry check or portfolio-ready image before creating an account.

Each path explains what it is for, what to validate and which image type to use as the first test.

The contact and new-conversation blocks now shrink correctly inside the screen instead of pushing the layout sideways.

The file field stays contained inside the form, keeping the support area more stable on narrow screens.

After choosing a first-scene route, visitors now see a clear call to start the test without going back to the top of the page.

Each visual example now offers a similar-scene test, keeping fidelity proof connected to signup.

When the social kit starts from a recent render, the modal offers the image download so the user can attach it manually in the X composer.

The flow stays on Web Intent and human review: prepared text, public link and downloadable image, with no autopost or OAuth before the canary.

Before the first result, the Render card opens the first-render guide; after that, it returns to the full generation panel.

The page now recommends generating from one ready image and comparing before/after instead of suggesting parallel paths too early.

When the library has no items yet, the primary CTA can open the latest project to upload the first source image.

The empty state explains that the image starts inside the project and returns to the Gallery once the render is ready for editing.

Long labels such as downgrade to Starter now wrap inside the button instead of overflowing the card.

The credits page received clearer Portuguese wording for balance, entries, debits and refunds.

The $7.99 or R$39 plan is framed as the first paid routine after one good render, before jumping into Solo.

A quick choice guide explains when to stay on 5 credits, when to enter Starter and when to move up to Solo or Plus.

Visitors can choose between joinery, exterior areas, SketchUp scenes or client-ready comparisons before opening the workbench.

Each playbook explains what to upload, what to check and what to do next without exposing internal technical terms.

Architects can choose a ready intent, review the text and apply the recommended strength before spending a credit.

Each recipe starts with fidelity language to preserve layout, materials, furniture and the project reading.

Architects can adjust the message, keep the public link and copy the final text without leaving the modal.

The post on X button now opens the composer with the edited draft, preserving human review and avoiding autopost.

The share modal now explains that X opens for human review, with no autopost and no new token in the browser.

The caption sent to the composer is kept compact so the public link is preserved and the post does not become too long.

The examples page now has a three-step guide to choose a clear scene, compare fidelity, and only then scale the batch.

After understanding what to inspect in examples, visitors find a direct prompt to test their own scene or review plans.

A new band summarizes the path: validate without a card, enter Starter with 30 monthly credits, then grow into Solo, Plus or Pro when volume increases.

Starter's value appears before the full plan comparison, helping architects understand R$39/mo or $7.99/mo without changing checkout behavior.

While reviewing a recent render, users now find the sharing shortcut on the image card itself, next to open, download and choose for delivery.

If the project is still private, ArchScene points users to public profile setup before opening any social composer.

Starter is now covered by the subscription contract and the price variables needed to activate checkout in USD or BRL.

If a price is not active in the current environment, ArchScene shows a human explanation instead of exposing internal Stripe details.

Visitors can switch between all examples, living/suites, kitchens, balconies and outdoor areas using the same real project and render pairs.

Each card explains which fidelity cue to inspect, helping architects decide whether to test ArchScene with their own image.

O Starter aparece em /precos e no billing com preco em USD/BRL, creditos mensais, custo por credito e caminho claro para evoluir quando o volume de renders crescer.

Architects who try to open the gallery now see a clear prompt to sign in and return directly to the visual workbench instead of a generic projects message.

Email, password, remember-me and submit controls stay briefly disabled during initial hydration, so the browser no longer falls back to a native POST to /login.

Clicking the card image opens the enlarged viewer, with a visible mobile button, position counter and previous/next navigation.

The modal supports Esc, keyboard arrows and backdrop close; the side panel scrolls on small screens and can download source images too.

Public support is for general help, access, billing, and security; project cases are directed to the authenticated chat.

When an account is already active in the browser, the page sends users to authenticated support so history, files, and credits stay in context.

The signup page compresses repeated reassurance copy on phones so the primary button stays reachable without a long scroll.

When Google is not enabled in an environment, ArchScene explains the email fallback instead of silently hiding the social path.

Selected renders now show the associated project as the title while keeping the render label as supporting visual context.

Alt text, links, embed and print views include project context so public portfolios feel more professional for clients.

The account menu, sidebar account card and dashboard shortcuts now show the saved photo, with initials only as the fallback.

The sidebar now includes name, email, plan and shortcuts to account settings and the public profile.

When a valid photo is selected, ArchScene updates the local preview without clearing the file that will be uploaded on save.

Users see the selected photo immediately before publishing the profile change.

The profile action validates the file safely, catches read/upload failures and redirects back to account settings with a clear message.

The account page no longer shows raw storage URLs and the server preserves the current photo when no new image is uploaded.

Users can see the current photo, upload a new image or mark the photo for removal without handling Storage details.

Project cards on the public profile and print/PDF view no longer serialize internal names when a public presentation title exists.

Public profiles, embeds and print/PDF views now prefer the published project title before falling back to the internal workbench name.

Profile pages are safer to send to clients, partners and social networks without leaking test names.

URLs such as /jean now open for visitors without a session while reserved routes such as dashboard and admin stay protected.

Account profiles now include Founder/CEO and Developer/founder roles so product creators do not have to present themselves as architects.

The profiles page now positions architects, designers, studios and the ArchScene team as part of the product's architecture visual community.

The first admin fold on phones now highlights incidents, new signups, support and the AI queue with direct shortcuts to act.

Jobs, failures and user search now use compact cards on phones while keeping the full tables for larger screens.

Credit controls, assisted user creation and operational notices now respect the available width on narrow screens.

Dashboard and project pages now point to a static public example showing 2D, before/after review and client handoff without calling AI or using project data.

The checklist now reinforces where the user is and what action comes next, especially between creating a project and uploading the first image.

The user detail highlights whether someone stopped before project, upload or render, and the admin queue replaces technical quality values with product language.

The links card separates 2D page, 3D tour and public/private state without showing the uploaded 3D filename.

Public 2D and 3D project pages reuse beta-safe titles so internal or test names do not leak into shareable URLs.

Public tour copy replaces GLB, manifest and technical-preview language with guided review and a simple fallback to the 2D presentation.

Projects, scenes, uploads and renders with temporary-style names now appear with presentation-ready titles instead of temporary filenames or backstage language.

Result cards now describe a project-faithful profile and user-friendly quality, instead of showing model IDs or raw technical values.

Cards and queues use optimized thumbnails while the full file remains available for large preview, comparison, download and editing.

Scenes with a finished render now expose a Compare / edit shortcut without requiring the user to open the group first.

Each group now shows how many sources, renders and edits exist in that scene, so users know what they are about to review.

The search input and sorting selector received explicit accessible names for better assistive navigation and QA snapshots.

The Account screen clarifies that the ready signals belong to the public showcase, so they are not confused with the full profile-completion percentage.

The Agents screen now uses friendlier labels and formats the credit balance consistently with the rest of the product.

Project cards now show counters as images and renders instead of leaving bare numbers beside icons.

Users can switch between all, recent, selected, failed and in-progress renders without losing project-page context.

The project page now shows a delivery-selection card and highlights the chosen render in history, reducing uncertainty about which image to send to the client.

The selection button now communicates that the user is choosing the render for delivery, not just marking a generic item.

Newest renders now appear before the queue and heavier controls, so users do not have to hunt through the full history at the bottom of the page.

Each recent render shows source, status, quality and quick actions to open the result, download the image or mark it as the best delivery.

The results section is now labeled as the complete history and states that newest renders come first, reducing review confusion.

The render area now combines chosen source, default model, estimated cost, balance and confirmation in one easier-to-understand card.

The ready-to-render image list became a card grid with larger previews, quality, status, size, cost and a direct generation CTA.

Instructions reinforce that AI improves visual presentation without redesigning the project, with clearer cost and confirmation before credits are used.

Critical dashboard dates now use a stable timezone, reducing server/browser differences during hydration.

Admin lists and cards now mask emails by default, keeping sensitive data less exposed during reviews and screen sharing.

The admin now separates consumed, granted/renewed and refunded credits more clearly when tracking AI cost.

The mobile bar and admin tables gained horizontal containment to avoid accidental sideways scroll in the cockpit.

Lighting, texture, cleanup and materiality edits stay in the preservation group, reinforcing camera, layout, millwork, major materials and proportions.

You can now click the render area that needs attention and describe the change, with localized instructions to preserve the rest of the image.

The base render is now more prominent in the edit desk and the prompt reinforces that the AI must treat the approved image as the primary reference, not loose inspiration.

The gallery now prewarms covers and the first likely images for each scene, so render groups feel more immediate without downloading the full library at once.

The edit desk can generate 1, 2 or 3 versions for comparison while showing cost, balance and remaining credits before confirmation.

Adding people or humanizing a scene is separated from the default flow and warns that it may change the reading of the project.

Lighting refinement no longer suggests adding LED strips where they feel visually useful. It now enhances only visible or explicitly specified lights.

O refinamento de iluminação deixa de sugerir fita de LED onde fizer sentido e passa a realçar apenas luzes visíveis ou explicitamente indicadas.

New routes target AI architecture rendering, SketchUp AI rendering, batch rendering for architects and before/after architecture rendering.

English pages now use OpenGraph, keywords and search copy aligned with the American architecture market.

The new routes are automatically included in the sitemap, robots rules and the public AI assistant guide.

New pages explain AI SketchUp rendering, batch rendering, before/after proof and AI rendering for architecture with organic search language.

Google, Bing and assistant crawlers receive clear public paths while dashboard, APIs and auth stay out of indexing.

The site now describes ArchScene as design software with organization and FAQ data, helping search engines understand the product category.

We added a public product summary and key links so assistants and discovery engines can understand ArchScene faster.

Render edits now prioritize camera, layout, furniture, millwork, major materials and proportions before applying any visual adjustment.

One-click edits no longer suggest free floor, plant or furniture changes and now enhance existing project elements instead.

Resultados concluídos podem mostrar o render ou a cena original mesmo quando a URL assinada direta não foi gerada na primeira leitura.

O painel fica mais visual para o arquiteto acompanhar os últimos resultados sem precisar abrir cada projeto.

Resultados concluídos agora usam os buckets corretos para exibir a prévia no painel, em vez de cair no ícone genérico.

O arquiteto consegue identificar o render recente pela imagem antes de abrir o projeto completo.

Notificações de instabilidade registradas agora orientam a conferir o estado atual antes de comunicar usuários ou iniciar deploy.

O alerta deixa de usar linguagem de emergência quando o incidente já está normalizado no status do ArchScene.

Alertas automáticos agora aparecem com linguagem de operação e levam o admin para o incidente certo, sem dominar a experiência do usuário.

A página de status prioriza impacto, acompanhamento e tempo de operação, deixando o diagnóstico técnico para o cockpit admin.

O monitor reconhece melhor o slot ativo antes de avisar instabilidade, reduzindo falsos alarmes durante atualização segura.

Real signups can alert the operation team so the first project is monitored before the user drops off.

Stripe payment and renewal events now have an operational alert after the webhook confirms and records the event.

When a user opens a support thread, the team can receive a direct link and respond while the test is still warm.

The reset email now shows the ArchScene lockup, Portuguese copy and a short English fallback for international users.

The first access email explains the next studio step and reinforces that projects are private by default.

The operations runbook separates app emails from native Supabase Auth emails so inherited sender names and subjects do not return.

O primeiro email depois do cadastro usa o idioma ativo do usuário e explica créditos, privacidade, suporte e o caminho para gerar o primeiro render.

A área de conta ganhou um card de segurança para atualizar senha sem depender do fluxo de recuperação por email.

Quando o usuário começa o cadastro a partir de uma área específica, o link de confirmação preserva esse destino seguro depois do login.

A tela de recuperação agora orienta o usuário a falar com suporte caso o email não chegue em alguns minutos.

O fluxo de cadastro, confirmação e nova senha ganhou um roteiro seguro para validar caixa de email sem registrar links privados.

When users start signup from a specific area, the confirmation link preserves that safe destination after login.

The recovery screen now points users to support if the email does not arrive after a few minutes.

Signup, confirmation and password reset now have a safe validation checklist that avoids recording private email links.

The project screen now has a safer panel for copying and opening the public 2D presentation.

The 3D shortcut only appears when there is an active ready model, avoiding incomplete client links.

The public page remains useful in 2D even without a 3D model, with clear copy about what is available.

Depois de autenticar com Google, o usuário volta para archscene.com em vez de herdar portas internas usadas no deploy.

O fluxo de autenticação agora normaliza a origem pública antes de redirecionar para projetos, recuperação de senha ou login.

When the Google link expires, the login screen shows a simple retry instruction instead of a raw technical error.

Social authentication failures now become short, actionable messages for users entering the studio.

Quando o provedor estiver habilitado no ambiente, usuários podem entrar ou criar conta usando Google.

O app só exibe provedores liberados por configuração, enquanto o segredo OAuth fica restrito ao Supabase Auth.

A tela de recuperação explica que o link só é enviado quando a conta existe, sem expor dados de cadastro.

A redefinição agora orienta senhas com pelo menos 8 caracteres e mensagens de erro mais claras.

Textos internos e sem acento foram trocados por mensagens prontas para usuários beta.

If a temporary preview is misconfigured with a live key, checkout, the billing portal and subscription changes are blocked.

The recommended flow now clearly separates visual preview, local testing and VPS production.

The team has a short checklist for validating landing, login, status, health and billing without mixing environments.

Primary actions and icon buttons now respect more comfortable minimum target sizes for mouse, trackpad and mobile.

Selecting, enlarging, opening menus and using batch actions is less cramped on dense cards.

Operational links and helper labels gained visible focus, better contrast and less exaggerated spacing.

The navigation balance now uses the same localized number format used in billing and project screens.

Render counters in the gamification card and public proof stats now follow the active language.

The edit drawer shows current balance and remaining balance with the right EN/PT number format.

Saldos, totais e movimentações agora seguem o formato do idioma ativo, incluindo data e hora no histórico.

Auditor, onboarding e playlists usam contagens localizadas em mensagens de custo, progresso e confirmação.

Chaves do plugin mostram criação e último uso com data e hora no formato correto para EN/PT.

Métricas do dashboard e da lista de projetos agora respeitam o formato de milhares do idioma escolhido.

Projetos e usuários no admin passam a mostrar datas com ano completo, reduzindo dúvida em revisões de beta.

Os passos de instalação do plugin SketchUp agora acompanham EN/PT em vez de ficarem fixos em português.

Quem visita pelo celular agora consegue começar grátis ou voltar aos exemplos sem procurar o botão no meio da página.

O hero ganhou uma dica clara para comparar cena do SketchUp e render final no before/after.

Blocos secundários ficam mais discretos no mobile e uma faixa resume prazo, revisão, arquivos aceitos e créditos protegidos.

O hero de preços agora oferece começar com 5 créditos grátis antes de pedir decisão de plano.

A página explica que 1 render padrão usa 1 crédito, preparação SKP não consome IA e falhas técnicas devolvem crédito.

Os botões dos planos ficaram menos agressivos e os cards mostram o custo aproximado por crédito.

O plano atual agora mostra o saldo disponível, os créditos que renovam todo mês e os créditos extras em blocos separados.

Os botões anuais indicam a economia aproximada em meses, reduzindo dúvida entre mensal e anual.

A página explica que o portal serve para trocar plano, atualizar cartão, cancelar e baixar faturas.

Mensagens como usuários, alvos, eventos, lotes e falhas agora aparecem com plural correto em vez de formatos com parênteses.

Alertas de fila IA e saúde do sistema usam números formatados para leitura rápida durante operação do beta.

Os nomes dos projetos podem ocupar até duas linhas antes de cortar, ajudando a reconhecer obras com nomes longos.

O selo de status saiu da mesma linha do título para não competir com o nome do projeto.

Em telas largas, a lista usa quatro colunas quando couber e reduz o efeito de card isolado na segunda linha.

O botão principal agora indica se o próximo passo é enviar imagens, gerar render ou revisar resultados prontos.

Painel, projetos, galeria e playlists ficam no grupo principal; auditor, agentes, faturamento, suporte, status e admin aparecem em áreas próprias.

O item aberto na lateral ganhou contraste e marcador mais forte, incluindo faturamento e status.

O botão de compra agora deixa claro que leva ao saldo de créditos, reduzindo ambiguidade no topo do app.

Logo, selo e chamada principal agora ficam alinhados ao centro do container esquerdo no desktop.

A pré-visualização antes/depois mantém proporção e respiro dentro do painel, sem competir com o formulário de entrada.

A confirmação ao sair da conta volta a exibir acentuação correta na tela de login.

O painel de entrada foi compactado para caber melhor na primeira tela em notebooks e monitores menores.

O CTA de transformações agora abre os oito comparativos na própria página inicial, mantendo o visitante no fluxo.

A comparação em tela grande agora carrega as imagens internas da galeria sem cair no erro de visualização.

The dashboard now prioritizes next action, essential metrics and render queue before progress blocks.

Goals, achievements, leaderboard, streak and heatmap live inside an expandable block to reduce initial scrolling.

Active renders and failures are separated from the latest completed results, reducing repetition on the main dashboard.

When a result or source image is available, the queue shows a thumbnail so users can recognize work faster.

Job and result IDs moved out of the main card body and remain only as technical item details.

Recent jobs no longer rely on short dates like 05/07 and instead show less ambiguous localized dates.

Metrics, refunded credits, queue position and image counts now follow the active language formatting.

When the interface is in English, Billing now shows dates like May 17, 2026 instead of ambiguous numeric dates.

Wallet messages and visible internal labels no longer show broken Portuguese accent encoding.

Number, date and credit helpers reduce the chance of future screens falling back to raw formats.

Instead of sending every large image through the main endpoint, ArchScene now issues a signed URL and the plugin uploads the scene directly to Storage, then registers it in the project.

The previous multipart endpoint remains available as a fallback for users who have not updated the exporter yet.

The flow preserves temporary code, scene, materials, file size, dimensions and project context so the dashboard stays in sync without routing the full file through the app server.

Um cron protegido registra snapshots de produção e usa os sinais do /status para acompanhar o funcionamento do produto.

Quando a fila de IA trava, o banco falha ou o servidor entra em atenção, o sistema cria ou atualiza um incidente operacional para o admin agir rápido.

Admins recebem aviso interno quando o monitor detecta degradação, com cooldown para evitar ruído durante o beta.

The notifications screen shows audience, type, severity, delivery channels and message appearance before dispatch.

Visible copy now uses clearer message language instead of internal broadcast terminology while keeping history and auditability.

Sending to a specific user now has clearer labels and empty states for support follow-up.

Real signups now create an internal admin notification without blocking signup if the alert cannot be delivered.

The notification opens the admin user detail, where the team can review profile, credits, projects, history and next steps.

Test emails and admin accounts are ignored by the automatic alert so the cockpit stays focused on real users.

Cost, insufficient-balance, render-confirmation and refund messages no longer show prototype placeholders. They now read as natural product copy.

Gallery, playlists, SKP import and plugin uploads now describe scenes, images and renders with cleaner count labels for architects.

Partial reception, scene limits and SKP import notices now explain the real state without odd abbreviations or technical copy.

The 'Scenes & sources' tab is separated from 'Renders & edits'. Multiple results from the same scene now appear in a collapsible group with a cover image and count, so users can scan scenes quickly and open only what matters.

The editing bench opens in quick-edit mode with 8 one-click adjustments, including warmer light, golden hour, cleanup, more greenery, minimal styling and realistic textures. The detailed 'Describe change' mode remains available.

The gallery header is leaner, repeated filters were combined, view controls are integrated with search, and batch actions stay close while items are selected.

The gallery mounts fewer images on first load and lets users load more items on demand, making the first navigation lighter for accounts with many scenes and renders.

Every credit-spending flow now shows the same simple calculation: cost, current balance and balance after the action.

Fixed text that could disappear in dark and sepia themes. Theme switching is instant, and the notification badge clears correctly when opened.

Keyboard focus is visible across gallery controls, reduced-motion preferences are respected, and the theme switcher uses localized labels.

Botão Compartilhar no header do projeto abre modal com link público copiável + envio rápido pra WhatsApp, LinkedIn, X, e-mail e legenda pronta pro Instagram.

Botão Apresentar abre os renders do projeto em fullscreen com setas pra navegar, auto-advance opcional, thumbnails de pulo rápido e atalhos de teclado.

Cada render tem botão Refinar que abre um modal com 5 ajustes de luz (LED, luz quente, spots/sancas, mais luz natural, cena noturna) — re-renderiza preservando layout, materiais e composição. Custa 1 crédito.

Click no título do projeto vira input editável com Enter pra salvar e Esc pra cancelar. Optimistic UI mostra o novo nome imediato.

Compartilhar link de projeto público no WhatsApp/LinkedIn agora gera uma OG card 1200×630 com cover image, título, nome do arquiteto e brand ArchScene.

/login/forgot-password e /login/reset-password agora têm logo ArchScene clicável + trust strip explicando o fluxo, em vez de um card isolado sem contexto.