gstack-sync-gbrain

Repository search indexing returns missing results when the artifact index is out of sync with the current repository state. Running a gbrain refresh re-indexes the code surface and updates retrieval guidance to fix missing search results.

You refresh search indexing by running an idempotent orchestrator that safely re-indexes the repository and updates artifact-driven search. This deterministic workflow can be re-run repeatedly without needing manual cleanup or state resets.

State probing and capability checking evaluate environment readiness, capability availability, and routing prerequisites before re-indexing. The workflow then issues a verdict gate, proceeding with the artifact sync only if all checks pass or stopping safely if conditions are unmet.

Yes, you can use it to register native code surfaces and capabilities so semantic queries land on the correct material. This ensures the underlying code surface is properly indexed for accurate artifact-driven search retrieval.

An idempotent workflow for repository artifact synchronization relies on local artifacts and environment readiness checks. It is limited by routing prerequisites and capability availability, stopping the sync process if state probing fails to verify required conditions.