docs: remove temporary development notes

docs/CONTRIBUTING.md

@@ -85,6 +85,11 @@ the resulting behavior, relevant validation, and documentation status. Link the
 issue when applicable. A short example or diagram is useful when it clarifies the change;
 commit histories and raw test logs are unnecessary.
 
+Before requesting merge, inspect the complete PR diff and changed-file list.
+Remove one-off patch/staging workflows, local logs, generated reports and temporary
+files. Keep review coordination, validation-run links and pending PR references in
+the PR discussion; repository documentation should describe the resulting behavior.
+
 Address review findings within the agreed scope and validate the affected paths again.
 Resolve a discussion after its issue is fixed or clarified. Inspect failing CI jobs before
 retrying; a rerun is appropriate for a temporary infrastructure failure, not a reproducible bug.

docs/ci.md

@@ -6,15 +6,12 @@ selects affected tests, reads the project Java version, checks CI policy and ver
 license headers and RAT. Selected Helm checks run as steps in preflight; other selected suites
 run through reusable workflows in the same run.
 
-CI results become advisory after [`.asf.yaml`](../.asf.yaml) is applied. It requests no required CI contexts
-and retains one approving review. This protection change takes effect after the configuration
-is merged and synchronized by Gitbox; verify live protection then. Failed tests keep their
-real failed results. Valid selection and Java outputs allow selected tests to run even when
+The protection policy in [`.asf.yaml`](../.asf.yaml) requests no required CI contexts
+and retains one approving review. Failed jobs retain their failing check results.
+Valid selection and Java outputs allow selected tests to run even when
 the preflight license checks fail.
 
-Preflight keeps its real `check-license` name. The temporary `Server memory tests`
-protection bridge has been removed after confirming both ASF and org master required
-contexts are empty. Actual backend jobs are named `Server memory tests (Java ...)`
+Preflight uses the `check-license` name. Backend jobs are named `Server memory tests (Java ...)`
 and `Server rocksdb tests (Java ...)`; their native checks report real execution.
 
 ## Coverage with selective tests

docs/cypher-api.md

@@ -122,15 +122,6 @@ translator failure; runtime errors such as `Unsupported predicate` and
 `CONTAINS query ... is not supported` also fall back.
 There is no `HugeGraph.Cypher.MissingParameter` contract.
 
-This contract repairs the unreleased proposal in
-[Server #3241](https://github.com/apache/hugegraph/pull/3241). The paired website
-work is [Doc #499](https://github.com/apache/hugegraph-doc/pull/499); its author
-must incorporate this response contract before coordinated publication.
-Parameterized POST requests are already provided by merged
-[Server #3289](https://github.com/apache/hugegraph/pull/3289).
-The earlier [bound-query fork #238](https://github.com/hugegraph/hugegraph/pull/238)
-is a historical reference; use the current request contract above.
-
 ## Temporal functions
 
 The built-in translator has no temporal functions of its own. The Server folds

docs/server-runtime.md

@@ -952,7 +952,7 @@ that field. Responses retain the raw zero marker so editing clients can preserve
 The bootstrapped `DEFAULT` space keeps explicit compute limits of 128 cores / 128 GB;
 existing positive compute limits are not converted to inheritance.
 Upgrade the Java client together with the Server before sending partial space
-updates (paired [Toolchain change](https://github.com/apache/hugegraph-toolchain/pull/834)).
+updates. The client must preserve the distinction between omitted fields and explicit zeros.
 Older clients send zero for omitted compute fields; the new Server interprets an
 explicit zero as restoring inheritance and cannot distinguish that from an omitted
 SDK property. Until clients are upgraded, use read-modify-write and explicitly send