feat: Automatically use the default Scope when no Scope is configured on first startup

[jiannnnyyyyy]

Feature description

When PowerContext is started for the first time without any Scope-related environment variables, automatically create and use the default Scope, and display it in the Dashboard.

Problem and proposed solution

After installing and starting PowerContext:

uv tool install "powercontext[cli,server]"
powercontext server run

powercontext doctor reports that the package, server, runtime, and database are all healthy. However, opening http://127.0.0.1:8000 shows:

No dashboard scope configured.

The Dashboard remains empty, making it unclear whether the server started correctly or what additional configuration is required.

We suggest that PowerContext should:

• Automatically use the server’s default Scope when no Scope is explicitly configured.
• Display the default Scope in the Dashboard.
• Provide an onboarding flow if Scope configuration is required.
• Include actionable Scope configuration guidance in powercontext doctor.

Alternatives considered

• Require users to manually set POWERCONTEXT_CODEX_SCOPE_ID or another Scope-related environment variable. This is explicit but creates unnecessary friction for first-time users.
• Add more documentation explaining the required configuration. This may help, but does not address the empty Dashboard or lack of in-product guidance.
• Keep the current behavior and only improve the Dashboard error message. This is easy to implement, but users would still need to configure the Scope manually.

Additional context

Environment:

powercontext 0.1.0 (PyPI)
macOS
http://127.0.0.1:8000

powercontext doctor output:

package: ok - powercontext 0.1.0
server liveness: ok
server readiness: ok
runtime: ready
database: ready

Related documentation:

https://github.com/oceanbase/powercontext/blob/master/docs/zh/docs/how-to/full-capability-runtime.md

Are you willing to contribute to this feature?

• Yes, I am willing to contribute code, docs, or design feedback.