summaryrefslogtreecommitdiff
path: root/frontend/src/styles/mobile.css
diff options
context:
space:
mode:
authorsoryu <soryu@soryu.co>2026-04-28 21:26:11 +0100
committerGitHub <noreply@github.com>2026-04-28 21:26:11 +0100
commit5bde7c2d7e099fd9c8b2615602ab1d096bd9b6be (patch)
treed605f7c02472f67a88f1c71c9258c1bf0823b44a /frontend/src/styles/mobile.css
parentd1fdfb140cc440664f77a24886172f9976a05a31 (diff)
downloadsoryu-5bde7c2d7e099fd9c8b2615602ab1d096bd9b6be.tar.gz
soryu-5bde7c2d7e099fd9c8b2615602ab1d096bd9b6be.zip
revert PRs #93-#98; enforce strict-linear-DAG + mandatory directive verify (#100)
* revert: roll back PRs #93-#98 to pre-Lexical baseline Reverts the entire chain of directive document UI work and the homepage redesign, restoring the working tree to the state at 3679ceb (before c8b169d / PR #93). PRs reverted: - #93 c8b169d feat: Document UI for directive orchestration with Lexical editor - #94 d6f01a6 fix: compilation error and warnings already merged via PR #93 - #95 5aa3faf fix: resolve compilation error and warnings in Rust backend - #97 d513f93 feat: document UI with contract blocks, expandable logs, and interaction controls - #96 6366941 feat: Redesign homepage with professional PC-98 styling - #98 d1fdfb1 feat: revert broken directive PRs, re-implement Lexical document orchestrator The directive Document UI experiments produced fragile output and merge artifacts; follow-up commits in this PR change orchestration to favor strictly linear DAGs and add goal/conflict verification so future runs do not require this kind of cleanup. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * feat(directive): strict-linear-DAG planning + mandatory `directive verify` Tightens directive orchestration so the final PR almost never needs a hand-merge: 1. Planning prompts now strongly bias toward strictly linear DAGs. Parallel steps are reserved for genuinely independent work (e.g. disjoint modules); the default for "in doubt" is sequential. Linear chains inherit each previous step's worktree, so the final merge is typically just a rebase against the base branch. 2. New CLI command `makima directive verify` does a local in-memory `git merge-tree` of HEAD against `<remote>/<base>` and exits non-zero with a list of conflicting files if the PR would not merge cleanly. Pure-local — no API call, no working-tree mutation. 3. Completion / PR-creation prompts now mandate three pre-push checks: a. build (`cargo check` and/or `tsc --noEmit`), b. `makima directive verify --base <base_branch>` must exit 0, and c. an explicit goal-alignment self-check against the diff. The orchestrator is told NOT to push, create the PR, or call `makima directive update` until all three pass. Skipping any of them is documented as a directive failure. The combination means that with a linear DAG the final PR-creation task should almost never see a real conflict — when it does, that is treated as a planning bug to escalate rather than something to paper over with `-X theirs`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(frontend): TS errors pre-existing on master - TaskSlideOutPanel: declare missing `selectedFileDiff` / `selectedFilePath` state hooks that were referenced everywhere but never created, and re-balance the JSX so the `<>...</>` fragment in the non-diff branch is closed (the previous indentation/braces would not parse). - api.ts: add a `getWorktreeDiff` thin wrapper around `getTaskDiff` so TaskDetail's per-file click handler type-checks (the per-file slice is a future improvement; today both return the full task diff). - WorktreeFilesPanel: remove unused `isClickable` local; the gating already reads `onFileClick` directly inline. Run after revert: `npx tsc --noEmit` exits 0. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Diffstat (limited to 'frontend/src/styles/mobile.css')
-rw-r--r--frontend/src/styles/mobile.css108
1 files changed, 0 insertions, 108 deletions
diff --git a/frontend/src/styles/mobile.css b/frontend/src/styles/mobile.css
index 7d1f282..c1c524d 100644
--- a/frontend/src/styles/mobile.css
+++ b/frontend/src/styles/mobile.css
@@ -51,112 +51,4 @@
.makima-inline-icon { width: 16px; height: 16px; margin-left: 6px; }
.makima-list { gap: 4px; }
.makima-list li { font-size: 12px; line-height: 1.45; }
-
- /* ================== Professional Landing Page – Mobile ================== */
-
- /* Compact header */
- .pro-header-content {
- padding: 0.45rem 1rem;
- }
-
- .pro-company-name {
- font-size: 0.85rem;
- letter-spacing: 0.12em;
- }
-
- .pro-crane-logo {
- height: 28px;
- }
-
- /* Hide center heart on small screens to save space */
- .pro-header-center {
- display: none;
- }
-
- /* Full-width nav buttons */
- .pro-header-nav {
- gap: 0.15rem;
- }
-
- .pro-nav-link {
- font-size: 0.7rem;
- padding: 0.3rem 0.5rem;
- }
-
- .pro-nav-login {
- margin-left: 0.25rem;
- }
-
- /* Hero – reduce heading size and padding */
- .pro-hero {
- min-height: 85vh;
- padding: 5rem 1.25rem 3rem;
- }
-
- .pro-hero-headline {
- font-size: clamp(1.4rem, 5.5vw, 2rem);
- }
-
- .pro-hero-sub {
- font-size: 0.9rem;
- margin-bottom: 2rem;
- }
-
- .pro-hero-tagline-jp {
- font-size: 0.75rem;
- letter-spacing: 0.35em;
- }
-
- .pro-hero-cta {
- flex-direction: column;
- align-items: stretch;
- }
-
- .pro-btn-primary,
- .pro-btn-secondary {
- width: 100%;
- text-align: center;
- justify-content: center;
- }
-
- /* Stack cards to single column */
- .pro-content-grid {
- grid-template-columns: 1fr;
- padding: 0 1rem 3rem;
- gap: 1.5rem;
- }
-
- .pro-card-header {
- padding: 1rem 1.25rem 0.6rem;
- }
-
- .pro-card-body {
- padding: 0.6rem 1.25rem 1.25rem;
- }
-
- .pro-card-title {
- font-size: 1rem;
- }
-
- .pro-card-subtitle {
- font-size: 0.88rem;
- }
-
- .pro-card-text {
- font-size: 0.8rem;
- }
-
- .pro-makima-logo {
- width: 48px;
- height: 48px;
- }
-
- /* Footer compact */
- .pro-footer {
- padding: 1.25rem 1rem;
- }
-
- .pro-footer-inner {
- font-size: 0.7rem;
- }
}