update getting-started, remove uselss flags

Author: saidctb

docs/getting-started/beginner-workflow.md

@@ -71,16 +71,11 @@ build and smoke test still need to run.
 
 ```bash
 python3 -m x2py src/scale.f90 \
-  --wrap \
-  --out-dir build/scale \
-  --json
+  --out-dir build/scale
 ```
 
-Build output goes under `build/scale`, leaving `src/scale.f90` untouched. Keep
-the JSON result in build logs when debugging. It records the module name, output
-directory, shared-library path, generated files, and native build plan. Use
-`--verbose` instead of `--json` when you need exact compiler and linker
-commands.
+Build output goes under `build/scale`, leaving `src/scale.f90` untouched. Use
+`--verbose` when you need exact compiler and linker commands in build logs.
 
 ## 4. Run A Python Smoke Test
 
@@ -132,12 +127,12 @@ selected output directory first:
 
 ```bash
 rm -rf build/scale
-python3 -m x2py src/scale.f90 --wrap --out-dir build/scale --json
+python3 -m x2py src/scale.f90 --out-dir build/scale
 ```
 
-Use `--wrap --makefile` when you intentionally want inspectable commands and
-manual rebuild control. `--makefile` and `--verbose` are separate modes and
-cannot be combined.
+The advanced Makefile workflow is available when you intentionally want
+inspectable commands and manual rebuild control. Makefile generation and
+`--verbose` are separate modes and cannot be combined.
 
 ## Advanced Next Step: Edit The Semantic Contract
 

docs/getting-started/first-wrapped-function.md

@@ -25,9 +25,7 @@ From the directory containing `scale.f90`:
 
 ```bash
 python3 -m x2py scale.f90 \
-  --wrap \
-  --out-dir build/first-function \
-  --json
+  --out-dir build/first-function
 ```
 
 The extension is named after the source stem: `scale`. The standalone native

docs/getting-started/first-wrapped-module.md

@@ -53,9 +53,7 @@ From the directory containing `module_state.f90`:
 
 ```bash
 python3 -m x2py module_state.f90 \
-  --wrap \
-  --out-dir build/first-module \
-  --json
+  --out-dir build/first-module
 ```
 
 The source stem creates extension `module_state`. Its contained module is

docs/getting-started/installation.md

@@ -37,8 +37,9 @@ Install these before attempting a wrapper build:
 - NumPy, whose Python package supplies the required C headers; and
 X2PY_C_DOCS_END -->
 
-GNU Make is optional. Direct builds do not require it, but `--wrap --makefile`
-emits a `Makefile.x2py` that expects GNU Make and a POSIX-style shell.
+GNU Make is optional. Direct builds do not require it. The generated Makefile
+workflow is an advanced build mode that expects GNU Make and a POSIX-style
+shell.
 
 On Ubuntu or Debian, the prerequisite packages normally come from:
 

docs/getting-started/verification.md

@@ -69,41 +69,29 @@ From the same directory, build `scale.f90` into a dedicated directory:
 
 ```bash
 python3 -m x2py scale.f90 \
-  --wrap \
-  --out-dir build/verify \
-  --json
+  --out-dir build/verify
 ```
 
-The JSON result must report:
+The command must create:
 
-- `compiled` as `true`;
-- `module_name` as `scale`;
-- an existing `shared_library` under `build/verify`; and
-- generated native bridge, object, runtime-support, and extension paths.
+- an importable `scale` extension under `build/verify`; and
+- generated native bridge, object, runtime-support, and extension files.
 
 <!-- X2PY_C_DOCS_START
-- generated bridge, C binding, object, and runtime-support paths.
+- generated bridge, C binding, object, and runtime-support files.
 X2PY_C_DOCS_END -->
 
-Import the extension through the Python API result so the platform-specific
-shared-library suffix does not need to be guessed:
+Import the extension from that build directory:
 
 ```python
-from importlib.util import module_from_spec, spec_from_file_location
+import sys
 
 import numpy as np
 
-from x2py import build_fortran_extension
-
-build = build_fortran_extension(
-    "scale.f90",
-    output_dir="build/verify",
-)
-spec = spec_from_file_location(build.module_name, build.shared_library)
-extension = module_from_spec(spec)
-spec.loader.exec_module(extension)
+sys.path.insert(0, "build/verify")
+import scale
 
-assert extension.scale(np.float64(3.0), np.float64(2.5)) == np.float64(7.5)
+assert scale.scale(np.float64(3.0), np.float64(2.5)) == np.float64(7.5)
 ```
 
 ## 4. Inspect Generated Files
@@ -127,9 +115,8 @@ print(build.output_dir)
 print(build.shared_library)
 ```
 
-For CLI builds, `--json` exposes the same fields. Add `--verbose` when a
-compiler or linker command fails; it prints the exact native commands and stage
-timings.
+For CLI builds, add `--verbose` when a compiler or linker command fails; it
+prints the exact native commands and stage timings.
 
 ## Escalation Path
 

tests/tools/test_documentation_structure.py

@@ -762,7 +762,7 @@ def test_beginner_workflow_reuses_scale_example_without_renaming_it() -> None:
     source_reference_index = page.index("[README Quick Start](../../README.md#quick-start)")
     layout_index = page.index("src/\n    scale.f90")
     contract_index = page.index("python3 -m x2py src/scale.f90 --pyi")
-    build_index = page.index("python3 -m x2py src/scale.f90 \\\n  --wrap \\\n  --out-dir build/scale")
+    build_index = page.index("python3 -m x2py src/scale.f90 \\\n  --out-dir build/scale")
     smoke_index = page.index("result = scale.scale(np.float64(3.0), np.float64(2.5))")
     advanced_index = page.index("## Advanced Next Step: Edit The Semantic Contract")
 
@@ -777,7 +777,9 @@ def test_getting_started_pages_keep_advanced_stage_flags_out_of_beginner_path()
 
     assert "--parse" not in content
     assert "--semantics" not in content
+    assert "--wrap" not in content
     assert "--wrap-readiness" not in content
+    assert "--json" not in content
 
 
 @pytest.mark.parametrize("heading", CLI_HELP_GROUP_HEADINGS)