「only」の検索結果

Use when writing, editing, cleaning, or refactoring Tailwind classes, components, or configuration. Not for read-only audits of Tailwind code, or general CSS without Tailwind.

日本語の概要は準備中です。原文の説明を表示しています。

Use when setting up a project, auditing agent command permissions, or asking which read-only bash commands and domains to allow. Not for remote, credential, publish, deploy, or irreversible changes.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a bug, failure, flake, regression, review finding, or ticket needs the core fixed so it cannot recur. Not for greenfield features: use tdd. Not for style-only review or typo-class one-liners.

日本語の概要は準備中です。原文の説明を表示しています。

Independently review one Proto UI autonomous-maintenance remediation in a fresh read-only context. Use after pui-remediate produces a packet and actual diff. Classify technical-completion eligibility without making product or integration decisions.

日本語の概要は準備中です。原文の説明を表示しています。

Inspect one bounded Proto UI pull-request slice, produce canonical review input, and route each eligible exact head toward review and integration. Use for review queues, linked work, evidence gaps, merge conflicts, stale revisions, or portfolio health. This evidence leaf is read-only; authorized review and integration continue in their registered leaves.

日本語の概要は準備中です。原文の説明を表示しています。

Inspect one bounded Proto UI Issue queue slice and route ready governed work toward claim and implementation. Use for intake health, readiness, ownership, claim conflicts, stale state, or a candidate task search. This evidence leaf is read-only; authorized claim and implementation continue in their registered leaves.

日本語の概要は準備中です。原文の説明を表示しています。

Diagnose one bounded Proto UI Actions or CI failure from an exact workflow run and revision, then route the exact repair, validation, or recheck transition. Use to locate the owning failure and distinguish infrastructure from change failures. This leaf remains read-only.

日本語の概要は準備中です。原文の説明を表示しています。

Select at most one eligible Proto UI work item and return a read-only proposal without changing GitHub or repository state. Use after pui-orient when requested contribution work is not yet bounded, or when a user asks what ready task fits the current capability and permission envelope. Do not post a claim, assign anyone, decide readiness, or invent work.

日本語の概要は準備中です。原文の説明を表示しています。

Publish one prepared Agent evidence packet as an additive Issue comment, including historical or closed Issues, under exact current authorization. Use after read-only Issue inspection and separately authorized evidence preparation. Do not reproduce, select work, upload assets, edit human text, claim, review, close, or change Issue metadata.

日本語の概要は準備中です。原文の説明を表示しています。

Execute one bounded read-only Proto UI autonomous-maintenance observation mission. Use for drift hunting, external-oracle comparison, repeatability control, or a no-finding maintenance run. Stop before verification or remediation.

日本語の概要は準備中です。原文の説明を表示しています。

Audit one bounded Proto UI collaboration-governance slice and route policy-determined drift toward reversible correction. Use across Issues, pull requests, Discussions, labels, milestones, Project, rules, permissions, or Actions. This evidence leaf is read-only; authorized corrections continue in their registered leaves.

日本語の概要は準備中です。原文の説明を表示しています。

Assess and route one bounded Proto UI dependency drift, advisory, or update question. Use to trace manifest and lockfile identity, consumer impact, compatibility evidence, provenance, update risk, and the exact next update or no-action transition. This leaf remains read-only.

日本語の概要は準備中です。原文の説明を表示しています。

Translate, complete, and audit Docusaurus localization under docs/i18n for both UI JSON catalogs and documentation Markdown/MDX pages. Use when adding or correcting locales, when a language switcher translates only theme labels while page content stays in the default language, or when verifying that non-default locales do not fall back to source documentation.

日本語の概要は準備中です。原文の説明を表示しています。

Reliability gate for answers. Forces evidence-based reasoning, explicit uncertainty, and “insufficient information” instead of guesses. Use when user says “be 100% sure”, “no hallucinations”, “only if verified”, “grounded answer”, or when stakes are high.

日本語の概要は準備中です。原文の説明を表示しています。

Run a standalone read-only rules compliance gate against changed files or a git ref. Use when you need a dedicated project-rules check without a full review or verify pass.

日本語の概要は準備中です。原文の説明を表示しています。

Enter explore mode to investigate ideas, systems, problems, and requirements before planning. Use explicit ultra mode when the user wants a durable adaptive research bundle with an index and only the justified C4, ADR, or dependency artifacts.

日本語の概要は準備中です。原文の説明を表示しています。

Fix RFDB V2 graph data silently not persisting to disk after analysis. Use when: (1) rfdb-server reports "0 nodes, 0 edges" on restart despite successful analysis, (2) segment directories exist but are empty (no .bin files), (3) manifest_index.json shows total_nodes: 0 despite analysis logging 70k+ nodes, (4) Docker builds produce empty graph databases, (5) --clear flag used before analyze command. Root cause: GraphEngineV2::clear() replaces the store with MultiShardStore::ephemeral() which has path: None, causing all flush operations to write to in-memory buffers only.

日本語の概要は準備中です。原文の説明を表示しています。

Recover from stale RFDB nodes that survive `commit_batch` cleanup despite having their `file` field listed in `changed_files`. Use when: (1) re-running an enricher/orchestrator step but old data with the same file field stays in the graph, (2) `commit_batch(changed_files=[X], ...)` reports success but a query later still returns nodes with `file = X`, (3) you re-pointed structural nodes (e.g., DIRECTORY/FILE) from a synthetic file path to real file paths and the old synthetic-path nodes won't go away, (4) graph-stream / find_by_type returns a mix of "stale" and "new" nodes for the same logical entity. Root cause: `handle_commit_batch` calls `engine.find_by_attr({file: X})` to enumerate nodes-to-delete, but that query path returns only a PARTIAL set after compaction (L1 segments and the file→nodes index can desync). Workaround: enumerate stale nodes via the TS rfdb client `queryNodes({file: X})` (different code path that finds all of them) and call `deleteNode(id)` per node, then re-commit the intended state. Related: rfdb-manifest-l1-carryforward (same L1 family).

日本語の概要は準備中です。原文の説明を表示しています。

Diagnose and fix RFDB data disappearing after compaction, where rfdb-server reports a tiny node count (e.g. "15 nodes") on startup despite manifest_index.json showing hundreds of thousands of nodes and segment files existing on disk. Use when: (1) rfdb-server logs "Default database: N nodes" with N orders of magnitude smaller than recent analysis output, (2) /api/stats returns only the most recent commit's nodes, (3) the issue appears AFTER a compaction event (manifest with l1_node_segments populated and node_segments: []), (4) subsequent commits dropped L1 references. Root cause: ManifestStore::create_manifest() initializes l1_node_segments/l1_edge_segments to Vec::new() instead of cloning from current manifest, so any commit AFTER compaction silently orphans all L1 data even though segment .seg files still exist on disk. Compaction injects L1 fields explicitly after create_manifest, but regular commits do not.

日本語の概要は準備中です。原文の説明を表示しています。

Fix nodes silently disappearing from RFDB when an enricher or post-resolution pass writes new nodes via BatchHandle. Use when: (1) writing a TypeScript enricher that should ADD nodes/edges to existing files, (2) after calling `client.createBatch()` + `batch.addNode({file: 'X', ...})` + `batch.commit()` the original nodes in file X have vanished, (3) tests that load a graph fixture, run an enricher, then query original nodes get empty results, (4) a verification step shows expected nodes pre-enrichment but 0 post-enrichment. Root cause: `BatchHandle.commit()` invokes RFDB's `commit_batch` which AUTO-POPULATES `changed_files` from each added node's `file` field, then the server DELETES all existing nodes whose `file` matches before inserting new ones — file-level upsert semantics. This is correct for the JS/Haskell analyzers (which fully re-emit a file's contents) but catastrophic for enrichers that only ADD to existing files.

日本語の概要は準備中です。原文の説明を表示しています。

Decide what to PERSIST in your data structures (graph nodes, DB tables, cache layouts) based on the QUERIES you must answer, not the DEFINITIONS that justify the data. Definitions tell you logical identity; storage strategy is independent. Materializing every definitional component leads to O(N×M) blow-ups that masquerade as memory leaks. Use when: (1) designing a new graph-node type, edge type, DB table, or cache layout; (2) about to name a `subgraph` / `comprises` / `members` / `contains` collection on a parent entity; (3) memory growth proportional to (entities × per-entity-elements); (4) "memory leak" debugging that survives multiple targeted patches — the leak may be storage shape, not retention; (5) pre-implementation sketch includes "for each X, store all reached nodes"; (6) research/spec doc says "X = ⟨A, B, C⟩" and you're tempted to make it three storage edges per X.

日本語の概要は準備中です。原文の説明を表示しています。

Fix intermittent `{:no_translation, :unicode, :latin1}` crashes in Elixir escript daemons that use length-prefixed framed IPC on stdin/stdout. Use when: (1) daemon worker crashes only on some input files, usually ones with non-ASCII bytes (kanji, cyrillic, emoji); (2) error surfaces as `Protocol error` from daemon's error branch or as garbled frame-length bytes seen by the orchestrator/client side; (3) standalone one-shot mode works fine on the same input but multi-request daemon mode fails; (4) `IO.binread(:stdio, N)` returns `{:error, {:no_translation, :unicode, :latin1}}` despite the "bin" prefix suggesting it should be encoding-agnostic. Root cause is the escript default `:standard_io` encoding — it's `:unicode`, and `IO.binread` still routes through the io_server, which translates bytes to codepoints and errors when raw binary frames contain invalid UTF-8 sequences.

日本語の概要は準備中です。原文の説明を表示しています。

Compute a unified outer hull around a group of hex tiles that includes multiple disconnected sub-clusters separated by 1-tile gaps. Use when: (1) rendering nested hierarchy hulls (e.g. "package" hull wrapping multiple "sub-region" hex islands), (2) the naive boundary trace outlines each island separately instead of as one bag, (3) flood-fill from outside walks THROUGH the 1-hex gaps and marks them exterior, (4) heuristic "non-adjacent same-group neighbours" over-fills L-shape concavities, (5) axial-only opposite-pair filling misses non-axial bridges between islands. Solution: morphological close (dilate + erode) on the hex grid — fills exactly the interior 1-hex gaps without affecting exterior corners, then trace boundary on the closed shape.

日本語の概要は準備中です。原文の説明を表示しています。

RFDB server becomes unresponsive (60s+ timeouts) during enricher addEdges write storms. Use when: (1) RFDB CPU spikes to 60-90% after addEdges calls; (2) subsequent reads time out at 60s; (3) server stays catatonic for 5-15 min after a write storm; (4) Tokio main thread parked (write-lock contention). Root cause: add_edges() calls maybe_auto_flush() which has a memory-pressure path that fires on NODE count — not edge count — and holds the exclusive write lock during disk I/O. Fix: separate maybe_auto_flush_edges() uses byte-limit only.

日本語の概要は準備中です。原文の説明を表示しています。