From: Thomas Walker Lynch <eknp9n@reasoningtechnology.com>
Date: Tue, 13 Oct 2026 08:28:31 +0000 (+0000)
Subject: skeleton update
X-Git-Url: https://git.reasoningtechnology.com/USER_NAME.png?a=commitdiff_plain;h=a897a50c0e45e6f326a624daa32cb6d2e3aa9d08;p=RT-Style

skeleton update
---

diff --git a/administrator/document/install_Python.org b/administrator/document/install_Python.org
deleted file mode 100644
index 04d60a6..0000000
--- a/administrator/document/install_Python.org
+++ /dev/null
@@ -1,38 +0,0 @@
-#+TITLE: Python Installation Guide
-#+AUTHOR: Project Administrator
-
-This project requires a dedicated Python environment. The configuration plugin (`shared/linked-project/Python.init`) was written targeting Python 3.12.3, though the architecture does not rely on any known version-dependent features. 
-
-* 1. Download and Extract
-Download the Python source code and extract it as a sibling to the main project directory. Assuming you are at the top level of your project workspace:
-
-#+begin_src bash
-cd ../
-wget https://www.python.org/ftp/python/3.12.3/Python-3.12.3.tgz
-tar -xzf Python-3.12.3.tgz
-cd Python-3.12.3
-#+end_src
-
-* 2. Build the Environment
-Compile the Python binaries in place. Setting the installation prefix to the current directory isolates the build, and enabling shared libraries ensures compatibility with C extensions.
-
-#+begin_src bash
-./configure --prefix="$(pwd)" --enable-optimizations --enable-shared
-make -j8
-make install
-#+end_src
-
-* 3. Link the Project
-
-Python-3.12.3 is linked to a Harmony derived project by default.  
-
-See installation_generic.org for details about linking a project, if you want to check the setup.
-
-If you are installing a different version, then at least the Python-3.12.3 version project linking is there as a good example.
-
-Project linking is not difficult, make a sym link to `project/<linked-project>`, and then add an init file, that is described in installation_generic.org. The 'project' in the link is literal.
-
-
-
-
-
diff --git a/administrator/document/install_generic.org b/administrator/document/install_generic.org
deleted file mode 100644
index 1069c20..0000000
--- a/administrator/document/install_generic.org
+++ /dev/null
@@ -1,21 +0,0 @@
-#+TITLE: Generic Third-Party Installation Guide
-#+AUTHOR: Project Administrator
-
-This project utilizes the Harmony skeleton's `.init` architecture for managing external dependencies. Third-party tools and projects are maintained outside the main repository boundary and linked into the workspace.
-
-* 1. The Neighbor Directory
-Download, clone, or extract the external tool into the same parent directory that contains this project workspace. It must sit as a sibling directory to your current project.
-
-* 2. The Symlink
-Navigate to the `$REPO_HOME/shared/linked-project` directory. You will notice a pre-existing symlink named `project` that points to the parent directory of this project. Use that to create a clean symlink to the external tool.
-
-#+begin_src bash
-cd shared/linked-project
-ln -s project/<external_tool_directory> <link_name>
-#+end_src
-
-* 3. The Initialization File
-Create a configuration file named `<link_name>.init` inside the `$REPO_HOME/shared/linked-project/` directory. This file is automatically sourced when a project participate enters their role environment using `. setup <role>` as part of the project setup.  Use this file to  update the `PATH` or export necessary environment variables needed for using the linked project.
-
-Review existing `.init` files in the directory for structural examples.
-
diff --git a/administrator/document/sys b/administrator/document/sys
deleted file mode 100644
index e69de29..0000000
diff --git a/administrator/tool/RT-style_v2_to_v3 b/administrator/tool/RT-style_v2_to_v3
deleted file mode 100644
index df95092..0000000
--- a/administrator/tool/RT-style_v2_to_v3
+++ /dev/null
@@ -1,55 +0,0 @@
-#!/usr/bin/env python3
-import sys
-import os
-import re
-
-def migrate_rt_tags(file_path):
-  if not os.path.isfile(file_path):
-    print(f"Error: File '{file_path}' not found.")
-    sys.exit(1)
-
-  with open(file_path, 'r', encoding='utf-8') as f:
-    content = f.read()
-
-  # 1. Migrate legacy tag terminology to current vocabulary
-  content = re.sub(r'<(/?)(RT)-index(\b|/|>)', r'<\g<1>\g<2>⋅term-index\g<3>', content)
-  content = re.sub(r'<(/?)(RT-counter)[_-]init(\b|/|>)', r'<\g<1>\g<2>⋅make\g<3>', content)
-  content = re.sub(r'<(/?)(RT-counter)[_-]inc(\b|/|>)', r'<\g<1>\g<2>⋅step\g<3>', content)
-  content = re.sub(r'<(/?)(RT-counter)[_-]label(\b|/|>)', r'<\g<1>\g<2>⋅snapshot\g<3>', content)
-
-  # 2. Migrate the primary RT namespace separator
-  rt_tags = [
-    "article", "memo", "book", "title", "TOC", "term-index", 
-    "endnotes", "term", "term-em", "neologism", "neologism-em", 
-    "code", "math", "symbol", "constraint", "crossref", "ref", 
-    "cite", "footnote", "page", "page-break", "chapter", "theme-selector"
-  ]
-  rt_pattern = "|".join(rt_tags)
-  content = re.sub(rf'<(/?)(RT)-({rt_pattern})(\b|/|>)', r'<\g<1>\g<2>⋅\g<3>\g<4>', content)
-
-  # 3. Migrate the secondary RT-counter namespace separator
-  counter_tags = ["make", "step", "indent", "snapshot", "read"]
-  counter_pattern = "|".join(counter_tags)
-  content = re.sub(rf'<(/?)(RT-counter)[_-]({counter_pattern})(\b|/|>)', r'<\g<1>\g<2>⋅\g<3>\g<4>', content)
-
-  # 4. Migrate the 'initial' parameter to 'on-first-step' within make tags
-  content = re.sub(r'(<RT-counter⋅make[^>]+)initial=', r'\g<1>on-first-step=', content)
-  
-  # 5. Migrate 'key="initial"' to 'key="on-first-step"' within read tags
-  content = re.sub(r'(<RT-counter⋅read[^>]+key=[\'"])initial([\'"])', r'\g<1>on-first-step\g<2>', content)
-
-  backup_path = file_path + '.v2.bak'
-  os.rename(file_path, backup_path)
-
-  with open(file_path, 'w', encoding='utf-8') as f:
-    f.write(content)
-
-  print(f"Migration complete: {file_path}")
-  print(f"Original file backed up to: {backup_path}")
-
-if __name__ == "__main__":
-  if len(sys.argv) != 2:
-    print("Usage: python3 migrate_rt_v3.py <file_path>")
-    sys.exit(1)
-    
-  migrate_rt_tags(sys.argv[1])
diff --git a/administrator/tool/html_to_v4 b/administrator/tool/html_to_v4
deleted file mode 100755
index 30f404f..0000000
--- a/administrator/tool/html_to_v4
+++ /dev/null
@@ -1,51 +0,0 @@
-#!/usr/bin/env python3
-# -*- mode: python; coding: utf-8; python-indent-offset: 2; indent-tabs-mode: nil -*-
-
-import sys
-import re
-from pathlib import Path
-
-def update_header_to_v4(file_path):
-    target_path = Path(file_path)
-    content = target_path.read_text(encoding='utf8')
-
-    title_match = re.search(r'<title>(.*?)</title>', content, re.IGNORECASE)
-    if not title_match:
-        print(f"Skipping {file_path}: No title tag found.")
-        return
-
-    document_title = title_match.group(1)
-
-    new_header = f"""<!DOCTYPE html>
-<html lang="en">
-  <head>
-    <meta charset="UTF-8">
-    <title>{document_title}</title>
-    <script src="RT-Manuscript_locator.js"></script>
-    <script>
-      window.RT.theme_preference('inverse_wheat');
-      window.RT.load('Layout/paginate');
-      window.RT.load('Layout/article_tech_ref');
-      window.RT.load('Element/theme_selector');
-    </script>
-  </head>
-  <body>
-    <RT·theme-selector></RT·theme-selector>
-    <RT·article>"""
-
-    pattern = re.compile(r'<head>.*?</head>\s*<body>\s*<RT[-·]article>', re.DOTALL | re.IGNORECASE)
-
-    if not pattern.search(content):
-        print(f"Skipping {file_path}: Header block pattern not matched.")
-        return
-
-    updated_content = pattern.sub(new_header, content, count=1)
-    target_path.write_text(updated_content, encoding='utf8')
-    print(f"Successfully updated {file_path}")
-
-if __name__ == '__main__':
-    if len(sys.argv) < 2:
-        print("Usage: python to_v4.py <html_file>")
-        sys.exit(1)
-
-    update_header_to_v4(sys.argv[1])
diff --git a/developer/authored/Manuscript.copy/Document/design.html b/developer/authored/Manuscript.copy/Document/design.html
index b95974d..17c6558 100644
--- a/developer/authored/Manuscript.copy/Document/design.html
+++ b/developer/authored/Manuscript.copy/Document/design.html
@@ -147,7 +147,8 @@
             Harmony supplies a maintenance tool for it, named <RT·code>scratchpad</RT·code>, which operates on the scratchpad of the current directory. <RT·code>scratchpad ls</RT·code> prints the tree with permissions and ownership, <RT·code>scratchpad size</RT·code> reports whether anything is there, and <RT·code>scratchpad write</RT·code> copies a file or directory onto the pad.
           </p>
           <p>
-            <strong><RT·code>scratchpad clear</RT·code> deletes the entire contents of the current directory's scratchpad</strong>, preserving only the top level <RT·code>.gitignore</RT·code>. It does not prompt. Given a name, as in <RT·code>scratchpad clear Manuscript</RT·code>, it removes that subdirectory alone, which is the form to reach for. A cleared pad means the next <RT·code>promote write</RT·code> has nothing to promote, so clear and rebuild rather than clear and promote.
+            <RT·code>scratchpad clear</RT·code> deletes the entire contents of the scratchpad, except for <RT·code>.gitignore</RT·code>. Given a directory name or path it deletes that directory.
+            <RT·code>scratchpad clear made</RT·code> deletes the entire contents of the accumulated builds, while <RT·code>scratchpad clear made/Manuscript</RT·code> deletes Manuscript build. The <RT·code>clear</RT·clear> command does not prompt for confirmation.
           </p>
         </RT·section>
 
@@ -441,7 +442,7 @@
               Each plugs in and registers its tasks.
             </RT·entry>
             <RT·entry key="10. DOMContentLoaded">
-              Parsing completes, the browser fires the event, and the pipeline runs. Nothing within the engine invokes the pipeline; the browser is the trigger. The locator requests the make file, which loads the stage manager, whose body attaches the pipeline to the event. There is no explicit call anywhere.
+              Parsing completes, the browser fires the event, and the pipeline runs. Nothing within the engine invokes the pipeline; the browser is the trigger. The header block requests the make file, which loads the stage manager, whose body attaches the pipeline to the event. There is no explicit call anywhere.
             </RT·entry>
           </RT·dictionary>
 
diff --git a/developer/authored/Manuscript.copy/Document/user.html b/developer/authored/Manuscript.copy/Document/user.html
index b694c9d..ec3a90a 100644
--- a/developer/authored/Manuscript.copy/Document/user.html
+++ b/developer/authored/Manuscript.copy/Document/user.html
@@ -123,7 +123,7 @@
           https://style.ReasoningTechnology.com
         </RT·code>
 
-        <p>To install the RT Manuscript style engine locally on disk, clone the github project to a convenient place to browse, say <RT·code>$PROJECT</RT·code>. Build the project. This will put the style engine in <RT·code>$PROJECT/consumer/Manuscript</RT·code> directory with the style engine in it. Browse the file <RT·code>consumer/Manuscript/setup.html</RT·code> and the style engine will be installed in the browser. Currently, it is only known to work in Chrome and Brave. <RT·code>setup.html</RT·code> can be loaded multiple times and/or from different locations, which is a useful feature for testing. Upon a page reload, each manuscript will use the most recently loaded style engine. <RT·code>setup.html</RT·code> will remain in effect for all RT Manuscripts for as long as the browser process runs.</p>
+        <p>To install the RT Manuscript style engine locally on disk, clone the github project to a convenient place to browse, say <RT·code>$PROJECT</RT·code>. Build and promote the project. This will put the style engine in <RT·code>$PROJECT/consumer/Manuscript</RT·code> directory with the style engine in it. Browse the file <RT·code>consumer/Manuscript/setup.html</RT·code> and the style engine will be installed in the browser. Currently, it is only known to work in Chrome and Brave. <RT·code>setup.html</RT·code> can be loaded multiple times and/or from different locations, which is a useful feature for testing. Upon a page reload, each manuscript will use the most recently loaded style engine. <RT·code>setup.html</RT·code> will remain in effect for all RT Manuscripts for as long as the browser process runs.</p>
 
         <RT·section>
           <RT·name>Decorators</RT·name>