docs(code): remove stale pre-RFC role wording and fix review aid
Follow-up cleanup of text left by the concurrent implementation: - marqdo-markdown AST, marqdo-ir statements/branch arms, frontend units, payload and signature module docs now describe RFC-LANG-0002 roles (payload carriers, heading modes, if/else groups, while/end, params) - marqdo-expression public docs list parse_payload_statement and stop describing a Markdown-link call that no longer exists - retired markdown.invalid_construct/markdown.inert_executable constants are documented as decode-only history for old Analysis/Trace JSON - drop the stale 'expected red' comment in the CLI integration test - the dev-only .mq.md review aid no longer reports semicolons inside string literals, and skips AST baselines / expected-invalid negatives Verified: fmt, clippy -D warnings and cargo test --workspace --locked green.
This commit is contained in:
1 parent
361a6cc341
commit
d5002ac826
9 files changed
+104
-52
No files matched your search
@@ -211,9 +211,8 @@ fn check_exit_codes_and_diagnostics() {
|
||||
assert!(stderr_text(&bad_json).is_empty());
|
||||
|
||||
// RFC-LANG-0002: a Strong at the Knowledge root is inert prose, not an
|
||||
// executable shape. There is no `markdown.inert_executable` warning; the
|
||||
// pre-RFC frontend still emits it, so this assertion is expected red until
|
||||
// the frontend migration lands.
|
||||
// executable shape, and the old `markdown.inert_executable` warning no
|
||||
// longer exists.
|
||||
let inert = cli(dir.path(), &["check", "warning.mq.md"]);
|
||||
assert_exit(&inert, 0, "inert Knowledge prose does not fail check");
|
||||
assert!(stdout_text(&inert).contains("checked 1 module(s): ok"));
|
||||
|
||||
Reference in new issue
Block a user