Jakob WennbergandClaude Sonnet 5
ec27228a8e
Em dashes (—) and en dashes (–) had spread across comments, docs, tests, and a few UI strings, reading as AI-generated boilerplate rather than house style. Replaced each with punctuation matching its context: colon for explanatory clauses, comma for asides, plain hyphen for numeric/legal ranges (e.g. "21-23§"), "to"/"till" for date ranges, parentheses for paired-dash asides. messages/en.json and messages/sv.json were fixed by hand together to keep sv/en in sync. Left untouched where the dash is the functional subject rather than decorative punctuation: date-range-parser.ts's separator regex, charset-repair.ts's CP1252 byte-mapping table (and its test), the SIE encoding mojibake docs, generic-csv.ts's minus-sign normalizer, the agent system-prompt files that already instruct against em dashes, and a golden iXBRL test fixture compared byte-for-byte. Also fixes two bugs surfaced along the way: an off-by-one in ApiKeysPanel's scope-label split (a leftover from an earlier partial pass), and a charset-repair test that had lost the literal en-dash it exists to verify. Regenerated the agent atom seed migration (skills:generate) since 27 SKILL.md files changed. Added a CLAUDE.md rule against em/en dashes, with an explicit carve-out for the functional-dash cases above. Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
37 lines
1.7 KiB
TypeScript
37 lines
1.7 KiB
TypeScript
import { createClient } from '@/lib/supabase/server'
|
|
import { redirect } from 'next/navigation'
|
|
import { getActiveCompanyId } from '@/lib/company/context'
|
|
import ChatNewStarter from '@/components/agent/ChatNewStarter'
|
|
import { getIntent } from '@/lib/agent/intents/registry'
|
|
|
|
export const dynamic = 'force-dynamic'
|
|
|
|
interface PageProps {
|
|
searchParams: Promise<{ intent?: string; prompt?: string }>
|
|
}
|
|
|
|
// /chat/new: generic conversation bootstrap. Reads ?intent= and ?prompt=
|
|
// from the URL and mounts AgentChat in fresh mode; AgentChat creates the
|
|
// conversation server-side on first invoke and the client swaps the URL
|
|
// to /chat/[id] when the id streams back. Mirrors /chat/intake but with
|
|
// caller-chosen intent/seed, so suggestion chips and ⌘K can route here
|
|
// inline instead of opening the slide-in sheet.
|
|
export default async function ChatNewPage({ searchParams }: PageProps) {
|
|
const supabase = await createClient()
|
|
const { data: { user } } = await supabase.auth.getUser()
|
|
if (!user) redirect('/login')
|
|
|
|
const companyId = await getActiveCompanyId(supabase, user.id)
|
|
if (!companyId) redirect('/onboarding')
|
|
|
|
const sp = await searchParams
|
|
const requested = typeof sp.intent === 'string' && sp.intent.trim() ? sp.intent.trim() : 'general.help'
|
|
// Validate against the registry: a bogus ?intent= would otherwise render the
|
|
// chat shell and then fail at invoke with a 400, which reads as "Anna is broken"
|
|
// rather than "bad link". Fall back to general help instead.
|
|
const intent = getIntent(requested) ? requested : 'general.help'
|
|
const prompt = typeof sp.prompt === 'string' ? sp.prompt : ''
|
|
|
|
return <ChatNewStarter intentId={intent} seedUserMessage={prompt} />
|
|
}
|