scripts/generate-content-types.ts writes the gitignored src/types/content-ids.ts (id unions + project category values) from the four structure documents; wired as generate:ids / predev / prebuild / prepare. src/types/index.ts re-exports them type-only and keeps only the code-owned unions.
Edit mode now writes JSON only: the v4 union leg is deleted (saveIdUnions, diffIdsWithUnions, applyUnionChanges, readUnionBlock, the EditBar union card, edit.union.* labels). Validator rule 7 requires a label for every category a project uses, in both ui/projects.json documents.
Tests: smoke-draft.ts 11/11 (rename re-sluging + category-label rule replace checks 9-12); new scripts/smoke-generated-ids.ts 7/7. Verified: pnpm build (chunk names unchanged, no runtime reference to the generated module), lint with no new warnings, validate:content, resume HTML byte-identical before/after with identical documents.
Docs: spec-v5-generated-content-ids.md added; spec-v4-live-edit.md §3.1 marked superseded + §12 row 23; AGENTS.md and README.md updated.
Deleting a record in edit mode removed the structure row and its text but left the id union member in src/types/index.ts, so Record<SkillGroupId, SkillGroupText> rejected the shortened text document (TS2741) and pnpm build failed. draft.ts: readUnionBlock reads a union as its declaration span (CRLF/LF safe, never round-trips), diffIdsWithUnions reports missing and stale members against committedStructures(), applyUnionChanges rewrites only that member list in one PUT; newIdsInCommitted/patchUnionSource removed. types/index.ts drops logistics-technology. Verified: smoke-draft 12/12 (new checks 9-12), validate:content, lint (no new warnings), build.
- compose.yaml: set -a before sourcing (sourced assignments were shell-only, envsubst saw nothing) + inline nginx command (a compose entrypoint override drops the image CMD; empty $@ exit-0 restart-looped locally and on the VPS)
- compose.override.yaml: local-only auto-merged override publishing 127.0.0.1:8081 (8080 taken on the dev machine); never shipped by the pipeline
- verified locally end-to-end: stack Up, probe 200, rendered default.conf carries real values, nginx -t OK; built site + 401-protected /api/content/ served through the published port
- docs: spec D13/§4.1 entrypoint corrected, §6 port-exposure open question + docker inspect check, rows 4/9; README local-stack section; AGENTS.md inventory
Run 3 failed at the test step: nginx's official entrypoint matches NGINX_ENVSUBST_FILTER as a regex against variable names (^filter$), so the comma form GITEA_TOKEN,GITEA_CONTENTS_API matched nothing — ${…} tokens stayed in the rendered config and nginx -t failed with 'unknown "gitea_contents_api" variable'. A literal hostname in proxy_pass is resolved during the config test, so the test placeholder must be a resolvable literal IP. Both reproduced and fixed locally against the repo files: the exact test-step container now passes nginx -t (exit 0). compose.yaml + deploy-infra.yml use GITEA_TOKEN|GITEA_CONTENTS_API (quoted in the shell script) and http://127.0.0.1:1. Spec rev.8: status line, D11, §4 sketch + resolved note, rows 2/4.
Run 2026-10-23 shipped files to dong-site/workspace/dong.nguyen/cv/… on the VPS: the action builds the rsync source as "/" (entrypoint.sh) and -R mirrors that absolute path; deploy/htpasswd also landed as a directory. Each step now uses plain -avz with an explicit remote_path (dong-site/ for nginx.conf + compose.yaml, dong-site/deploy/ for htpasswd). Spec §4 sketch/notes resolved, §8 rows 2/4 record both run outcomes and the owner-side VPS cleanup before the next dispatch.
First real run 2026-10-23: burnett01/rsync-deployments passes the comma-list path input to rsync as one quoted argument — link_stat "nginx.conf,compose.yaml,deploy/htpasswd" failed, nothing shipped, live container untouched. Apply the spec §4 fallback: one rsync step per file with full remote_* config, -avzR kept. Spec: §4 sketch + inference note resolved, §6 paths-filter risk annotated, §8 rows 2/4 record the run outcome and the re-run-via-dispatch step.
Repo side of spec-v4-deploy-infra: deploy-infra.yml (paths-filtered nginx redeploy, test-before-touch, health probe); compose.yaml rename + secrets/site_config entrypoint override; site identity externalized - SITE_URL/SITE_NAME read from env (site.ts, vite site-identity plugin, index.html tokens, generated robots.txt); nginx.conf/vite dev proxy read GITEA_CONTENTS_API; .env.example; AGENTS.md + specs updated. Rev.7: site identity delivered as Gitea Actions variables (vars. context, public values) instead of secrets; upload-artifact unified to v7 across jobs.
Gitea 28 decides create-vs-update solely by the body 'sha' (blob ID): empty sha -> create (422 'already exists' on an existing file), stale sha -> 422 'does not match'. The client sent last_commit_sha, which Gitea 28 bodies ignore - every save was a CREATE, so nothing ever reached the branch. fetchDoc/putBase64 now carry the file's blob sha, save reads the new sha from FileResponse.content.sha, and save-conflict detection accepts 412 (older Gitea) or 422 with a 'does not match' message; other 422s stay a hard failure with resume. Spec 6.1 amended with dated note; AGENTS.md DraftStore line aligned.
A first tag commit on a text document that does not hold the array yet
(an older target branch, e.g. profile.currentInterests still living in
the structure document) built an object {"0": …}; the join then overrode
the structure array with it and items.map crashed on the re-render.
setPath now creates [] for [n] segments under an undefined root.
smoke-draft check 8 reproduces the old-baseline tag edit (8/8 pass).
Tag dropped every prop beyond children/accent/className, so the editing
surface EditableText attaches (ref, contentEditable, key/blur handlers)
never reached the span: tags rendered through as={Tag} — interests,
philosophy keywords, project-detail technologies — showed a pencil but
never became editable (React 19: ref is a plain prop the component must
declare). Tag is now a pass-through; visitor markup is unchanged.
Row 18: ui.about.subtitle/experience.tldrText/philosophy.quotes -> profile.subtitle/.tldr/.philosophyQuotes in content.{vi,en}.json; call sites repointed with EditableText wrap; SectionHeading subtitle prop becomes ReactNode; edit.fields labels added. Row 19: experience.company/.duration, projects.role/.metrics, profile.currentInterests/.roles, philosophy keywords move to text documents; VI carries localized dates/company labels/metrics, en overrides with originals, proper nouns and term lists identical (en omits); draft templates, JsonPanel hints, loader comments, resume TL;DR follow the new shapes. Verified: build, validate:content, lint (no new warnings), smoke-draft 7/7, per-language SSR marker smoke on affected routes, build:resume-all.
?edit entry with Basic-auth probe; DraftStore copy-on-write over live
branch documents (?ref GET / branch PUT, last_commit_sha optimistic
concurrency, three-way rebase on 412); EditableText inline editors;
JsonPanel with templates and orphan-free delete; EditBar sequential-PUT
save with conflict actions and merge hint on non-master branches.
scripts/smoke-draft.ts regression check.
Phase 1 of spec-v4-live-edit: data/i18n foundation, no visible feature.
- src/data/{profile,skills,experience,projects}.json: language-neutral
structure documents with thin typed loaders; all prose moved to
src/i18n/locales/{vi,en}/content.json; chrome strings to ui.json
- src/i18n/: dict-types, cross-document validator (runs at module load and
via pnpm validate:content), loader joining structure+text once (UI/CONTENT),
I18nProvider/useI18n mounted in App under LanguageProvider
- all 22 consumers read joined records via useI18n(); field.ts and
strings.ts deleted; *En field pairs removed from the domain types
- hero tagline renders as plain-text segments (D9); philosophy quotes as
paragraph arrays; footer display name now localizes per language (D6)
- resume generator consumes UI/CONTENT; generated resume HTML verified
byte-identical (EN+VI) before/after the migration
- AGENTS.md and v3/v3-i18n + v4 specs updated; deploy.yml concurrency group
No code referenced the asset — ResumeIcon in src/components/ui/icons.tsx inlines the same geometry, which is required for currentColor theming. Update the icons.tsx comment and AGENTS.md to drop the file pointers; spec follow-up history left intact.
Drawn from .timeline-marker::after rather than from the entry or the header, because the current-role entry pads its own content box while the marker is pinned to the spine: left 10px, top 3px, width 24px on the 36px gutter (16px on the 28px mobile gutter) — the same x 12 to x 36 arithmetic .timeline-tldr::after already uses. The link carries the node's own ink: --border-strong for an ordinary ring and the gap node, --accent for the two ends of the timeline (the first node and the TLDR diamond, whose link already exists), and it follows the ring through the hover transition. The current-role link stops at the panel's accent edge (x 28 desktop, x 24 mobile). Spec: spec-ui-experience.md, new §Node → Title Link.
.mobile-menu-icon-option.active gains color: var(--accent), so the sheet's Language and Mode glyphs follow data-theme/data-palette the way the bar's .nav-control.open already does. Palette dots paint their own --preview-*-accent and are unchanged; :hover keeps its fill-only behaviour. Recorded as Q19 in spec-v3-mobile-navigation.md.
- Extract SunIcon/MoonIcon from the bar theme control into src/components/ui/icons.tsx
(exact geometry and attributes, so the bar renders identically)
- MobileMenu Mode row: Dark option draws MoonIcon, Light draws SunIcon in the
.mobile-menu-icon-option square the Language and Theme color rows use,
aria-pressed + translated aria-label/title
- Delete .mobile-menu-segment-option (3 rule groups) from App.css — last user gone
- AGENTS.md picker paragraph, spec-v3-mobile-navigation.md (Q18 + progress row),
spec-v3-i18n.md cross-reference updated
- ResumeIcon: split page outline with a visible left-edge dash and stroked CV
lettering (owner's 30-grid draft adapted to the 24 grid, spec follow-up 19),
rendered at 24px matching the home glyph inside the 44px target
- ResumeDialog: portal to document.body — the fixed overlay anchored to the
bar's backdrop-filter containing block instead of the viewport;
useClickOutside takes an exclusion ref for the portaled panel
- .nav-resume-trigger: glyph is --accent at rest/hover/open, follows both
theme axes
- .nav-brand: gap 12px -> 4px (borderless icons read glyph-to-glyph); the
420px media rule only drops the bordered action gap to 8px
- public/cv-icon.svg rewritten as the canonical glyph; AGENTS.md and
spec-v3-resume-redesign.md (follow-ups 19-23) updated
One trigger at every width opens the language dialog: the details dropdown markup, its CSS, both chevron rules and the hero-download desktop/mobile variants are gone, and @media (max-width: 768px) lets the trigger fill the CTA column like the other two buttons.
The trigger carries an open class so the :hover accent fill does not fire at the click instant behind the overlay, and the scrim is a plain colour mix instead of backdrop-filter: blur(4px), which used to repaint the page under the fading overlay. transition: all became explicit background/color transitions.
The lazer split was geometric: inset: -200% resolved against the wrapper, so the rotating layer measured 1710x265 for the 342x53 mobile wrapper, and once its short half-side (132.5px) is narrower than the wrapper half-diagonal (173px) the layer stops covering the wrapper's own edges, cutting the beam in two for part of every cycle (14/72 angles). Both layers are now inset: 0 and the spin animates a registered @property --lazer-angle (0deg -> 360deg) instead of rotating a box: 1 lit segment at 72/72 angles on both 342x53 and 167x53, same 4s cycle, and the blurred glow layer shrinks to the wrapper box.
Also carries the nav chrome this feature needs: .nav-resume, the borderless .nav-resume-trigger (border-color transparent at rest, hover and open, matching the home icon beside it while keeping the 44px target, hover fill and :focus-visible ring), and the 420px gap plus new 360px padding tightening so six controls fit a 320px viewport. AGENTS.md and docs/design/specs/v3/spec-v3-resume-redesign.md follow-ups 13-17 record all of it.
ResumeNavButton is the third item in .nav-brand, right after the home icon: a 44px icon target named by strings.nav.resume, aria-haspopup=dialog on its own #resume-modal-nav, gated on resumeAvailable.
The picker markup is no longer duplicated. ResumeDialog owns the overlay, panel and resumeLanguages options and takes a dialogId, so the hero keeps #resume-modal and the bar gets #resume-modal-nav. useResumeDialog holds the state both triggers share: open flag, container/trigger/panel refs, click-outside (close guarded on openRef, because the listener is live while closed and otherwise steals focus on every page click), Escape, body-overflow lock and focus return. Panel focus moved from onAnimationComplete to a one-frame effect: AnimatePresence keeps open=true on the exiting copy, so the old handler refired at the end of the exit and stranded focus on <body>. resumeAvailable now gates the leaf components, so Hero renders <DownloadResume /> plainly.
- site: Zalo removed from SocialId, Profile, social.ts, ContactLinks, strings and
icons.tsx; the resume QR block keeps Zalo by owner decision
- resume: .header-photo 72 -> 96px, .header-info margin-left 12 -> 24px,
.header-qr gap 18 -> 50px so the Telegram code sits clear of Zalo
- contact: <DownloadResume /> removed from the Contact section and ContactPage;
DownloadResume() + DownloadButton() and the dead .download-resume-button rule
deleted, Hero CTA untouched
New spec-v3-review-fixes.md carries the findings, the per-bundle implementation detail, the affected-file list, the out-of-scope table including the declined resume.pdf bundle with its measured 200 text/html probe, the gate numbers and the commit record. spec-v2-seo.md acceptance is now honest: robots, sitemap, JSON-LD and canonical are done, per-route title/description/OG remain open because the SPA serves one head for every route. spec-v2.md statuses no longer contradict shipped work. AGENTS.md drops both barrels, documents the pure field() helper, the canonical origin module, the sitemap build step and the lazy/default-export gotcha.
Typewriter reads useReducedMotion: under reduced motion the timer never starts and the first role renders whole, while a screen-reader-only span exposes the full role list once instead of one keystroke at a time. BackToTop scrolls instantly under reduced motion and is labelled in the active language; the nav landmark and the mode toggle stop being English-only. The hero photo declares its measured 1200x1600 canvas plus fetch priority so the box is reserved before the 898 kB image decodes. HomePage stays eagerly imported because it owns the LCP; the other six routes lazy-load behind one Suspense boundary, which is also why the pages barrel is gone.
index.html advertised nothing: no title, no description, no Open Graph, no canonical. The head now carries both theme-color values, an OG block with an absolute 1200x1600 image, a Twitter card and a Person JSON-LD block with sameAs and a PostalAddress. src/data/site.ts holds the canonical origin; generate-sitemap.ts writes dist/sitemap.xml from navPaths plus the project list (10 urls) and fails the build if dist/index.html no longer contains siteUrl, because an HTML head cannot import TypeScript and the origin is therefore written twice by hand. Chained into pnpm build so dist/ is complete before the deploy workflow uploads it.