bvandeusenandClaude Opus 5.5
bdd803537b
CI & Build / Python lint (push) Successful in 9s
CI & Build / Plugin hooks (push) Successful in 22s
CI & Build / TypeScript typecheck (push) Successful in 1m0s
CI & Build / integration (push) Successful in 1m55s
CI & Build / Python tests (push) Successful in 2m20s
CI & Build / Build & push image (push) Successful in 1m7s
Components, stores, api clients, router, types and shared CSS now state what each piece is and why, without the milestone that introduced it. diff.ts names its consumers instead of the copy history; stores/notes and tasks state their current scope instead of the cleanup that set it; theme.css states the token practice instead of the sweep that established it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
56 lines
2.1 KiB
CSS
56 lines
2.1 KiB
CSS
/* Shared by the rules panes (RulebookListPane, RuleListPane,
|
|
RulebookDetailPane, RuleSweepPane): the pane surface, its heading, and the
|
|
title chip. Counting them in this comment went stale the first time a
|
|
fourth was added, so it no longer does. Load with
|
|
<style src="@/assets/rules-shared.css" /> beside the component's own
|
|
scoped block; never restate these there (#2903, milestone 299). */
|
|
.pane {
|
|
background: var(--fs-surface-hover);
|
|
padding: 1rem;
|
|
overflow-y: auto;
|
|
}
|
|
.pane header h2 {
|
|
font-family: Fraunces, serif;
|
|
font-style: italic;
|
|
margin: 0 0 0.5rem 0;
|
|
}
|
|
.form-buttons { display: flex; gap: 0.5rem; }
|
|
|
|
/* A small marker beside a rule's title. Two of these appeared within one
|
|
milestone (tier, then verification) and were byte-identical; a third would
|
|
have drifted. The pane's italic serif title is inherited by anything inside
|
|
it, so the chip resets family and style explicitly. */
|
|
/* A rule with no trigger cannot be retrieved, and retrieval is the only
|
|
delivery — so this marks a rule that will never
|
|
reach a session. Warning rather than error: the rule is not broken, it is
|
|
unreachable, and the fix is one field away. */
|
|
.rule-chip-inert {
|
|
color: var(--fs-warning-fg);
|
|
background: color-mix(in srgb, var(--fs-warning) 12%, var(--fs-surface-raised));
|
|
}
|
|
|
|
.rule-chip {
|
|
margin-left: 0.4rem;
|
|
font-family: var(--fs-font-body);
|
|
font-style: normal;
|
|
font-size: 0.62rem;
|
|
color: var(--fs-text-secondary);
|
|
background: var(--fs-surface-raised);
|
|
border-radius: var(--fs-radius-pill);
|
|
padding: 0.05rem 0.4rem;
|
|
vertical-align: middle;
|
|
}
|
|
|
|
/* A PREFERENCE, marked because force is the one thing a list of instructions
|
|
must not leave the reader to infer. A preference does not bind — ignoring it
|
|
costs consistency, not correctness — and it is the one kind the agent
|
|
rewrites on its own, so a row that renders identically to a rule teaches the
|
|
opposite of both facts.
|
|
|
|
The accent, not the warning colour: nothing is wrong with a preference. It
|
|
is a different KIND, and the marker says which. */
|
|
.rule-chip-preference {
|
|
color: var(--fs-accent);
|
|
background: var(--fs-accent-soft);
|
|
}
|