Design chat-to-knowledge ingestion around abstraction, not raw transcripts

[JRS1986]

Feedback

If CodingScaffold adds automatic chat ingestion later, it should not save raw chat messages directly into team knowledge.

Design direction

• Treat raw transcripts as sensitive source material, not the wiki itself.
• Summarize, compress, abstract, and deduplicate before proposing knowledge updates.
• Redact secrets, private data, and irrelevant conversational history.
• Prefer reviewable proposals under curated Markdown/wiki paths rather than silent writes.
• Keep human review in the promotion loop, especially for team/company knowledge.

Scope

This is a future design issue. The current README clarification should avoid claiming automatic chat ingestion exists today.