Summary
Facets are deprecated in favor of --context, but the stan-cli documentation still presents facets as an active feature. This creates confusion and misdirects users toward a workflow that is no longer intended.
References to remove / rewrite
At minimum:
(There may be additional mentions in README or other guides; do a repo-wide search for facet, facets, facet.meta.json, and --facets.)
Desired outcome
- Docs should not recommend or describe facets as a current feature.
- Replace guidance with the canonical
--context approach:
- when to use
--context
--meta archive concept (thread opener / minimal context)
- how to reduce context size / improve relevance with context mode rather than overlay exclusions
Acceptance criteria
- A search for
facet / facets / --facets in guides/ returns no results, or only clearly-labeled deprecation notes that point to --context.
- CLI examples no longer reference facet flags.
- The assistant guide’s “mental model” aligns with current implementation strategy (
--context over overlay).
Notes
This issue is intentionally scoped to documentation cleanup; a broader “docs aligned to implementation” sweep can follow as a separate issue/epic.
Summary
Facets are deprecated in favor of
--context, but the stan-cli documentation still presents facets as an active feature. This creates confusion and misdirects users toward a workflow that is no longer intended.References to remove / rewrite
At minimum:
guides/stan-assistant-guide.md-f, --facets,-F, --no-facets,--facets-on,--facets-offfacet.meta.json,facet.state.json,.docs.meta.jsonoverlay metadataguides/cli-examples.md--facets-*guides/archives-and-snapshots.md(There may be additional mentions in README or other guides; do a repo-wide search for
facet,facets,facet.meta.json, and--facets.)Desired outcome
--contextapproach:--context--metaarchive concept (thread opener / minimal context)Acceptance criteria
facet/facets/--facetsinguides/returns no results, or only clearly-labeled deprecation notes that point to--context.--contextover overlay).Notes
This issue is intentionally scoped to documentation cleanup; a broader “docs aligned to implementation” sweep can follow as a separate issue/epic.