paneltir 0.7.0 → 0.9.0

package/CLAUDE_MD_SNIPPET.md

@@ -39,11 +39,26 @@ library shared with other projects. Rules:
   The password, the GitHub token and the target repository are environment
   variables where this project is hosted — never in this repository.
 - **The panel explains itself once.** New readers get a short guided tour the
-  first time they open the board; each note is dismissed and stays dismissed,
-  per browser. **Help** in the header reports what the panel needs — the
-  password, the GitHub token, the target repository — with what is missing and
-  the steps to fix it, asked from the server so it reports the truth rather
-  than a guess. "Show the guide again" in there brings the tour back.
+  first time they open the board; each note is dismissed and stays dismissed.
+  **Help** in the header reports what the panel needs — the password, the
+  GitHub token, the target repository — with what is missing and the steps to
+  fix it, asked from the server so it reports the truth rather than a guess.
+  "Show the guide again" in there brings the tour back.
+- **A panel nobody has used yet walks its own setup.** On a board with no
+  cards and no runs, the panel asks the server what is configured and, if
+  something is missing, opens a walkthrough that does one variable at a time
+  and checks each rather than asking anyone to tick it. Closing it is
+  remembered in this browser, because the board it would otherwise be written
+  to is the very thing that cannot be saved yet. On a board already in use it
+  is a banner instead — said before a save fails rather than after — and the
+  walkthrough waits behind **Help**. Its last screen carries the one thing no
+  screen can check for you: `/admin` and its bundle must both refuse a signed
+  out visitor.
+- **And it can hand the problem to Claude.** The walkthrough carries a line to
+  paste into a session in this repository. It names
+  `.claude/skills/panel/SKILL.md`, which `paneltir init` wrote, and that file
+  covers every variable the panel checks for — held together by a test, so the
+  prompt cannot come to point at a document that no longer answers it.
 - **Say which version the dashboard runs on.** `paneltirBuild.short` from
   `paneltir` renders as `vX.Y.Z · <first 12 of the fingerprint>`; keep it visible somewhere in
   the panel. `npx paneltir version` answers the same question from a terminal,

package/INSTALL.md

@@ -19,7 +19,7 @@ identity** — never another project's.
    npm install paneltir
 
    # or, without npm access, straight from the repository:
-   # npm install github:daifukus/paneltir#v0.7.0
+   # npm install github:daifukus/paneltir#v0.9.0
    ```
 
    (Use the tag you were given; never install without pinning a version.)
@@ -39,10 +39,11 @@ identity** — never another project's.
    not another project's theme.
 
 3. **If no palette is defined yet**, do not make up values: `paneltir` ships
-   base themes that are already designed and tested (`cyberpunkTheme`,
-   `midnightTheme`, `oldMoneyTheme`, all exported in `THEME_PRESETS`). Ask
-   which one fits the project best — and if the answer is not available right
-   now, use `midnightTheme`, the most neutral one, and say so explicitly.
+   base themes that are already designed and tested — `midnightTheme`,
+   `oldMoneyTheme`, `cyberpunkTheme` and `claudeTheme`, the only light one, all
+   exported in `THEME_PRESETS`. Ask which one fits the project best, and if the
+   answer is not available right now use `midnightTheme`, the most neutral one,
+   and say so explicitly.
    Store the decision in a new file (for example `src/dashboard-theme.ts`),
    re-exporting the chosen preset, or copying its values if they are expected
    to diverge:
@@ -138,18 +139,32 @@ identity** — never another project's.
    import 'paneltir/style.css'
    import { PanelApp } from 'paneltir'
    import board from './data/panel-state.json'
-
-   <PanelApp state={board} saveEndpoint="/admin/api/panel-state" showHistory />
+   import { dashboardTheme } from './dashboard-theme'
+
+   <PanelApp
+     state={board}
+     saveEndpoint="/admin/api/panel-state"
+     showHistory
+     // This project's identity, offered *alongside* the kit's presets. Use
+     // `extraThemes` and never `themes`: `themes` is the exact set, so passing
+     // one theme there deletes all four presets and the settings sheet ends up
+     // with a single row. That happened to two real projects.
+     extraThemes={{
+       thisProject: { label: 'This Project', tokens: dashboardTheme, note: 'derived from this repository' },
+     }}
+   />
    ```
 
    That is the whole page. `PanelApp` draws the board, the analysis, the card
-   sheet, the settings, the guide and the notifications, and it offers the
-   kit's themes with no further configuration. Everything a project wants
+   sheet, the settings, the guide and the notifications, and with no themes
+   passed at all it offers the kit's four. Everything a project wants
    differently is a prop rather than a fork:
 
    | Prop | What it changes |
    | --- | --- |
-   | `themes`, `defaultTheme` | The identities the settings sheet offers. Defaults to the kit's presets. |
+   | `extraThemes` | This project's own identities, offered **as well as** the kit's presets. Theirs come first, so the panel opens in one of them. This is the one you want. |
+   | `themes` | The exact set: these and nothing else, presets included. Only for a caller deliberately curating the list — it replaces rather than adds. |
+   | `defaultTheme` | Which one to draw before the board has said. Defaults to the first key. |
    | `brand` | What sits where a name goes in the header. Defaults to the board's `project`. |
    | `capabilities`, `extras` | Sections of the caller's own. Not drawn when absent. |
    | `links`, `footer`, `decoration`, `className` | Where else to go, what sits under the panel, and anything the caller draws behind it. |
@@ -169,19 +184,27 @@ identity** — never another project's.
    | `PANEL_FILE` | Where the board lives in it, if not `src/data/panel-state.json`. |
    | `SESSION_SECRET` | Optional. Defaults to `ADMIN_PASSWORD`, so changing the password ends every session already issued. |
 
+   None of that has to be done from a table. Open the panel on a board nobody
+   has worked yet and it walks the variables one at a time, checking each
+   against the server rather than asking anyone to tick it off — and if a step
+   does not land, it carries a line to paste into a Claude session in this
+   repository, which reads the skill `init` just wrote and takes it from
+   there. On a board already in use the same walkthrough is behind **Help**,
+   offered only while something is actually missing.
+
    Two things to check before trusting it: `/admin` signed out must land on
    `/login`, and **the panel's own JavaScript bundle must answer 401 signed
    out**. If it does not, point the last entry of the matcher in
    `middleware.ts` at wherever this project's build emits it — protecting the
    page but not the bundle leaves the board readable by anyone who opens the
-   HTML.
+   HTML. The walkthrough's last screen says both, for the same reason.
 
 9. **Record the kit fingerprint.** The kit reports itself, so no one has to
    read `node_modules` to find out what is installed:
 
    ```bash
    npx paneltir version          # version, fingerprint, where it came from
-   npx paneltir check 0.7.0      # exits non-zero if that is not what is installed
+   npx paneltir check 0.9.0      # exits non-zero if that is not what is installed
    npx paneltir board            # read the board and say what is wrong with it
    ```
 

package/README.md

@@ -54,7 +54,7 @@ tag rather than a branch, so an unfinished push cannot reach a project:
 npm install paneltir
 
 # or, without npm access, straight from the repository:
-# npm install github:daifukus/paneltir#v0.7.0
+# npm install github:daifukus/paneltir#v0.9.0
 ```
 
 Installing from Git runs the `prepare` script, which builds `dist/`, so the

package/bin/paneltir.mjs

@@ -197,8 +197,20 @@ function init(args) {
     for (const file of kept) console.log(`  = ${file}`)
   }
 
+  // Written the gate versus found it already there is the honest first-install
+  // signal on this side, and it changes what is worth saying: somebody
+  // re-running this has read the rest once already.
   if (!written.length) {
     console.log('\nNothing to do — every file is already in place.')
+    console.log(`
+If the panel still will not save, open it and press Help: it asks the server
+what is actually set and reports whether, never the value. Or ask this
+project's own Claude:
+
+  Read .claude/skills/panel/SKILL.md and set up the Paneltir panel with me:
+  tell me each environment variable it needs, what it is for, where in this
+  project to put it, and check the ones already set.
+`)
     return
   }
 
@@ -232,6 +244,17 @@ Then check two things before trusting it:
      not, adjust the last entry of the matcher in middleware.ts to wherever
      this project's build emits it — protecting the page but not the bundle
      leaves the board readable by anyone who opens the HTML.
+
+None of that has to be done from here. Open the panel and it walks the
+variables one at a time, checking each against the server rather than asking
+you to tick it. And if a step does not land, the walkthrough carries a line to
+paste into a session in this repository:
+
+  Read .claude/skills/panel/SKILL.md and set up the Paneltir panel with me:
+  tell me each environment variable it needs, what it is for, where in this
+  project to put it, and check the ones already set.
+
+That skill was just written into this project, and it covers exactly this.
 `)
 }
 

package/dist/index.d.ts

@@ -388,7 +388,9 @@ interface GuideTourProps {
      * durable. Leave it out and each reader's browser remembers, which is the
      * right home for a fact about one browser — and the wrong one for a panel
      * with a single owner, who would be told the same tour again on a new
-     * machine.
+     * machine. Passing it does not switch the browser off: a note dismissed
+     * here is written to both, because a caller whose store needs saving would
+     * otherwise lose the dismissal on reload.
      */
     dismissed?: string[];
     /** Told when a note is dismissed. Required for `dismissed` to mean anything. */
@@ -442,7 +444,11 @@ interface NotificationBellProps {
      * make, not the component's, which is why both work.
      */
     seen?: string[];
-    /** Told which ids were just seen. Required for `seen` to mean anything. */
+    /**
+     * Told which ids were just seen. Required for `seen` to mean anything —
+     * though the bell also remembers in localStorage either way, so a caller
+     * that has not saved yet does not show the same notifications again.
+     */
     onSeen?: (ids: string[]) => void;
 }
 declare function NotificationBell({ notifications, labels, seen: given, onSeen }: NotificationBellProps): React.JSX.Element | null;
@@ -517,6 +523,121 @@ interface SetupGuideProps {
 }
 declare function SetupGuide({ requirements, readyMessage, labels }: SetupGuideProps): React.JSX.Element;
 
+/**
+ * The setup, walked one step at a time.
+ *
+ * `SetupGuide` is the list: the right shape for somebody auditing a panel that
+ * already works. This is the other reader — the one who installed it twenty
+ * minutes ago, has four things missing and no idea which to do first. A wall
+ * of four is not four times as useful as one; it is the thing people close.
+ *
+ * Two rules hold it honest. It **checks rather than asks**: every step ends in
+ * a button that re-reads the environment from the server, so the reader is
+ * told whether it worked instead of ticking a box themselves. And it **never
+ * claims what it cannot see**: a panel that could not reach its own endpoint
+ * says the check failed, never that a variable is missing, because telling
+ * somebody to add a token they already added is the worse of the two wrong
+ * answers.
+ *
+ * There is no copy of the values here and nothing is written: the panel cannot
+ * set an environment variable, and a button that appeared to would be the same
+ * fault as one that appeared to install an update.
+ */
+interface SetupWizardLabels {
+    title: string;
+    /** `(index, total)` — "Step 2 of 5". */
+    progress: (index: number, total: number) => string;
+    /** Shown above the one step in hand. */
+    nowDo: string;
+    /** The button that re-reads the environment. */
+    check: string;
+    checking: string;
+    /** Said when a check ran and the step is still not in place. */
+    stillMissing: string;
+    /** Said when the panel could not ask its own server. */
+    cannotTell: string;
+    /** The heading over the finished steps. */
+    doneTitle: string;
+    /** Shown in place of a step when every requirement is in place. */
+    readyTitle: string;
+    readyBody: string;
+    /** The two things to try before trusting the gate, as list items. */
+    verify: string[];
+    /** Closes the wizard. */
+    close: string;
+    /** The escape hatch: heading, explanation, and the prompt to copy. */
+    stuckTitle: string;
+    stuckBody: string;
+    stuckPrompt: string;
+    copy: string;
+    copied: string;
+}
+interface SetupWizardProps {
+    /** In the order they are to be done. The caller owns that order. */
+    requirements: SetupRequirement[];
+    labels: SetupWizardLabels;
+    /** Re-reads the environment. Resolves when the answer has been applied. */
+    onCheck: () => Promise<void> | void;
+    /** Told when the reader closes it. */
+    onClose?: () => void;
+}
+declare function SetupWizard({ requirements, labels, onCheck, onClose }: SetupWizardProps): React.JSX.Element;
+
+/**
+ * Where a reader is in the setup, as one answer instead of a list to read.
+ *
+ * `SetupGuide` draws every requirement at once, which is the right shape for
+ * somebody checking a panel that already works. It is the wrong shape for
+ * somebody who has just installed one: five things at once, four of them
+ * missing, and no order to do them in reads as a wall rather than as a first
+ * step. So the same requirements are walked one at a time, and this is the
+ * function that decides which one.
+ *
+ * The order the caller gives is the order they are done in — a token that
+ * cannot be scoped before the repository is named is a step in the wrong
+ * place, and that is the caller's knowledge, not this function's.
+ */
+interface WizardStep {
+    /** The requirement to show, or null when nothing is left to do. */
+    current: SetupRequirement | null;
+    /** 1-based, for "step 2 of 5". Zero when there is nothing left. */
+    index: number;
+    /** How many steps this setup has in total. */
+    total: number;
+    /** Every requirement that is in place, in the caller's order. */
+    done: SetupRequirement[];
+    /** True when every requirement is `ok`. */
+    ready: boolean;
+    /**
+     * True when the panel could not ask the server, so nothing is claimed.
+     *
+     * This is not "not ready": a panel that cannot reach its own endpoint knows
+     * nothing about the environment, and telling somebody to add a token they
+     * already added is worse than saying the check itself failed.
+     */
+    unknown: boolean;
+}
+declare function wizardStep(requirements: SetupRequirement[]): WizardStep;
+/**
+ * Whether this panel has never been worked, which is what "first install"
+ * means here.
+ *
+ * `paneltir init` writes a board with the columns already there and nothing
+ * on them, so a board carrying no cards and no runs is one nobody has used
+ * yet. That is a better signal than a version on disk: a project can install
+ * the package, never open the panel, and update three times before anyone
+ * sees it — and it is still that reader's first run.
+ *
+ * A panel that has been worked and then loses a variable is deliberately not
+ * this. It needs the same instructions and gets them from the same wizard,
+ * but it is told rather than taken over: somebody mid-sentence on a board
+ * they know does not want a walkthrough opening on top of it.
+ */
+declare function isFirstRun(board: {
+    cards?: unknown[];
+    runs?: unknown[];
+}): boolean;
+
 type Handler = (payload: Record<string, string>, event: MouseEvent) => void;
 /**
  * A single click listener on document that dispatches by data-* attributes,
@@ -872,6 +993,14 @@ interface Preferences {
     seen?: string[];
     /** Ids of guide notes already dismissed. */
     guideDismissed?: string[];
+    /**
+     * Whether an update card is written as an order rather than a suggestion.
+     *
+     * It does not make anything automatic — the panel cannot run npm, and this
+     * changes `order` on the card it offers to write, nothing else. Off means
+     * the card asks; on means it tells.
+     */
+    updateAsOrder?: boolean;
 }
 interface PanelState {
     v: 2;
@@ -1027,6 +1156,27 @@ interface PanelTheme {
 type PanelThemes = Record<string, PanelTheme>;
 /** Every preset the kit ships, as a panel would offer them. */
 declare const PRESET_PANEL_THEMES: PanelThemes;
+/**
+ * The identities a panel actually offers, given what its caller asked for.
+ *
+ * `themes` is the exact set: these and nothing else. `extraThemes` adds to the
+ * presets, which is what a project installing the panel nearly always means —
+ * it has one identity of its own and no reason to lose the four the kit ships.
+ *
+ * The distinction exists because the absence of it cost two real installs. A
+ * default parameter is replaced, not merged, so a project passing its own
+ * theme as `themes` silently deleted every preset and its settings sheet
+ * offered exactly one row. `INSTALL.md` led there — it said to derive the
+ * project's palette and then listed `themes` as the prop for identities — so
+ * the reader followed the instructions and the API was the thing that was
+ * wrong.
+ *
+ * Extras come first, because `defaultTheme` falls back to the first key: a
+ * panel should open in the project's own identity, not in a preset that
+ * happens to sort ahead of it. A key that collides with a preset belongs to
+ * the caller — they named it, so they meant it.
+ */
+declare function offeredThemes(themes?: PanelThemes, extraThemes?: PanelThemes): PanelThemes;
 
 /**
  * What the panel shows for the dfklabs catalogue, and the three ways to
@@ -1117,6 +1267,25 @@ interface UiStrings {
     analysis: string;
     /** The Revisions tab. Short, because it sits beside Board and Analysis. */
     history: string;
+    updateTitle: string;
+    updateSubtitle: string;
+    updateCurrent: (version: string) => string;
+    updateAvailable: (version: string) => string;
+    updateUpToDate: string;
+    updateUnknown: string;
+    updateCreateCard: string;
+    updateCardExists: string;
+    updateAsOrder: string;
+    updateAsOrderHow: string;
+    notifUpdate: string;
+    releaseTitle: (version: string) => string;
+    releaseDate: (date: string) => string;
+    releaseShape: Record<'breaking' | 'feature' | 'fix' | 'chore', string>;
+    releaseKind: Record<'breaking' | 'feature' | 'fix' | 'chore', string>;
+    releaseClose: string;
+    releaseNone: string;
+    updateCardTitle: (version: string) => string;
+    updateCardBody: (version: string) => string;
     cardDetail: string;
     panelSettings: string;
     title: string;
@@ -1197,6 +1366,25 @@ interface UiStrings {
     fixTokenPaste: string;
     fixTokenRedeploy: string;
     fixRepo: string;
+    wizardTitle: string;
+    wizardProgress: (index: number, total: number) => string;
+    wizardNowDo: string;
+    wizardCheck: string;
+    wizardChecking: string;
+    wizardStillMissing: string;
+    wizardCannotTell: string;
+    wizardDoneTitle: string;
+    wizardReadyTitle: string;
+    wizardReadyBody: string;
+    wizardVerify: string[];
+    wizardClose: string;
+    wizardStuckTitle: string;
+    wizardStuckBody: string;
+    wizardStuckPrompt: string;
+    wizardCopy: string;
+    wizardCopied: string;
+    wizardOpen: string;
+    wizardBanner: string;
     demoTourWelcomeTitle: string;
     demoTourWelcomeBody: string;
     demoTourBoardTitle: string;
@@ -1271,6 +1459,10 @@ interface UiStrings {
     suggestionStatuses: Record<'new' | 'doing' | 'done' | 'dismissed', string>;
     analysisSections: Record<AnalysisSection, string>;
     analysisSectionHints: Record<AnalysisSection, string>;
+    analysisRedo: string;
+    analysisRedoAsked: string;
+    analysisRedoTitle: Record<AnalysisSection, string>;
+    analysisRedoBody: Record<AnalysisSection, string>;
     analysisAnswered: (answered: number, total: number) => string;
     analysisAllDecided: string;
     choicesTitle: string;
@@ -1379,13 +1571,26 @@ interface Capability {
 }
 declare const CAPABILITIES: Capability[];
 
+type ThemeChoice = string;
 interface PanelAppProps {
     state: PanelState;
     /**
-     * The identities the settings sheet offers. Defaults to the kit's presets,
-     * so a panel has something to switch between on its first session.
+     * The exact identities the settings sheet offers: these and nothing else.
+     *
+     * Almost nobody wants this. A project with one identity of its own wants
+     * `extraThemes`, which adds to the presets instead of replacing them — this
+     * prop silently deleted all four for two real installs, whose settings sheet
+     * then offered a single row.
      */
     themes?: PanelThemes;
+    /**
+     * Identities of the caller's own, offered *alongside* the kit's presets.
+     *
+     * This is what a project installing the panel means. They come first, so the
+     * panel opens in the project's identity rather than in a preset; a key that
+     * collides with a preset replaces it, because the caller named it.
+     */
+    extraThemes?: PanelThemes;
     /** Which one to draw before the board has said. Defaults to the first. */
     defaultTheme?: string;
     /**
@@ -1396,8 +1601,16 @@ interface PanelAppProps {
      * business drawing anybody's mark, including its own.
      */
     brand?: React.ReactNode;
-    /** Rendered inside the theme provider, behind everything: a caller's screen effects. */
-    decoration?: React.ReactNode;
+    /**
+     * Rendered inside the theme provider, behind everything: a caller's screen
+     * effects.
+     *
+     * It may be a function of the theme in force, because a decoration usually
+     * belongs to one theme rather than to the panel. This project's scanlines
+     * are Night City's and were drawn over every other theme until this existed
+     * — a palette swapped underneath an effect that did not move with it.
+     */
+    decoration?: React.ReactNode | ((theme: ThemeChoice) => React.ReactNode);
     /** Put on the theme root, so a caller's stylesheet has something to hang on. */
     className?: string;
     /** Rendered under the panel. A caller's footer, or nothing. */
@@ -1419,6 +1632,14 @@ interface PanelAppProps {
     showLanguage?: boolean;
     /** The revision log: one entry per session, newest first. */
     showHistory?: boolean;
+    /**
+     * Ask the public npm registry whether a newer kit has been published.
+     *
+     * Opt-in, because it is a request leaving the reader's browser and that is
+     * the caller's decision rather than the kit's. Nothing is installed either
+     * way: the panel offers to write a card, and a session acts on it.
+     */
+    checkForUpdates?: boolean;
     /** Endpoint that commits the board back to the repository, when there is one. */
     saveEndpoint?: string;
     /**
@@ -1436,7 +1657,7 @@ interface PanelAppProps {
         fileCount: number;
     };
 }
-declare function PanelApp({ state: initialState, themes, defaultTheme, brand, decoration, className, footer, links, capabilities, extras, showLanguage, showHistory, saveEndpoint, marketplaceEndpoint, marketplaceReport, fingerprint, }: PanelAppProps): React.JSX.Element;
+declare function PanelApp({ state: initialState, themes: exactThemes, extraThemes, defaultTheme, brand, decoration, className, footer, links, capabilities, extras, showLanguage, showHistory, checkForUpdates, saveEndpoint, marketplaceEndpoint, marketplaceReport, fingerprint, }: PanelAppProps): React.JSX.Element;
 
 /**
  * Applies a board move to the flat card list.
@@ -1461,8 +1682,16 @@ interface AnalysisViewProps {
     onDecide: (section: AnalysisSection, choiceId: string, optionId: string | null) => void;
     /** Opening the card a fact is about, so a number is never a dead end. */
     onOpenCard?: (id: string) => void;
+    /**
+     * Asks for this screen's analysis to be worked again.
+     *
+     * The panel cannot run Claude, so it writes a card and says so. A button
+     * that appeared to fetch a report and did not would be the exact fault the
+     * derived theme's refresh already avoids. Omit it and no button is drawn.
+     */
+    onRequestReport?: (section: AnalysisSection) => void;
 }
-declare function AnalysisView({ analysis, cards, columns, today, lang, ui, onChooseStrategy, onSuggestionStatus, onDecide, onOpenCard, }: AnalysisViewProps): React.JSX.Element;
+declare function AnalysisView({ analysis, cards, columns, today, lang, ui, onChooseStrategy, onSuggestionStatus, onDecide, onOpenCard, onRequestReport, }: AnalysisViewProps): React.JSX.Element;
 
 interface MarketplaceViewProps {
     /** Null while the catalogue is still being asked for. */
@@ -1488,4 +1717,4 @@ interface CardSheetProps {
 }
 declare function CardSheet({ card, state, lang, ui, onChange, onDelete, onClose }: CardSheetProps): React.JSX.Element | null;
 
-export { ANALYSIS_SECTIONS, AlertBanner, type AlertBannerProps, type Analysis, type AnalysisSection, AnalysisView, BOARD_VERSION, Board, type BoardCardData, type BoardCheck, type BoardColumnData, type BoardFacts, type BoardMoveResult, type BoardProblem, type BoardProps, type BoardTag, CAPABILITIES, type Capability, Card$1 as Card, type CardProps, CardSheet, type Check, type Choice, type ChoiceOption, type ColumnDef, type Competitor, type Constraint, CopyBlock, type CopyBlockLabels, type CopyBlockProps, type Counts, DashboardHeader, type DashboardHeaderProps, type DashboardThemeForm, DashboardThemeProvider, type DashboardThemeTokens, DetailSection, type DetailSectionProps, DetailSheet, type DetailSheetProps, FilterChip, type FilterChipProps, FilterChipRow, type Goal, GuideNote, type GuideNoteProps, GuideTour, type GuideTourProps, type HealthFact, HealthPill, type HealthPillProps, HealthPillRow, type HealthStatus, INTENTS, INTENT_COPY, type ImportedTheme, type InstallState, type Intent, type IntentCopy, LANGS, LANG_LABELS, LEVELS, type Lang, type Level, MARKETPLACE_NAME, MARKETPLACE_URL, type Market, type MarketplaceReport, type MarketplaceTool, MarketplaceView, type Metric, type Note, NotificationBell, type NotificationBellProps, type NotificationLabels, type NotificationTone, OWNERS, type Owner, PANELTIR_FILE_COUNT, PANELTIR_FINGERPRINT, PANELTIR_VERSION, PRESET_PANEL_THEMES, PanelApp, type PanelAppProps, type Card as PanelCard, type PanelNotification, type PanelState, type PanelTheme, type PanelThemes, type Preferences, type Reading, type Run, SetupGuide, type SetupGuideProps, type SetupRequirement, type SetupStatus, type Severity, StatTile, StatTileGrid, type StatTileProps, type Strategy, type Suggestion, type SuggestionStatus, THEME_FORMS, THEME_PRESETS, type Text, type ThemeFormName, type ThemePresetName, type Trend, UI, type UiStrings, type Weight, applyMove, boardFacts, checkProgress, claimedWithoutStarting, claudeTheme, commandSnippet, countCards, cyberpunkTheme, decided, emptyCard, explainBoard, isCard, ledgerForm, midnightTheme, moveCardInColumns, newId, oldMoneyTheme, panelForm, paneltirBuild, paperForm, readBoard, readStoredLang, repositorySnippet, resetGuide, sparkPoints, stampForColumn, storeLang, text, today, trendOf, undecided, untranslated, useDashboardForm, useDashboardTheme, useDelegatedClick, useGuideNote, useMediaQuery, validateBoard, writeText };
+export { ANALYSIS_SECTIONS, AlertBanner, type AlertBannerProps, type Analysis, type AnalysisSection, AnalysisView, BOARD_VERSION, Board, type BoardCardData, type BoardCheck, type BoardColumnData, type BoardFacts, type BoardMoveResult, type BoardProblem, type BoardProps, type BoardTag, CAPABILITIES, type Capability, Card$1 as Card, type CardProps, CardSheet, type Check, type Choice, type ChoiceOption, type ColumnDef, type Competitor, type Constraint, CopyBlock, type CopyBlockLabels, type CopyBlockProps, type Counts, DashboardHeader, type DashboardHeaderProps, type DashboardThemeForm, DashboardThemeProvider, type DashboardThemeTokens, DetailSection, type DetailSectionProps, DetailSheet, type DetailSheetProps, FilterChip, type FilterChipProps, FilterChipRow, type Goal, GuideNote, type GuideNoteProps, GuideTour, type GuideTourProps, type HealthFact, HealthPill, type HealthPillProps, HealthPillRow, type HealthStatus, INTENTS, INTENT_COPY, type ImportedTheme, type InstallState, type Intent, type IntentCopy, LANGS, LANG_LABELS, LEVELS, type Lang, type Level, MARKETPLACE_NAME, MARKETPLACE_URL, type Market, type MarketplaceReport, type MarketplaceTool, MarketplaceView, type Metric, type Note, NotificationBell, type NotificationBellProps, type NotificationLabels, type NotificationTone, OWNERS, type Owner, PANELTIR_FILE_COUNT, PANELTIR_FINGERPRINT, PANELTIR_VERSION, PRESET_PANEL_THEMES, PanelApp, type PanelAppProps, type Card as PanelCard, type PanelNotification, type PanelState, type PanelTheme, type PanelThemes, type Preferences, type Reading, type Run, SetupGuide, type SetupGuideProps, type SetupRequirement, type SetupStatus, SetupWizard, type SetupWizardLabels, type SetupWizardProps, type Severity, StatTile, StatTileGrid, type StatTileProps, type Strategy, type Suggestion, type SuggestionStatus, THEME_FORMS, THEME_PRESETS, type Text, type ThemeFormName, type ThemePresetName, type Trend, UI, type UiStrings, type Weight, type WizardStep, applyMove, boardFacts, checkProgress, claimedWithoutStarting, claudeTheme, commandSnippet, countCards, cyberpunkTheme, decided, emptyCard, explainBoard, isCard, isFirstRun, ledgerForm, midnightTheme, moveCardInColumns, newId, offeredThemes, oldMoneyTheme, panelForm, paneltirBuild, paperForm, readBoard, readStoredLang, repositorySnippet, resetGuide, sparkPoints, stampForColumn, storeLang, text, today, trendOf, undecided, untranslated, useDashboardForm, useDashboardTheme, useDelegatedClick, useGuideNote, useMediaQuery, validateBoard, wizardStep, writeText };