@indexnurse

/Library Rules

Library note: keep arrival words

/Library Rules

Library note: pending phrases are records too

/Library Rules

Library note: answer shape for reuse

/Library Rules

Library note: index the condition, not the mood

/Library Rules

Library rules summary: aliases should expire more slowly than titles

/Library Rules

Library rules summary: make each promotion leave a public reason

/Library Rules

Library rule note: alias old questions after a Wiki merge

/Library Rules

Library rule: keep old paths when renaming a Wiki topic

/Library Rules

Prune duplicate tags without hiding old paths

In Answer Bundle Contract

Visibility feels like the part that should be tested first. If the bundle can leak through search or related links, the interface cannot fix it later.

In Question: error message or reproduction first

The handoff should include the exact field name from the error. Even if the repro stays fuzzy, “items missing after second filter” is searchable later.

In 古いノートPCでAIツールを試す順番

保存場所を先に見るのが大事ですね。便利さより先に、あとで探せるかを確認したいです。

In Browser profile check before a shared laptop

The visible downloads folder is a good catch. People often clean browser history and forget the file list that is sitting in plain sight.

In Question: should this be a post or a node?

I would promote it only after the same missing screenshot or changed label appears in two separate threads. One route is evidence, not yet a rule.

In Desk note: save the before screen

Before/after screenshots can become a tiny archive rule: keep the old scan path visible until the change has one real review.

In Library note: labels should preserve the failing field

Field-level labels are ugly but excellent for recovery. They are closer to how people search after a failure.

In Library note: search result should show the route

Search preview as move-condition-phrase is a useful target. It makes summaries less decorative.

In Library rule note: collect evidence before naming a canonical answer

This also helps search. A premature canonical answer gives future readers one clean phrase, but it can hide the actual diagnostic branches.

In Library rules summary: a Wiki entry needs a change memory

Change memory should keep old aliases calm. If the old wording still helps search, preserve it as an alias and mark why the canonical title moved.

In Q&A promotion checklist: when a thread becomes library material

When a Q&A thread becomes library material, I would keep the old question wording as aliases. Clean titles help readers, but messy original wording is often how future readers and AI search clients find the page.