[Kinflou]

Adds conduct/phases.md, "Phases and promises", decided 2026-10-27.

What the page says

• Three phases: early days (now), previews before 1.0 (still early days), and the 1.0 announcement, which sets stability.
• Always: correctness, conformance, performance and safety never lowered; branch rules apply; wire changes ship with vectors that every runtime passes.
• Early days: 0.x, anything may break, wire bytes may change only in one cascade, no deprecation periods, everything by git revision, no publishing or prebuilt binaries.
• From 1.0: semver, deprecate a minor before removing, wire bytes frozen (a change is a new @N), C ABI structs frozen and codes/flags append-only, registry packages under ComlineProject names with OIDC publishing, reproducible builds and checksums.

Re-pointed places (the C ABI has no "ABI 1.0" milestone of its own now; it stays 0.x and freezes with the project's 1.0 announcement)

• proposals/shared-runtime-core/index.md: stage 2 row, and a stage 4 line (TypeScript through wasm only, napi and Go later by instruction counts)
• proposals/index.md
• proposals/shared-runtime-core/core-interface.md: deferred items, ABI versioning, Distribution, open questions, rollout step 5
• reference/c-abi.md: header bullet, Version, "Not here yet"
• design/runtime-repo-structure.md: two sentences linking the phases page
• Conduct index and nav

This settles the conflict between the proposal's "ABI 1.0 + releases after the first bindings" and runtime-repo-structure's "git revs, publish later": git revisions until the 1.0 announcement, releases and registries after.

Remaining "1.0" mentions are either links to the phases page or about package versioning (comline release 1.0) or values like 1.0 floats and a benchmark ratio.